Types or talks
The visitor types a question, or presses a button and speaks to the agent in a real voice. Both go to the same agent and get the same answer.
Website chat
The website answers back.
A visitor on a client's site has a question at nine at night. The contact form promises somebody will be in touch. By morning they have booked with whoever answered first.
What the agent does
The phone agent, on the website, in the client's colours.
One line of code puts the same agent on the site. The visitor types, or presses a button and talks, and gets the answer a caller would.
One knowledge base
The widget reads the same knowledge base as the phone agent. Change the opening hours once and the phone, the chat and the texts all change.
The client's brand, nobody else's
Their colours and their avatar. No vendor branding in the snippet, the loader or anything the visitor sees. The widget looks like part of the site because it is.
Nudges and quick questions
A nudge on the pages that need it, and quick-question buttons so a visitor can ask the common thing in one press instead of typing it.
Locked to the site
An allowed-domain list decides where the widget will load. The API key never reaches the browser, so the snippet on the page gives nothing away.
Remembers the conversation
The transcript follows the visitor from page to page for an hour, so a question asked on the pricing page is still there on the contact page.
How it goes for the visitor
Open, ask, answered, logged.
- One line of code goes on the site. Any site, any platform. The allowed-domain list says where it may load.
- The visitor opens the widget. They type, or press the button and talk. A page nudge or a quick-question button may have started it for them.
- The agent answers. From the knowledge base and the website itself, in the same words a caller would hear.
- The visitor moves around the site. The transcript stays with them for an hour, so nobody repeats themselves.
- The chat is logged. In the dashboard, separately from phone calls, so the business can see what the website is being asked.
What the business gets
A record of every website conversation, and one place to keep the facts.
The website stops being a brochure and starts being somewhere a question gets answered.
- Website chats logged in the dashboard, separately from phone calls, so the two can be read apart.
- One knowledge base behind the phone, the chat, the texts and the email agent. One edit, every channel.
- A widget in the client's own colours and avatar, with no mention of anyone else.
- Chats, calls and texts for the same enquiry kept together where a lead is filed. See lead capture.
- Anything else through the REST API and webhooks, or Zapier.
WhatsApp, stated plainly
The platform can send one-way messages WhatsApp-first, falling back to text when WhatsApp cannot deliver: a follow-up after a call, an alert about an important call, a booking link, a sign-up code. There is no WhatsApp agent. A customer cannot hold a conversation with the agent over WhatsApp, and Talkgate does not sell one. Two-way conversation is the phone, text, the website widget on this page, and email.
Sold through partners
The obvious add-on to every website you already look after
If you host, build or maintain a client's website, the widget is a line of code away and carries the client's own colours. It is sold most simply as a companion to the phone agent: the same facts, the same voice, one more door into the business. Clients who only want the website piece can have it on its own. Sold through partners: you set the price, Talkgate runs the platform. See the partner programme.
Works with
Any website, and the client's own software behind it.
Live answers about a particular customer come from the connected system. See all integrations.
Next step
Put the widget on a test page and ask it something.
A partner briefing shows the widget running in a client's colours, the chat log, and the knowledge base behind both.