Verified. Checked.Fixed. Closed.
Here's exactly what happens between a customer's first message and a closed ticket, and what it takes to switch it on.
Seven steps. Every conversation. No shortcuts.
Connect your docs and your app
ClientSupport reads your product docs as a per-product knowledge base, and talks to your app through a small, documented support contract. No scraping, no screen automation.
- Markdown docs ingested and searched per product
- A handful of HTTPS support endpoints in your app
- A shared secret signs every request both ways
Know exactly who is asking
Signed-in customers are recognized instantly through a support token your app signs. Logged-out customers get a 6-digit code at the email on their account.
- Codes last 10 minutes with 5 tries
- Captcha before any code is sent
- 24-hour lockout after repeated failures, and you get an email
- Verification lasts 30 minutes, bound to one conversation and browser session
Check the live account
Once verified, the agent reads plan, orders, usage and account health, then runs read-only diagnostics for that customer's own account.
- Account ids always come from verification, never from the model
- No card data and no price catalog in the chat
- Diagnostics are read-only by design
Take the safe action
The model proposes a tool call. The server checks verification, role, rate limits and argument shape, writes the audit row, and only then executes it.
- Password resets go only to the account's own email, 3 per hour
- Billing portal and upgrade links only for owners and billing admins
- One global switch turns off every account tool instantly
Clear two independent judges
Before any reply is sent, two reply judges from different model families review it for promises the business never made. An input judge flags oblique money asks before the model even answers.
- Billing conversations answered from approved templates
- A blocked draft is replaced with a safe handoff sentence
- Judges must differ from the generator and from each other
Hand off what should be human
Refunds, credits, disputes and 2FA resets are never improvised. They land in your inbox with the transcript, a summary and every action already taken.
- The customer is told exactly what happens next
- Nothing is refunded or promised in the meantime
- You reply once, with the whole story in front of you
Close the loop
The customer rates the answer, the conversation is stored with its audit trail, and you can review any of it from your AI assistant through the MCP connector.
- One rating per conversation
- Every attempt logged, including denials
- Transcripts expire after 90 days, the audit log is kept
Live in three moves.
No rip-and-replace. Your app keeps owning its data and actions. ClientSupport only asks for what the contract allows.
Drop in one tag
Add the widget script to your app. Signed-in pages pass a short-lived support token so customers never have to prove who they are twice.
Connect your app
Expose the six support endpoints below, signed with a shared secret. A second product that speaks the same contract is just another config folder.
Choose models and judges
Pick your generation model and two judges from different model families. We run the live judge evals with you before go-live.
| Endpoint | What ClientSupport asks your app for |
|---|---|
| GET account-status | Plan, orders, usage and holds for the verified customer |
| GET diagnostics | Read-only checks for one account, like order tracking, failed webhooks or sync health |
| POST password-reset | Your own reset email, to the address on the account |
| POST billing-link | A short-lived Stripe portal or upgrade checkout URL |
| POST otp/send | Send a 6-digit code to the email on exactly one account |
| POST otp/check | Confirm the code and bind verification to the conversation |
ClientSupport will never ask your app for refunds, credits, cancellations, coupons, data deletion or 2FA resets. Those routes should not exist on the support credential at all.
Where customers meet it. Where you run it.
The same pipeline, the same guardrails and the same audit log behind every surface.
In-app widget
One script tag. Signed-in customers are verified instantly through your app's support token.
Hosted help page
A full-page help desk you can link from anywhere, with email-code verification for logged-out customers.
Founder handoff inbox
Edge cases arrive by email with the transcript, summary and actions, ready for a one-shot reply.
MCP connector
Read conversations, list tickets, check settings and draft replies from Claude, ChatGPT or Grok.
See your help desk run itself.
Apply for early access and we'll walk you through a live conversation on a product like yours. Month-to-month, no annual lock-in.