Web chat

The assistant that answers your phone can hold the same conversation in writing, as a chat on your own website. Same assistant, same knowledge — typed instead of spoken.

What it is#

Web chat puts your OnCore assistant on your own website as a text conversation. A visitor types a question into a chat window on your page and the assistant replies in writing — the same assistant that answers when customers call or text your number. You build the chat window to match your site's look; OnCore supplies the conversation behind it. Your website talks to OnCore with short-lived session passes, so your account credentials never appear anywhere a visitor could find them.

What you can do with it#

• Answer questions on your site around the clock — pricing, availability, opening hours: visitors get an immediate written answer instead of a contact form.
• Give one consistent front door everywhere — phone, SMS, and website chat are all handled by the same assistant, so updating it in one place updates every channel.
• Open with a greeting — the chat can start with the assistant's own opening message, inviting the visitor in before they type anything.
• Keep the thread for returning visitors — tag each visitor with an identifier from your site and their conversation carries on across page reloads instead of starting over.
• Feed every chat into your systems — each finished conversation delivers a transcript, summary, and analysis to your servers, and the full history is searchable and exportable through the API.

How to set it up#

Web chat runs on the phone number your assistant already answers: your server exchanges your API key for a short-lived session pass tied to that number, hands the pass to the visitor's browser, and the browser sends messages and receives replies directly — the integration walkthrough is in the Embedded web chat guide, with the full endpoint specification in the Web Chat API reference. Finished chats are delivered to your servers by the end-of-conversation report and can be listed, filtered, and exported through the Conversations API.

Limits & FAQ#

• Web chat is text only; a chat message can be up to 4,000 characters.
• A session pass lasts 30 minutes. When it expires, your page fetches a fresh one from your server — with a visitor identifier attached, the conversation continues where it left off; without one, a new session starts a new conversation.
• OnCore provides the conversation service, not a ready-made chat widget — the chat window on your page is yours to design, in any framework.

Is it the same assistant as our phone line? Yes. The chat is keyed to a phone number you own, and the assistant assigned to that number answers both — one place to update its knowledge, every channel follows.

Can we see the chats afterwards? Yes. Every web-chat conversation lands in your conversation history alongside SMS and WhatsApp threads, with its messages and summary — query or export them through the Conversations API, or receive each one as it ends via the end-of-conversation report.

What happens when the visitor closes the chat? Your page tells OnCore the conversation is over, and the end-of-conversation report fires with the transcript and analysis — so your follow-up starts the moment the chat ends.