An English–French AI receptionist should be tested with both languages during the same realistic business call.
Bilingual receptionists in the US often pair English with Spanish.
Atlas supports a different pair.
It speaks English and French, detects the caller’s language and can switch when the caller changes language.
It does not speak Spanish.
Atlas supports English and French only
The language claim should be precise.
Atlas can answer an English-speaking caller and a French-speaking caller.
It can also continue when a caller changes between those two languages during the conversation.
The word “bilingual” should not be used to imply Spanish or every language.
Businesses that require another language need a different process.
Who this pair is for
An English–French pair is a narrow fit, and that is fine. It suits a business whose callers may speak either language, for example: If you are not sure how many French speakers live in your service area, the US Census Bureau publishes data on languages spoken at home.
- a trade or service business with French-speaking and English-speaking customers
- an owner based in the US who also serves French-speaking customers abroad or at home
- a business in France that takes calls from English-speaking clients
If your callers mostly speak Spanish, this is not the right tool. Better to know it before you start the trial.
Use the same call scenario in both languages
A credible language test keeps the business request consistent.
For example, an English-speaking caller can request an appointment and provide a fictional name and phone number.
A French-speaking caller can repeat the same type of request with different fictional details.
Compare whether Atlas collects the same required information and follows the same booking process.
The goal is not to claim that one language sounds better.
The goal is to verify that the business process remains intact.
A test script for three calls
Use fictional or authorised contact details, and keep the same request across the calls so you can compare.
| Call | What you do | What you check |
|---|---|---|
| 1. English | Request an appointment from start to finish in English | Name, number, request and slot are captured |
| 2. French | Request the same type of appointment in French | The same information is collected, in the same order |
| 3. Switch | Start in English, then continue in French after the reason for the call is confirmed | The agent follows, and loses neither the name, the number nor the request |
Test a language switch in the middle of the call
Begin the call in English.
After Atlas confirms the reason for the call, continue in French.
Check whether the conversation follows the new language without losing the caller’s name, number or request.
Then inspect the transcript and owner recap.
A written script can prepare the test, but it cannot replace an actual recording.
The article should not claim a successful live result until that recording has been completed and reviewed.
What a switch looks like, illustrated
The exchange below is an illustration of the behaviour to test. It is not a recording of a real call.
Atlas: Hello, I am the company’s assistant. How can I help you?
Caller: Hi, I would like to book a visit for next week.
Atlas: Of course. What is the visit for?
Caller (in French): En fait, je préfère continuer en français, si c’est possible.
Atlas (in French): Bien sûr. Pour quelle date souhaitez-vous la visite ?
The thing to verify is the last line: the conversation continues in French and the request stated in English is not lost.
Check the captured details after the bilingual call
Atlas emails the owner after every call.
The email includes the outcome, duration, caller details, request, appointment information, summary and full transcript.
For a bilingual test, verify the spelling of the name, the phone number, the stated need and the selected calendar slot.
If Atlas handled a call poorly, the subject includes [PROBLEME].
This signal helps the owner identify the conversation for review.
A checklist for the recap
| Item | Question to ask yourself |
|---|---|
| Name | Is the spelling right, including accents? |
| Phone number | Is every digit correct? |
| Request | Does the summary reflect what was asked, in either language? |
| Appointment | Is the slot in your calendar, at the right time and time zone? |
| Transcript | Does it show the point where the language changed? |
| Subject line | Does it start with [PROBLEME] when the call went badly? |
Accents deserve attention. A name with an accent or a hyphen is exactly the kind of detail a bilingual test should include.
Google Calendar booking follows the same rules in both languages
The delivered agent checks the client’s Google Calendar and proposes slots that are actually available.
It creates the appointment in the correct time zone.
If the caller provides an email address and books an appointment, Atlas sends an email confirmation.
It does not send an SMS confirmation.
The pre-purchase demonstration agent does not book because calendar access is connected after the customer approves how the agent speaks.
The business voice still needs human review
Atlas uses a cloned voice that reflects the business.
The owner listens to the configured agent before activation and can request adjustments.
A voice should not be described as indistinguishable from a person without evidence.
The practical question is whether callers can understand it and whether it follows the approved business process in English and French.
What to do if a language test goes wrong
- Write down exactly where it went wrong: which call, which sentence, which detail.
- Check the recap and the transcript to see whether the detail was heard wrongly or recorded wrongly.
- Send the example to BotLib during the adjustment phase before activation, so the agent can be corrected.
- Test again with the same scenario, so you compare like with like.
The review step before activation exists for this reason. It is cheaper to find a problem in your own test call than with a real customer.
The receptionist keeps the same operational limits in both languages
Changing language does not change what Atlas is authorised to do.
Atlas does not transfer calls, provide a technical diagnosis, promise an intervention time or dispatch a person.
It does not invent a price that is missing from the client’s business information.
If the business supplies an emergency number, Atlas can communicate it.
The caller must dial the number separately.
US pricing applies to the English–French configuration
The launch offer is $49 per month for the first 20 US customers.
The price is retained while the subscription remains active.
The regular monthly price is $99.
The annual plan costs $470.40 per year, equivalent to $39.20 per month when billed annually.
Usage costs $0.25 per minute and calls are rounded up to the next full minute.
| Billed minutes in the month | Launch price ($49) | Regular price ($99) |
|---|---|---|
| 50 | $61.50 | $111.50 |
| 100 | $74 | $124 |
| 200 | $99 | $149 |
A test call of 70 seconds counts as 2 minutes, so a bilingual test with three short calls uses only a few minutes of the 100 free ones.
The trial should include a bilingual test plan
The trial lasts 7 days and includes 100 free minutes.
A card is required, and the first subscription charge occurs on day seven.
After the trial, every minute is billed from the first minute.
Plan one English call, one French call and one mid-call language switch.
Use fictional or authorised contact details.
Compare the transcript, calendar event and recap after each test.
Setup takes 3 to 5 days after questionnaire approval
The business completes a questionnaire and defines its call process.
BotLib configures Atlas and the business voice.
The owner calls the agent, listens in both required languages and requests adjustments.
After approval, Atlas begins answering real customers.
A bilingual evaluation checklist keeps the claim precise
- The test should use English and French rather than an unsupported language pair.
- The same business process should be checked in each language.
- The mid-call switch should be verified through an actual call and transcript.
- The name, number, request and appointment should remain accurate after the switch.
- The owner should approve the voice and wording before activation.
- The business should keep a separate process for transfers, diagnosis and emergency dispatch.
Review Atlas’s documented language and call functions and the current US pricing.