Every conversation finds its home.
SupportNest turns scattered customer messages into one shared inbox — tickets with owners and statuses, filters that surface the right thread, and AI drafts that take the typing out of the routine replies.
- 14
- Seeded conversations
- 4
- Channels in the demo
- 8
- AI suggestion types
- Poppy Ashworth2mOrder #58213 — arrival date wrongemail
- Desmond Ferro27hCannot sign in after resetchat
- Ines Kovac5hInvoice shows a cancelled planemail
- Hollis Turner49hReturn label never arrivedemail
support@ is one mailbox and six half-private inboxes.
- Two teammates answer the same customer an hour apart.
- A thread 'pending on the customer' quietly drowns below newer ones.
- Nobody can say who owns a conversation, or what was promised.
- First response time is whatever it is — nobody measures it.
The SupportNest answer
One nest. Every thread owned, statused, and findable.
The inbox shows who's waiting and why; statuses carry the story; and the AI drafts the routine parts so replies leave in minutes — while the judgment stays with your team.
Try the shared inboxFrom scattered to settled in three moves
No migration ceremony, no six-week rollout — the nest is working the same afternoon.
Every channel lands in the nest
Emails, chats, and social messages become tickets with the customer, the subject, and the ask — all in one shared queue nobody has to babysit.
Claim, route, reply
One click owns the ticket; filters keep the right ones in front of you; AI drafts the routine parts so the reply goes out in minutes.
Status keeps the story straight
Open turns to pending when you've asked the customer something, solved when it's fixed — and the thread always shows who said what, and when.
Everything a support team actually uses
No hidden pages, no mystery steps — these are the features the demo genuinely exercises.
Threads read like stories
Full history beside the reply box, statuses one click away, and the AI draft waiting in the wing — that's the whole working surface.
Return label — Hollis Turner
pending- The returns portal said a label was emailed but nothing arrived.Hollis
- I've reissued the label as a PDF — could you confirm it landed?Avery · agent
- Got it, printing now. Thank you!Hollis
AI suggestion
Confirm the label arrived, remind about the 30-day window, and offer the pickup option as a fallback.
Ownership, visible
The avatar rides with the ticket — everywhere it appears.
Claim it yourself or assign across the team; reassignment keeps the whole thread. On Flock, round-robin spreads new arrivals so nobody drowns.
See the assignment flowThree teams that stop losing threads
Online stores
Where is my order, returns, address swaps — the FAQ queue that eats mornings. Statuses and drafts shrink it to minutes, with CSAT proving it.
SaaS teams
Trial questions route to the owner of that account; bugs get a linked ticket; pending keeps sneaky churn-risk threads visible, not buried.
Agencies
One inbox per client on Flock, shared views per script, and a history your whole roster can search when someone's away.
Three plans, two months free yearly
Pick by team size. Switch any time — the demo nest has every capability available.
Hatchling
For a small team answering customers from one nest.
$15/mo
- Shared inbox with one-click assignment
- Open, pending, solved, closed workflow + SLA timers
- Filters by status, channel, assignee, and search
Flock
For teams where support is a squad, not a side duty.
$39/mo
- Everything in Hatchling
- 15 seats with roles and round-robin routing
- 5 shared inboxes with per-inbox signatures
Aviary
For companies where the inbox is the front door.
$99/mo
- Everything in Flock
- Unlimited seats, inboxes, and history
- SAML/SSO enforced sign-in
The FAQ a team lead would write
The full list lives on the pricing page FAQ.
Answer your first ticket in a minute.
The demo nest arrives with 14 conversations across four channels — claim one, draft a reply with AI, set it solved.