One support inbox for all your products

Every site, app and backend you run sends customer messages to the same place. Your team and your AI agents read and reply from there.

Create account See how it installs

Add it to a site with one line

For anything that is not a website, send one HTTP request.

Websites

<script src="https://usesupportbox.com/widget.js" data-project="pk_…" defer></script>

The widget is one file with no dependencies: 16 KB, about 5.4 KB gzipped. It renders in a Shadow DOM, so its styles and yours stay apart.

Apps, backends and forms

curl https://usesupportbox.com/v1/public/conversations \
  -H "x-project-key: pk_…" \
  -H "content-type: application/json" \
  -d '{"email": "ada@example.com", "body": "My export is stuck."}'

The pk_ key is safe to ship in a page or an app. It can only start conversations and read your published help articles.

Many products, one inbox

Create one project per product. Messages from all of them arrive in the same inbox, and each project keeps its own settings.

Its own key: Each product sends messages with its own project key.
Its own AI settings: Turn AI answering on for one product and leave it off for another.
Its own help center: Articles are written and published per project.
Its own Slack channel: One private channel per project, one thread per conversation.

AI agents can help, within limits you can read

Connect a coding agent or your own automation to the MCP server at /mcp. It gets 13 tools: 8 that read and 5 that write.

What an agent can do

Read projects, members, conversations and help articles
Create a project and get its install snippet
Reply to a conversation
Update a conversation
Create and edit help article drafts

What no tool can do

Delete anything
Publish a help article: a person does that
Add or remove team members

Built-in AI answering is optional. It uses your own Anthropic key, answers only from the FAQ you write, and hands the conversation to a person when it cannot answer.

The full API and MCP reference for agents is at /llms.txt.

Reply from where your team already is

A reply reaches the customer whichever of these it was written in.

Dashboard: The inbox updates live as messages arrive, and shows when a customer is typing.
Slack: Each conversation is a thread. Reply in the thread and the customer gets it.
Email: If the customer has left the page, your reply is emailed to them.
Webhooks: Three signed events, for new conversations, new messages and updates.

A help center for each product

Write articles in Markdown. Agents can draft them; a person publishes.

Hosted for you. Pages are rendered on the server and work without JavaScript.
On your own domain. If your site is on Cloudflare, one small Worker route serves it at your address.
Readable by AI tools. Each help center has its own llms.txt, a sitemap, and a Markdown copy of every article.

What it costs today

Supportbox is free today, within these limits. Paid plans have not been decided.

New conversations	200 a day
Reply emails	100 a day
AI replies	300 a day
Team members	up to 50

There is no charge per seat. There is no charge per AI reply either: you pay your model provider directly.

What it does not do yet

Better to read it here than to find out after you install it.

No incoming email. There is no support@ address to forward to. Email is used to send your replies.
The widget is in English only. You can change its button colour and label.
No passwords or SAML single sign-on. You sign in with Google, with a link or code sent to your email, or with an API key.

Try it on one product

Create an account with Google or with your email. By email, we send you a sign-in link and a six-digit code.

Create account Log in