All channels in one queue
Email, your portal, web forms and the API arrive as numbered tickets in one list.
Tickets
A shared inbox your clients can trust.
Every request gets a number, an owner and a clock.
app.hookdesk.ai/tickets
Fictional example dataWhy teams use ticketing
Status rules that never hide work
Tickets reopen when a client replies, so nothing sits unseen in a closed folder.
Collision detection
See when a teammate is viewing or replying to the same ticket.
Views and saved filters
Save the filters you use every day and pin them to your menu.
Bulk actions with Undo
Change many tickets at once, with 60 seconds to undo.
How it works
1
Capture
Each request lands in the queue with its own number.
2
Assign
Set an owner and priority; the SLA clock starts from your business hours.
3
Reply
Reply or add an internal note, with ten seconds to undo a send.
4
Resolve
Close the ticket when the work is done; the client sees it in the portal.
Works with
Planning
Plan tickets against real capacity.
Explore planningAutomations
Rules that suggest; people decide.
Explore automationsClient portal
Branded requests, approvals and share links.
Explore client portalQuestions
Can clients see internal notes?
No. Internal notes stay with your team. Clients only see replies.
What happens when a client replies to a resolved ticket?
The ticket reopens and returns to the queue.
Can two people reply to the same ticket by mistake?
Hookdesk shows who else is viewing or replying, so you can hand over first.
Make next week realistic.
Set up in 10 minutes. Bring your team when you’re ready.