Resources / Chat and FAQs

Record a visitor’s language preference for follow-up

A visitor may prefer another language for a staff conversation.

01

The decision this workflow supports

A visitor may prefer another language for a staff conversation. Recording that preference is useful, but it should not become a promise that a particular language is supported by every shift or by an untested assistant translation.

02

Put the review process in place

Use only language support the owner has approved for the current workflow. If a preference cannot be met automatically, record it for staff and clarify the uncertainty. Preserve dates, contact details and request status carefully when the visitor switches languages.

03

Worked example for your team

A fictional visitor asks to continue with staff in a language that is not listed as supported on the current shift. Record the preference and explain that staff must confirm how they can help. Do not promise a particular employee or translate an unapproved policy as though it were authoritative. Ask the visitor to check the key request details, especially dates and contact information. The staff reviewer should see both the language preference and any unresolved communication need, rather than assuming the assistant completed a conversation in a verified supported language.

04

Sample wording to approve

“I can note your preferred language for the team. Staff will confirm how they can help. Please check the request summary so the date and contact details are recorded correctly.” This wording is a draft for the restaurant owner to approve before use.

05

Fields for the staff handoff

Staff need preferred language, approved support available, request summary, contact route, and staff reviewer. Mark uncertain details explicitly and keep the requested action separate from anything restaurant staff have already confirmed.

06

Acceptance tests before use

A language preference is not a staffing guarantee. Switching languages does not alter the event date. Unsupported translation does not invent a restaurant policy. Record the observed result, assign any mismatch, and repeat the affected scenario after correction.

Further reading

Catering inquiry value calculator ↗

Try Ava with your business’s public information ↗

Related guides

Your workflow, first

Let’s map your first week.

Bring the calls you want covered. We’ll agree the script, handoff and limits.

Start a pilot