Not a canned chatbot — an autonomous agent that answers in the persona you set, takes real actions (email a booking link, capture a lead, open a ticket), and hands off to a human the moment it should. Every reply governed, every action audited.
Answers, acts and escalates — inside one governed agent.
In the persona and tone you set — governed, no raw visitor PII to the model.
Emails a booking link, opens tickets, captures leads — within what you allow.
The page each chat began on, plus a returning visitor’s past chats — so replies start with context.
Hands off to a human with full context the moment it should.
A visitor lands, the agent engages, and the conversation ends as a booked call, a CRM lead or a ticket. No copy-paste, no dropped enquiries.
The widget appears on your site. The agent sees the page the chat began on and — for a returning visitor — their past conversations, so it can open with context, not a generic greeting.
Replies follow the persona and tone you set, steered by the recent conversation — and every message is governed, so no raw visitor PII reaches the model.
Within the actions you allow, it emails a booking link, captures a lead or opens a ticket — right there in the conversation.
When a question needs a person, it escalates with the full transcript and context, so your team picks up mid-thought — never from scratch.
Every chat finishes as a governed record — a CRM lead or a ticket — with the whole exchange logged to a tamper-evident audit trail.
The console, the AI co-pilot, the branding, the always-on cover and the realtime plumbing — all included with your Business seats.
Included with Business seats. Transcript→CRM lead and pre-chat lead capture use the CRM, part of the +£11/mo Operations add-on; booking-link auto-send needs the Mail module. Nothing is certified; the built-in pay page uses Revolut.
The agent operates on tokenised data, stays inside the actions you allow, and logs every step to a tamper-evident ledger. Set guardrails once; the kill-switch is always one click away.
How SCRS works →It can only do what you allow — booking-link send, lead capture, ticketing.
Visitor PII is masked before the model; rehydrated only for agents.
Every message & action recorded and reversible.
Strangers type anything into a chat box — emails, phone numbers, even card details. SCRS handles that data the same patent-pending way it handles the rest of your workspace.
Before any message is sent to a third-party model, sensitive details are tokenised. The model reasons over Henderson→client_4821 — your team sees the real visitor. Reversible by design.
The agent only performs the actions you switch on, on data it’s allowed to touch. When someone leaves your team, the SCRS leaver kill-switch revokes their access to the records behind those conversations — logically, in one step.
The transcript doesn’t vanish when the visitor closes the tab. It writes straight into the same governed data the rest of your workspace runs on — no integrations to wire.
A sales-shaped conversation lands in the CRM as a lead, with the full thread attached — ready to convert into a deal, quote or invoice.
Explore CRM →A support-shaped conversation becomes a ticket in the shared inbox, with SLAs, the knowledge base and AI auto-resolve already in place.
Explore Ticketing →When no one’s around, the agent collects the enquiry and contact details so it’s waiting as a lead when you’re back — no after-hours visitor lost.
Booking via Flows →Most website chat widgets reply and stop. Live Chat reasons, acts and records — safely.
| Typical website chatbot | Other Me Live Chat | |
|---|---|---|
| Answers in your voice | Scripted flows or generic LLM | Your persona & tone, governed |
| Takes real actions | Hands off a form at best | Booking-link send, ticketing, lead capture |
| Visitor context | Usually none | Chat’s page + returning-visitor history |
| Human handoff with context | Starts the agent from scratch | Full transcript carried across |
| Visitor PII protection | Raw text sent to the model | Tokenised before the LLM, fail-closed |
| Writes to your records | Export or copy-paste | CRM lead or ticket, same governed data |
| Audit & reversibility | Limited logs | Tamper-evident trail, reversible actions |
Patent-pending SCRS firewall (UK App 2602911.6). Customer data stored in the UK/EU. No client data used to train models.
Chat hands off cleanly to Ticketing, books through Flows, and writes back to the CRM — same governed data, no integrations to wire.
