Tickets that arrive with the customer's history.
Departments, email to ticket, saved replies and priorities, with the customer's services and invoices beside every ticket.
A desk per department, a mailbox per desk
Give each department its own address. Emails sent to it become tickets in that department, and staff are assigned where they belong.
Your forms open tickets too
Route the contact form to one department and the inquiry form to another. Open departments accept guests; the rest only your customers.
The history is already there
A ticket can name the service it's about, and staff see the customer's services and invoices beside the thread.
Urgent, when it's worth it
Normal, High and Urgent. Urgent can require a paid ticket credit, so priority support becomes something you sell.
Urgent tickets your customers pay for.
Priced on the server before checkout
Answer the common questions once
Saved replies for your team, and a knowledge base your customers search before they write.
Attachments, checked
Files sent with tickets are checked and re-encoded before they're stored, and you decide whether customers may upload at all.
Everyone hears what they should
Customers get an email when a ticket opens, gets an answer or closes; staff get one when a ticket arrives. A guest's first email never triggers an automatic reply.
Tickets in your team chat
Build it yourself
- ticket.created
- ticket.replied
- ticket.closed