Answer chats from Slack or Teams, let the AI answer the phone and call your own tools over MCP, automate anything over a real REST API — and put the whole thing inside your mobile app.
New chats, AI handoffs and reopened conversations post straight into the channel your team already lives in — and agents answer right from there. The visitor sees the reply in the widget instantly.
Everything your console can do, your tools can do too. Tokens are minted in one click and scoped read or read-write.
Conversations, replies, contacts, tickets and stats over clean JSON with tenant-scoped bearer tokens — shown once, hashed at rest, revocable instantly.
A native MCP server so Claude, your IDE or any agent framework can drive SiteHelp — and an MCP client so your AI calls your connected tools mid-chat.
Signed outbound webhooks trigger your Zaps in real time; the API handles the actions — reply, create tickets, look up contacts — with no code.
Point your number at SiteHelp and callers talk to the same grounded AI that answers your chats — in the caller's language, in real time. It hands off to a person (or takes a voicemail) the instant it should, and every call becomes a transcript in the workstation that counts in your resolution analytics.
We already expose an MCP server so agents can use SiteHelp. Now the assistant is also an MCP client: connect your internal admin API, billing system or ops runbook, and the bot calls those tools mid-conversation to actually resolve the request — not just describe it.
One URL puts the full chat experience — themes, languages, AI, attachments — inside any iOS or Android app.
A hosted full-screen chat page for WebViews, with copy-paste snippets for Swift, Kotlin, React Native and Flutter.
Pass the signed-in user's name and email and they skip the pre-chat survey — the conversation lands on the right contact.
The chat screen carries the tenant's brand, colours and theme — nothing of ours unless you want it.
From the channel your team lives in to the agents your tools run — SiteHelp meets your stack where it is.