Support tickets that do not get lost
Not every problem needs a visit. A customer says the water tastes off or the pump is noisy. A ticket keeps the conversation, who owns it and how long it has waited, and can link to the visit or the system.
Illustration with sample data
The problem
Complaints in private chats
Problems arrive on personal phones. Nobody else can see them, and nobody knows which are overdue.
One queue
Every ticket with its status, priority, owner and age. Filter by what is unassigned, mine or overdue.
Response clocks
First-response and solution targets, counted in calendar hours or your business hours. The clock pauses while you wait for the customer.
Saved replies
Insert your usual answers with the customer's name and ticket number filled in. You still read it before sending.
Internal notes
Talk inside the team without the customer seeing it.
Linked work
Link a ticket to a system or a visit, within what each person is allowed to see.
Customers can follow it
They raise and follow tickets in the portal. They never see internal notes.
How it works
Three steps
- 1
It arrives
A customer opens a ticket, or staff open one for them.
- 2
It is handled
Assign, reply, link a visit.
- 3
It closes
Solved tickets close by themselves after your chosen days and can be reopened for a while.
Questions
About support tickets
Can I set response targets?
Yes. Priorities, hours and the targets are company settings.
Does a ticket turn into a job?
You can link a visit to a ticket so the work and the conversation stay together.
Can I export tickets?
Yes. The queue can be downloaded as a CSV file with the same filters.
Works together with
See it with your own kind of work
Book a short demo. Tell us what you service and how many people you have, and we will show you the parts that matter to you.