Shared inbox
Emails and web-form requests become tickets. Customer replies thread back to the right ticket, and internal notes never reach the customer.
Help desk for small teams
Email and web-form requests from all your brands land in one list. Next to each ticket, agents see the customer’s plan and recent activity from your own product, so the first reply is the right one.
Most help desks assume one company, one inbox. Ours starts from several brands sharing one support team.
Emails and web-form requests become tickets. Customer replies thread back to the right ticket, and internal notes never reach the customer.
Each brand gets its own support address, help center and email style. Customers only ever see the brand they wrote to.
Connect your product and the sidebar shows the customer’s plan, usage and recent activity. Agents stop asking for details you already have.
Triggers assign and tag new tickets, automations follow up on quiet ones, and macros turn common answers into one click.
Set first-reply and resolution targets per brand and priority. Timers pause while you wait on the customer, so the numbers stay fair.
Publish answers once and let customers find them. Pages are plain, fast HTML that search engines and AI assistants can read.
Point support@yourbrand at your help desk. New emails become tickets, and replies go out from the same address.
Repeat for each brand, invite your agents and put them in groups. Views and macros work across every brand.
Link customer accounts through the API to show plan and usage data next to tickets. It’s optional; the inbox works without it.
For developers
Our own agent app is built on the public REST API, so you can create tickets from your product, sync customers and build your own tools on the same endpoints.
Webhooks are signed and retried until your server answers. Every change to a ticket is recorded with who or what made it, so you can always see why something happened.
Read the API docscurl -X POST https://api.example.com/v1/tickets \
-H "Authorization: Bearer $API_TOKEN" \
-H "Idempotency-Key: 7f3c9a" \
-d '{
"brand": "seraverra",
"subject": "Scan stuck on processing",
"requester": { "email": "dana@ptowndigital.example" },
"custom_fields": { "scan_id": "02b034b1" }
}'Priced per agent, per month. Every plan starts with a free trial.
One brand, getting out of a shared inbox.
[$ price] / agent / month
Several brands and a growing team.
[$ price] / agent / month
Support connected to your own product.
[$ price] / agent / month
No. Forwarding your support address is enough to start answering tickets. Connecting your product through the API is optional and can come later.
No. Notes are visible only to your agents and are never included in emails to the customer.
No. Each brand has its own address, help center and email style, and customers only hear from the brand they contacted.
Yes. Tickets, customers and organizations can be imported through the API. [Describe the import tool or service once it exists.]
Start with one support address and add the rest when you’re ready.