Choose the languages your audience uses
Enable the languages for the agent’s role and intended customers. Start with the markets you serve and expand the deployment through testing and tuning.
Choose the languages, voice and terminology for the people you serve. Echo brings multilingual agent configuration together with a team that can help prepare and tune the experience for your audience.
Your voice. Your knowledge. Your way of working.
Can I return the jacket I bought last week?
I can help. Is it unused, with its tags still attached? Our example policy allows returns to be reviewed within 14 days.
Returns & exchangesIllustrative product experience · example data · no live actions
Enable the languages for the agent’s role and intended customers. Start with the markets you serve and expand the deployment through testing and tuning.
Prepare names, product terms and service instructions in context. Review the way the agent explains your business rather than translating a greeting alone.
Work through voice, pace, enabled language and representative questions. Our setup teams can help refine the conversation using agreed enablement hours.
Explore the configuration and decisions behind a useful conversation. Each step shows what you control and how it helps your customer.
Configure the greeting, voice, pace and enabled languages around the people who will use the agent. Test the actual conversation, including your product names and common questions.
Choose a greeting and conversational instructions that match the task. A service agent should explain how it can help; a sales agent should open a useful discovery conversation.
The greeting and instructions can vary by agent and business task.
Workflow ideas to configure around the knowledge and systems you use.
Prepare hotel policies and service requests for Arabic- and English-speaking guests, with the right terminology and a clear route to your team.
Explore it with AIHelp buyers ask about capabilities in an enabled language while keeping the answers grounded in your approved product information.
Explore it with AIConfigure the language and questions for an intended customer group, then review how the conversation captures the detail your service team needs.
Explore it with AIFrom voice and knowledge to integrations and launch. These are the details that help you choose a useful next step.
Talk through your idea with the Echo guideYes. The website conversation experience offers both languages, and Arabic and English chat have been exercised with the website agent. Use the language controls to choose the conversation you want to explore.
The website agent has 32 configured language choices. The website pages themselves are currently in English and Arabic. For your deployment, confirm the intended languages and review the voice and conversation quality with our team.
Echo’s agent configuration includes voice and voice-speed controls alongside language and greeting settings. We help choose and test an appropriate combination for the role and audience.
We can scope language and voice tuning around your intended audience and review representative conversations. Particular dialect or accent requirements should be assessed and tested as part of the deployment.
No. Website language, the website demonstration agent and your own Echo agent configuration are separate. Your team chooses the enabled languages and channel experience for your agents.
Echo supports configurable agent voice, pace, greeting and instructions. Your setup should include testing your business names, terminology and common questions in the intended languages so the experience fits your audience.
Our team reviews your number, current telephony provider and routing requirements. Forwarding, routing and number provisioning are scoped for the deployment; any provider or telephony costs are discussed as part of setup.
Echo supports enabled language choices, and our website agent currently has 32 configured languages. We help choose and test the languages your customers need. Website translation, the agent’s greeting and conversation language are separate parts of the experience.
You can explore Echo directly, or work with our setup team. We help define the first task, configure the agent and knowledge, connect channels and scope any required integration. A focused knowledge-and-chat workflow can be a useful first step before deeper systems work.
Your plan’s annual enablement allocation can support agent and knowledge setup, channel onboarding, language tuning and agreed integrations. Our setup teams are available 24/7. The included allocation, additional engineering and ongoing support terms are agreed with you for your plan and scope.
The first use case determines the work. Readiness depends on approved knowledge, channel access, language testing, system integrations and your review. We agree a scoped first launch and its acceptance steps rather than asking you to redesign every process at once.
Discuss the expected voice and chat usage, number of agents, channels, team access and implementation needs with us. Platform usage, telephony or channel-provider charges and engineering scope can affect the total. The current quote or plan terms define what is included.
Yes. Bring your access, data handling, hosting and operational requirements into the scoping discussion. We review the applicable deployment and commercial options with you, including any additional engineering or documented assurances your organisation needs.
You do not need to prepare everything alone. Use this checklist to see what you already have and where our setup team can help.
items you marked ready
A local planning checklist; nothing is submitted.Five questions customers really ask, the audience and the outcome you want.
We define the agent’s role, the first workflow and how to judge whether it works.
Example: explain returns and prepare a service request.
Product descriptions, policies, service instructions and a person who owns each source.
We organise the agent’s knowledge, clarify boundaries and test missing information.
Example: current policy, exclusions and who approves exceptions.
Your first channel, the languages customers use and the tone you want them to hear.
We configure the entry point, greeting and available voice or messaging settings.
Example: Arabic and English website chat, then a phone workflow.
The tools involved, a system owner and the specific information or action needed.
We scope permissions, identity checks and the connection or engineering required.
Example: read an allowed order status; prepare a request for review.
Who owns enquiries, who replies to exceptions and what a person must approve.
We map the messaging takeover, team responsibilities and follow-up process.
Example: AI explains policy; the service team approves the refund.
Typical enquiries, difficult cases, product names and examples in your launch languages.
We test the whole journey, review responses together and agree the first release.
Example: a normal request, missing knowledge and a rejected system action.
Setup teams are available 24/7. Engineering work and enablement hours are scoped to your plan and workflow.
Explore the platform yourself, or work with our team on your first workflow. You don’t need to have every answer before you start.
Get to know agent configuration, knowledge and channels. Choose a focused use case and begin shaping your agent.
Our 24/7 setup teams help with knowledge, languages, channels and the integrations your workflow needs.
Less time repeating the basics. More attention for the conversations that need your people.
02A better starting point for sales: what the customer needs, why it matters and where to take the conversation.
03Less re-explaining and re-entering. More context for the team responsible for getting the job done.
04A useful conversation from the first hello, shaped around the customer’s question and your business process.
05A consistent service voice across configured channels, with people ready to take over when the message needs them.
06From a customer question to the right information, a prepared request or a permitted action in your systems.
07Move from guessing what happened to reviewing the conversation and deciding what to change next.
08A platform you can use, with people to help you turn an idea into a working customer experience.
09Your information becomes part of the conversation, with a clear approach when an answer needs more context.
10A customer conversation stays visible as it moves between an AI reply and a person’s decision.
11From a contact list to conversations with a purpose and follow-up your team can understand.
12A clear customer experience starts with the right language, the right information and a thoughtful conversation.