Ticketing built on chat
Raise a ticket from any chat, give it an owner, and tell the customer when it is done.
Raise a ticket from any conversation
The ticket stays linked to the thread, and the reply goes back the way the customer wrote.
Website chat
Followed in the chat widget.
Email
Replies from your own address.
WhatsApp
Back to the number they used.
Instagram
Raised and answered in the DM.
Telegram
The bot says when it is done.
Slack
The thread stays in Slack.
Discord
From a mirrored server thread.
Microsoft Teams
The channel keeps it in view.
Everything the work after the reply needs
One ticket, linked to the conversation it came from.
A customer ticket for one person, a back-office task behind the scenes, or a tracker for an issue many report.
- Customer
- Back-office
- Tracker
Everything about it, on one sheet
Click a card on the board and the ticket opens beside it.
One sheet for all of it
The state, the owner, the notes and the files, open beside the board.
A feed of the work
Who did what and when, in order, under the subject.
Every customer behind it
Linked conversations stay a click away, and Reply all reaches them.

Refund for order #4821 not received
- System2 hours ago
Raised from the conversation with Nuray Aksoy.
James Brown1 hour agoSame as #147, linked it.
Emma Wright12 minutes agoRefund approved, waiting on finance to confirm.
Nuray Aksoyjust nowFinance confirmed. Refund lands in 3 to 5 days.
Links3
- Nuray AksoyWhatsApp
- James BrownWebsite chat
- Emma WrightEmail
What the customer sees
The ticket follows them in the chat widget, in plain words.
Plain words, not states
Open reads as Submitted and Solved as Resolved. No priorities, no notes.
A person's name
The owner's first name, so the customer knows someone has it.
Told when it moves
In the widget and by email, when it changes and when it is done.

Tickets
From chat to ticket to done
Three steps, without leaving the conversation.
- 01
Raise it
In the conversation, switch the composer to Ticket. Write what needs doing, then pick a kind and a priority.
- 02
Work it
Filter the Tickets board by state, priority and owner. Add notes and files as you go.
- 03
Close the loop
Set the final state and reply from the ticket. The conversation keeps the link.
What is a ticketing system?
Software that turns a customer request into tracked work, so nothing is forgotten between the first reply and the fix.
- Ticket
- A unit of work with a number, a subject, a state and an owner, linked to the conversation it came from.
- State
- Where the work is: open, in progress, waiting, solved or closed. The board shows them as columns.
- Priority
- Low, normal, high or urgent. The same flag the conversation carries, so nothing is triaged twice.
- Owner
- The teammate it is assigned to. Unassigned is the queue, and a workflow can assign it for you.
Sellio raises a ticket only when the work outlives the chat
Sellio beside Zendesk and Freshdesk
Ticket-first help desks. The differences are seats, AI billing and where a ticket starts.
| Feature | |||
|---|---|---|---|
| Five seats, per month | $95/mo (Essentials) | $275/mo (Suite Team) | $275/mo (Pro) |
| Pricing model | Per workspace. Per workspace; seats and channels are plan limits | Per agent. Per agent; AI per resolution; add-ons extra | Per agent. Per agent; AI per agent and per session |
| Free plan | 2 seats, no clock. 2 seats, 1 channel, 1 AI agent, no trial clock | 14-day trial. None; 14-day trial | 14-day trial. Not on the pricing page; 14-day trial |
| Website live chat | One script tag. One script tag; guides for HTML, React, Next.js and more | Suite plans. Suite plans | Via Freshchat. Via Freshchat or Omni |
From Mini. From Mini: WhatsApp Business API, several agents on one number | Suite, plus fees. Suite plans, plus conversation fees | Via Freshchat. Via Freshchat or Omni | |
| How AI is billed | Metered, with caps. Metered from an included credit, with caps you set | Per resolution. Per automated resolution, on top of seats | Per session. 500 one-time trial sessions, then $49 per 100 |
| Tickets | From Essentials. From Essentials: raise from any chat; customer, back-office and tracker | Ticket-first. Ticket-first | Ticket-first. Ticket-first |
| Visual workflow automation | From Mini. From Mini: 11 triggers, 18 actions, no code | Form-based. Triggers and automations, form-based | Form-based. Automations, form-based |
| Analytics and CSAT | From Essentials. From Essentials: response times, resolution, CSAT; topics and email reports on Essentials | Explore. Explore; advanced on higher plans | Reports and CSAT. Reports and CSAT |
| Full comparison | Sellio vs Zendesk | Sellio vs Freshdesk |
Tickets from $95 a month
Priced per workspace, not per seat or per ticket. AI use past the included credits is extra.
Every feature, for growing support teams.
All the Mini features, plus:
- AIAI turns a chat into a ticket
- AICustom voice for the AI agent
- Analytics
- AI resolution & handoff rates
- CSAT ratings
- Up to 25 automations
- Ticketing system
- Voice replies in the widget
- Advanced analytics
- Scheduled reports
Bigger limits and no Sellio branding.
All the Essentials features, plus:
- Unlimited automations
- Remove Sellio branding
The shared inbox and chat widget start free; tickets come with Essentials. See every plan
Ticketing questions
Straight answers about when a ticket is raised, automation, linked customers, price and the API.
No. Conversations are the default; a ticket is raised only when work continues after the reply, which keeps the inbox fast and the ticket board meaningful.
Most support needs no ticket: answer from the inbox and resolve the conversation. Raise one from the thread when something outlives the chat: switch the composer to Ticket and give it a subject. The ticket stays linked to the conversation and the contact, so nobody loses the context.
How conversations become tickets is in the inbox docs.
Tickets for the work that outlives the chat.
Raise them from any conversation, track them by state and owner, and tell the customer when they are done.
No credit card required

