Your Website Chat Can Take the Call Now

Visitors on your website can now call your AI agent without a phone. Turn on the Call button in the Entagl Website channel and the chat widget grows a small phone icon. A visitor taps it, allows the microphone, and is talking to the same Coordinator that answers your phone line and WhatsApp. It can book, answer, ask a person on your team to step in, or take a callback request. The call, its transcript and its recording land in that visitor's chat thread in your inbox. It is off by default, and you decide how long a call may run and how many minutes a day all visitors together may use.

Why put a Call button in a chat widget at all?

Because a lot of people still want to talk. In ServiceNow's April 2026 study of more than 27,000 consumers, 87% ranked the phone as their preferred channel for customer service. The same study found three-quarters prefer to try self-service first, and nearly half said chatbots fail to understand their questions. Read those three numbers together and you get the visitor on your pricing page at 9pm: they tried the chat, the question got complicated, and now they want to say it out loud.

Until now that visitor had two options. Find your number, leave the page and dial it, hoping someone picks up. Or give up and come back tomorrow (they usually don't). Our own Response Velocity Study across 32,581 conversations put a number on how expensive "tomorrow" is: replies within 60 seconds converted at 35.1%, replies after 1 to 24 hours at 7.1%.

A Call button removes the detour. The visitor stays on your page, in the same chat window, and the agent that already knows your services, prices and calendar picks up in seconds.

What happens when a visitor taps Call?

1. The browser asks for microphone permission. Nothing starts until the visitor says yes.
2. The call opens either full screen over your page or inside the chat window itself. That is your choice, in the Website channel settings.
3. The Coordinator answers with your business name and the instructions you already gave it. No phone number is involved on either side.
4. During the call it can check availability and book an appointment, answer from your FAQs and knowledge files, take a callback request with the visitor's number, or flag the conversation for a human on your team.
5. When the call ends, the transcript and recording sit in the visitor's chat thread in your inbox, next to the messages they typed before and after. One contact, one history.

Two things it will not do, on purpose. It will not transfer the call to a phone number (there is no phone leg to transfer), and it will not start a second call for the same visitor while one is running.

Who is it for?

Anyone already using the Coordinator who also has the chat widget on their site. In practice that is clinics, salons, dental practices, agencies and shops where the question that stops a booking is a spoken one: "Is this right for me?", "What does the first visit involve?", "Can I come Saturday?"

If a visitor's question is a quick fact, chat is still faster and they will keep using it. The Call button is for the moment chat stops being enough.

How do you turn it on?

It is a setting, not a project.

1. Make sure the Coordinator is on. The switch stays greyed out without it, with a link to the Coordinator page.
2. Add at least one allowed website under Channels, Website, Security. This is required: without an allowed website the switch also stays off, so no page you do not own can start calls on your minutes.
3. Open Channels, Website, and find the Voice calls card. Turn on "Show a Call button".
4. Pick the call screen (full screen or inside the chat window), set the longest call in minutes, and set the daily call budget in minutes.
5. Save. Reload your site. The Call button is in the chat header.

Step by step with screenshots: Channels in the help center.

What does a website call cost?

Website calls spend Coordinator credits at the same per-minute rate as an incoming WhatsApp call. The rate is shown on the Voice calls card before you turn it on, and every website call appears on your usage page as its own line, labelled "Website call", so nothing is hidden inside a chat total.

Two limits keep an open button from becoming an open tab on your account:

Limit	Default	Range	What it protects
Longest call	10 minutes	1 to 60	One visitor cannot run the meter for an hour
Daily call budget	60 minutes	1 to 1,440	All visitors together, in any rolling 24 hours

On top of those, every call starts with a quick Cloudflare security check that most visitors never notice, each visitor can have one call at a time, and there are limits per network address, per visitor and per business that you do not need to configure. A caller who says nothing for 20 seconds is hung up and not charged, which is what an automated script usually does. When the 24-hour budget is used up, the visitor sees a plain message asking them to continue in chat, you get a notification with a link to raise the limit or turn calls off, and nothing is charged for a call that never connected.

Where does the audio go?

Calls are routed by the visitor's location. A visitor in the United States, Canada, or Central and South America is handled by Entagl's US media servers. Everyone else is handled in the EU. That is the same routing the Coordinator uses for its phone test calls, and it matters if you have customers in Europe who ask where their voice data is processed.

What is different from a phone call to the Coordinator?

Mostly nothing, which is the point. Same instructions, same voice, same booking tools, same inbox. The differences are practical:

• The visitor has no caller ID, so the agent asks for a name and, if a callback is needed, a number, and reads it back.
• There is no transfer to a phone line. Escalation means flagging a human on your team or taking a callback request.
• The call is tied to the visitor's chat thread, so if they typed three messages before tapping Call, the agent has already read them.

If you want to check the agent before visitors do, our guide on how to evaluate and test an AI phone agent applies here as well; run the same interruption, correction and "I want a person" scenarios on the widget.

FAQ

Does the visitor need an app or an account?

No. A browser with a microphone is enough. On a phone, the mobile browser asks for microphone permission the same way it does for a video call.

Can I offer calls on some pages but not others?

The button follows the widget. Wherever the chat widget is shown, the Call button is shown with it, as long as the page's website is on your allowed list.

What happens if the Coordinator is turned off later?

The Call button disappears from the widget and the setting is ignored until the Coordinator is on again. Every call start re-checks this, so a switch flipped by mistake cannot keep spending minutes.

Can my team join a website call?

The call sits in your inbox like any other Coordinator call. A team member can watch the live transcript and flag the conversation. Taking over the audio of a browser call is not part of this release.

Where do I see the transcript?

In the visitor's thread in your inbox. A "Voice calls" card at the top of the thread holds each call with its status, transcript and recording, and the spoken lines are saved to the same thread so search and summaries see them. The visitor's own chat history inside the widget stays chat only; the transcript is never shown back to them there.

Is there a free way to try it?

If your Coordinator is on a free grant, the Call button works with it; the usual free-minute rules apply. Set a small daily budget while you test.

Want to hear it on your own site? Book a 30-minute demo and we will turn the Call button on for your widget, run a call with you, and show you where it lands in the inbox.

If you are still deciding whether voice belongs in your funnel at all, our earlier post on reminder and confirmation calls covers the outbound side, and the 2026 voice-model roundup explains why a browser call today sounds nothing like the IVR you remember.