A voicebot for customer service that needs no script

For years, a voicebot in customer service meant a carefully drawn script. Someone mapped out the questions customers were expected to ask, wrote a reply for each one, and connected them into a tree. The result worked as long as callers stayed on the path. The moment someone asked a question in a slightly different way, or asked two things at once, the voicebot fell back to "Sorry, I did not understand" and the caller started pressing zero.

Language models changed what a voicebot can be. Instead of matching a caller's words to a fixed branch, a modern voicebot can understand a question asked in any phrasing and look for the answer in a body of text. That moves the work from building scripts to keeping good content. For most companies this is a better trade, because the content already exists: the website, the terms and conditions, the product sheets, the FAQ the support team keeps in a shared document. It also changes what happens when a customer asks something nobody planned for. Instead of a dead end, the voicebot searches everything you gave it, and when the answer is not covered, it offers a callback request so a person can follow up.

Asyntai's voicebot is built on that idea. You add your website, and Asyntai reads it page by page. You upload the documents that never made it online, as PDF files or pasted text. Then you write a short set of instructions in plain English: when to put a caller through, how to talk about refunds, which questions should always become a callback request. When a call comes in, the voicebot says it is an AI assistant, gives your greeting, and answers from that material. Callers hear it reply within a second or two and can interrupt it at any time. Everything it says traces back to material you control, which makes it easy to check: when a caller gets an unexpected answer, the transcript shows the question, and you can find the passage behind it in your own pages.

This matters a great deal for European businesses, where content often lives in more than one language. A rental company in Amsterdam may have its terms in Dutch, its website in Dutch and English, and a price list in English only. A software company in Prague may document its product in English and its contracts in Czech. With Asyntai, the knowledge base can be in any language. The voicebot reads it all and answers calls in English, which suits international customers, tourists, and companies whose service line already runs in English. If you need another language on calls, write to [email protected].

The other big change is who builds and runs the voicebot. A scripted system usually needs a developer or a specialist to add a branch. With Asyntai, the people who answer customers every day can manage the voicebot themselves. Every step is a form in the dashboard. Correcting an answer means correcting the source: refresh the web page in Asyntai, upload a new version of the document, or add an instruction. Asyntai is based in the EU, and the whole setup is designed for teams that want a working voicebot without a project. That lets the support lead own the voicebot rather than the IT department, and the support team is usually where the knowledge sits anyway.

A voicebot also needs a clear way out. Some callers will always want a person, and some questions should go to one. Each phone number you connect can have a transfer number. When a caller asks for a person during your escalation hours, the voicebot says it is putting them through and transfers the call; the receiving phone shows the caller's own number. If nobody picks up within 20 seconds, the caller comes back to the voicebot, which apologizes and takes a callback request. Outside your hours the callback request is the route, with the phone number read back and confirmed, and the request lands in your escalation inbox.

The phone side runs through Twilio, a widely used cloud phone platform that offers local numbers in many European countries. You connect your own Twilio account, import the number you want answered, and Twilio bills you directly for the number and the call minutes. If your customers already know your company number, you can keep it and forward calls to the Twilio number when the team does not answer, or outside office hours. Twilio may ask for business verification before you buy a number in some countries, so it is worth starting that step early. Phone calls are available on the Asyntai Standard plan and higher.

Customers do not only call. Many of them are already on your website when a question comes up. The same voicebot can sit behind a voice button in the Asyntai chat widget, so visitors can talk instead of type. It uses the same knowledge and the same instructions, and the conversation is stored with your other chats. If you also want to understand how voicebots differ from callbots that replace phone menus, our callbot page covers that side.

The simplest way to see whether a content-based voicebot fits your service desk is to try it on your own material. Create an Asyntai account, add your website, upload a document or two, and make a free test call in the browser. Ask it the five questions your team hears most often. The voice agent guide explains each setting, and when the answers are right, you connect a number on the Phone Calls page.