Skip to content

Chapter 14 · Account

Website bot

A chat and voice button for your own website: visitors answer a few questions, then talk to one of your workflows — typed, or as a call from their browser.

What it does

Settings → Website bot puts a floating button on your website. A visitor presses it, answers the questions you chose (their name, phone, email, address, or your own), and then either chats with a workflow by typing or calls it from the browser — the same workflow, the same voice, as a phone call. Every conversation appears in Call history as “Website”, with the visitor’s details.

  1. Press New website bot. Give it a name, the websites it will be on (one or several — the same bot and code work on all of them), and pick the workflow that answers.
  2. Choose what visitors can do: chat and voice, chat only, or voice only. A chat can run its own workflow for chat — typed conversations suit a shorter flow that asks more — or the same one as the call.
  3. Switch on the details to ask before the conversation — name, email, phone, address — and add your own questions. Each becomes a {visitor_…} variable in the workflow.
  4. Set the button’s position, colour, icon, size and text, and the panel’s title, subtitle and greeting.
  5. Press Create, then Copy code and paste the one line into your website, just before </body> (or your site builder’s “custom code” box).

The visitor’s details in the workflow

What the visitor typed is there before the first step runs: {visitor_name}, {visitor_email}, {visitor_phone}, {visitor_address}, one {visitor_…} per question you added, {visitor_fields} (all of it as one JSON object) and {call_source} (“website”). When a phone number was asked, it is also the conversation’s {phone_number}, so Get party info and Save to party work for a website visitor like a caller. The designer’s Variables panel lists them under Website visitor.

A chat workflow, step by step

The simplest chat agent is five steps, and the AI builder writes it for you — in the designer’s prompt box, say “a website chat agent for a dental clinic that answers questions about hours, prices and services and books appointments”. It knows the {visitor_…} variables and the rules below. The HelloCall Agent step is the chat agent; its Templates (the agent library) and Improve with AI work exactly as for a call.

  1. Speak — “Hi {visitor_name}, welcome to Sunrise Clinic. How can I help?”
  2. HelloCall Agent — the instruction says who it is and what it knows (hours, prices, services, policies); the prompt is {last_answer}; actions such as BOOK_APPOINTMENT and TALK_TO_HUMAN.
  3. Speak {reply} — wired back to the HelloCall Agent, so the conversation goes on until the visitor is done.
  4. Each action’s line: an Ask for what is missing, then Save to party / Datamold / Notify on email, and a Speak that confirms.
  5. End — a polite goodbye; below it, Summarize and Save to party so every chat leaves a lead with the visitor’s phone.

Billing and limits

A voice call is paid from your wallet at your plan’s rate, like a phone call, for as long as it is connected. A chat is not a call: it costs no talk time, only the AI tokens its steps use. Each bot has a time limit (ten minutes by default, up to sixty). Pause a bot to stop new conversations without removing the code; delete it and the button disappears from the site.

Questions about website bot

Every question from every chapter is also on the FAQ page.

Can I use one bot on several websites?

Yes — list every website under Websites (up to ten) and paste the same line into each. With Only work on these websites on, conversations can only start from those addresses; the preview in HelloCall still works.

Where do the chats go?

Into Call history like any call, marked “Website”, with the transcript and the visitor’s details. A summary is written to the party when a phone number was given.

Does the microphone work inside the button?

Yes. The panel asks the visitor for microphone permission when they choose to call; it runs on HelloCall’s own page inside your site, so nothing on your site needs changing.