Skip to content

BUILD & RUN — CHAT AGENTS

Most website chat takes an email and never books the job.

The chat widget on your site is a form wearing a costume. It takes a name, promises somebody will be in touch, and adds a delay to a person who was ready to buy. This one answers the actual question and finishes the booking inside the conversation.

Book a pilot call

Free · 20 minutes · no commitment

YOUR SALES AND GROWTH

WHO THIS IS FOR

Businesses whose website chat collects an email address for somebody to chase tomorrow.

THE PROBLEM

The delay is the whole cost. Somebody who was ready to book is now waiting for a callback, and every hour they wait the decision reopens. Each step between wanting the thing and having it booked is a place to lose them, and a form that promises a human is a step, not a shortcut.

WHAT IT LOOKS LIKE

Web chat

Airport shuttle bookings

EXAMPLE CONVERSATION

SEATS AND TIMES FROM THE LIVE BOOKING SYSTEM

  1. Customer · web chat

    Is there a shuttle from Pearson to London on Friday? I land at 4:10 pm.

  2. Agent

    Yes. Friday’s 5:30 pm run has 6 seats left. Which terminal, and how many of you?

  3. Customer

    Terminal 3. Two of us, three bags.

  4. Agent

    It stops at Terminal 3 at 5:40 pm, which leaves 90 minutes after you land for customs and bags. Seats are $79 each. Shall I book two?

  5. Customer

    Yes, please.

  6. Agent

    Booked. If your flight lands late, your seats move to the next run with room.

Booked in the chat

Friday, 5:40 pm

Terminal 3 · 2 seats · 3 bags

Ask for a person at any point and the office takes over this chat, with the conversation attached.

A traveller books an airport shuttle in the website chat on their phone. The agent answers from the live seat count and the operator’s own terms, and finishes the booking inside the conversation.

What you get.

  • An agent that can answer on your real services, terms and availability.
  • Qualification and booking completed inside the conversation, not handed onward.
  • Deployment across web chat and whichever messaging channels your customers already use.
  • A handover to a person with the conversation attached, when one is warranted.

How it works.

Priced against the scope, after a Diagnostic that is small on purpose. The shape of the work we can tell you now.

THE SHAPE
Built, then run. It needs revisiting whenever your services, prices or availability change.
WHAT WE NEED FROM YOU
Access to your site and to whatever holds your real availability.
WHAT YOU KEEP
The configuration and the full conversation history.

What this does not include.

Published because you should know before the call, not after the invoice.

  • A generic FAQ bot. If a search box would do the job we will say so and save you the money.
  • Deployment without a route to a human.

How we price this →

QUESTIONS

Our CRM already includes a chat widget.

Most bundled widgets route to a form. The question is whether the conversation can see your real availability and finish the booking. If yours can, keep it — we will tell you that.

Can it run alongside a voice agent?

Yes, and it usually should. Chat takes the straightforward enquiries; voice takes the callers who want to talk to something.

Bring us one bad week.

Book a pilot call. Tell us where the week goes wrong, and we’ll tell you what an Operations Diagnostic would map and measure.

The first paid step has a clear scope and an end date, and the pilot after it is one workflow — not a platform, and not an open-ended retainer.

Free · 20 minutes · no commitment