Introduction
The operational helpdesk for small and medium businesses — one place to receive customer messages, turn them into tickets, and keep a record.
Get started in minutes
Embed the chat widget on your site with a single snippet.
Key features
One shared inbox
Website chat and email arrive as conversations in a single inbox your whole team works from.
Trackable tickets
Turn any conversation into a ticket with a reference like ACM-42, a status, a priority, and an owner.
Teams and routing
Route work to teams with rules, and let automatic assignment spread new tickets fairly.
AI assistant
Answers widget visitors from your published help articles, and hands off to a human with a briefing.
Quick links
Overview
The two integration surfaces, how to choose between them, and the conventions shared by both.
Install the chat widget
Embed the snippet, set your origin allow-list, and configure branding. No API code.
Public API: Authentication
The publishable key and visitor token model, and where each one belongs.
Context Sources
Let agents pull data out of your systems and onto a ticket — you build the endpoint, we call it.
API reference
The six Public API endpoints — conversations and the help center.
For developers
There are two ways in: install the chat widget and write no API code at all, or build your own interface on the Public API from your backend. Both feed the same inbox. The API is versioned under /api/v1. Start with the overview.
Local development: http://localhost:8080/api/v1