A ticketing system that starts from the conversation
Raise a ticket from any chat, WhatsApp message or email, give it a state, a priority and an owner, and tell the customer when it is done.
No credit card. Live in minutes.
What a ticket carries.
Everything the work after the reply needs, on one sheet that stays linked to the conversation it came from.
Ticket type
3 customer reports
Ticket attributes
Attachments
Links
Sent to 3 of 3 conversations
Workflow
Tickets, last 30 days
Raised
84
Solved
71
Open backlog
13
Median time to solve
5h 20m
Raised from the thread, on any channel
The ticket keeps its link to the conversation it came from, and the reply goes back the way the customer wrote.
Website chat
The customer follows the ticket in the widget.
Email
The reply goes out from your own address.
WhatsApp
The reply lands back on the number they wrote to.
Instagram
Raised from the DM, answered from the DM.
Telegram
The bot tells them when it is done.
Slack
The thread stays in Slack while the ticket is worked.
Discord
Raised from a mirrored thread in your server.
Microsoft Teams
The Teams channel keeps the conversation in view.
Everything about it, on one sheet
Click any card on the board and the ticket opens beside it. The state is a dropdown, the owner a pill, and the whole story of the work is the feed under the subject.
- One sheet for the state, the owner, the notes and the files.
- Activity is a feed: who did what, when, in order.
- 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, checkout is rejecting some Visa cards. 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
Tickets
What the customer sees
The ticket follows them in the chat widget, in plain words: no states, priorities or notes, just where it is and who has it.
- Internal states become plain words: Open is Submitted, Solved is Resolved.
- The owner's first name, so the customer knows a person has it.
- Told in the widget and by email when it moves, and when it is done.
From chat to ticket to done
- Step 1
Raise it
In the conversation, switch the composer to Ticket, write what needs tracking, pick a kind and a priority.
ReplyNoteTicketRefund for order #4821 not received
CustomerUrgentRaise ticket - Step 2
Work it
On the Tickets board, filter by state, priority and assignee. Add notes and attachments as you go.
OpenUrgent
NurayRefund for order #4821 not received
#14212m2 notes1 file
Subscription charged twice this month
#1461h1 note
- Step 3
Close the loop
Set the final state and reply to the customer from the ticket. The conversation keeps the link.
#142 Refund for order #4821Solved
Refund sent, 3 to 5 days to your card.Sent to the customer on WhatsApp
What is a ticketing system?
Software that turns a customer request into a tracked item of work, with a number, a state, a priority and an owner, so nothing is forgotten between the first reply and the fix.
Most help desks make every message a ticket, which is why they feel heavy. Sellio keeps the conversation as the unit of support and raises a ticket only when work continues after the reply. Four terms carry the whole thing.
- Ticket
- A unit of work with a number, a subject, a state and an owner. In Sellio it is raised from a conversation and stays linked to it.
- State
- Where the work is: open, in progress, waiting, solved, closed. The board is the states as columns.
- Priority
- Low, normal, high or urgent. The same flag a conversation carries, so nothing is re-triaged on the way to a ticket.
- Owner
- The teammate the ticket is assigned to. Unassigned is the queue, and a workflow can assign on creation.
Ticketing questions
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.
Still have a question? Contact us or browse the 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