Skip to content

Multilingual template

Bilingual caller handoff script

A multilingual intake pattern for teams that receive English, French, Dutch, or mixed-language calls and need clean routing.

Test multilingual answeringView all templates

Example dialogue

A safe starting point for the first call flow.

Treat this as a planning artifact, not a recording or customer transcript. The production version should use your approved greeting, disclosure, service rules, and escalation contacts.

Havio agent

Hello. I can help in English, French, or Dutch. Which language do you prefer?

Caller

French, please.

Havio agent

Bien sur. Je vais prendre les details et transmettre le resume a l equipe dans la bonne langue.

Caller

Je veux planifier une visite.

Havio agent

Je vais verifier les informations necessaires, puis creer une demande de visite avec le resume.

Qualification questions

  • Which language does the caller prefer?
  • Should summaries be written in caller language, team language, or both?
  • Which language-specific transfer contact should receive the call?
  • Does the call require localized consent, disclosure, or recording language?
  • What should happen when the caller switches language mid-call?

Routing rules

  • Use approved disclosure and recording language for the caller region and language.
  • Route to language-specific humans when the topic requires a person.
  • Summarize in the team language when configured, while preserving key caller wording.
  • Escalate when the agent is uncertain about meaning, consent, or sensitive context.

Output fields

  • Detected and preferred language
  • Consent and recording state
  • Caller request and translated summary
  • Language-specific owner or queue
  • Uncertainty or escalation flag

Launch checks

  • Approve scripts in each supported language before launch.
  • Test language switch, accent, noisy audio, and opt-out paths.
  • Confirm where translated summaries are written.
  • Review multilingual transcripts with a native speaker during soft launch.

Launch readiness

Turn this template into a checklist before callers hear it.

Check the items your team has approved. The list becomes a practical demo brief for routing, knowledge, transfers, and post-call review.

Readiness score

0%

0 of 4 checks complete

Guardrails

The template is only launch-ready after the boundaries are approved.

Approve what the agent can say about prices, availability, timing, policy, and service scope.

Confirm when the agent must transfer, create a callback, or stop because the request is sensitive.

Test failed calendar writes, unreachable transfer contacts, missing caller data, and unclear intent.

Review transcripts during soft launch before expanding traffic or adding more call types.

Related buyer paths

Use this template with the pages buyers usually need next.

Bilingual receptionistContinueRecording consentContinueBelgian real estate workflowContinue