One inbox. Conversations, not tickets.
The person waiting longest is right there at the top. Answer, move to the next, reach "you're all caught up." Everything you know about the customer sits beside the thread — no queues, no SLAs, no bloat.
The whole workflow.
Open. Read. Reply. Resolve. There isn't a fifth step, and there's nothing to configure to get there.
Newest at the top
New messages surface at the top of one list. No triage, no assigning — just the next person to answer.
Open the thread
The customer's messages and your replies, in order, with their context in a panel right beside it.
Reply like a human
Write and send — it reaches them by email. AI can draft a suggestion first, but you approve before anything sends.
Resolve, or it returns
Mark it resolved and it's out of your way, still searchable. If they write again, it comes right back.
Context, right beside the thread.
Every conversation carries the customer's email and whatever attributes your form sent — plan, signup date, account id. No more asking "which plan are you on?" before you can help.
It's the same context you attach when you set up your contact form — it just shows up here, rendered next to the messages.
Built for how small teams actually work.
Enough structure to stay organized, none of the machinery that makes support feel like a factory.
One team per app
Each team owns an inbox, its sources, and its members. Run several products? Switch between them without crossing wires.
Shared, not siloed
Everyone on the team sees the same inbox and can reply to any conversation. Roles keep settings and keys with owners and admins.
Filter by source
See where each conversation came from — production, marketing, staging — and narrow the inbox to one source when you want to.
Every channel, one place
Form, API, or inbound email — every message lands as a conversation in the same inbox, regardless of how it arrived.
AI drafts, you approve
Suggested replies are a starting point, never an auto-send. You read, tweak, and send — an assistant, not an autoresponder.
No ticket theater
No "your ticket #48213 has been escalated." Your customers write to you; you write back. That's the whole idea.
Questions, answered.
Are these tickets?
No — they are conversations. There are no queues, no SLAs, no swimlanes, and no ticket numbers. It is one list of people who wrote to you, newest activity first, and you answer from the top.
How do I know who I am talking to?
Every conversation has a customer panel beside it showing their email and any attributes your form or API sent — plan, signup date, account id, whatever helps. The same person across two messages is one customer, so their context follows them.
Can my teammates help?
Yes. Invite teammates to a team and everyone shares the same inbox — anyone can read and reply to any conversation. Small teams do not need assignment rules; they need to see what is going on. Roles keep settings like sources and billing with owners and admins.
What if I run more than one app?
Each app is its own team with its own inbox, sources, and members. A switcher moves you between them, so an agency or a founder with several products keeps every app cleanly separate.
Where do messages come from?
Anywhere you have wired up: the embeddable contact form, a form posting to the API, or inbound email if you turn it on. However a message arrives, it lands as a conversation in the same one inbox.
A calmer place to answer. Be present.
One list, real context, replies that reach people by email. Free to start — no card, no queue to build.