The workspace where your agents pick up what the AI hands over
Queue, macros, statuses, triggers: the tools of a full helpdesk, for the requests that need a human.
Klarodesk’s agent workspace is where your team handles the requests the AI hands over. The queue is organised into configurable views with live counts. Requests are routed to the right team based on their category, then to the least busy agent. Agents get macros with variables and actions, custom statuses grouped as in Zendesk (open, pending, on hold, solved), tags, custom fields and internal notes. Admins can add triggers and automations, email targets to forward a request to another department, fields required before solving, and automatic closing after a few days. A phone call can be logged as a ticket, and the interface installs like an app.
What it does
Configurable queue
Filtered views with counts, shared with everyone or with specific teams, so each agent sees what matters to them first.
Teams and assignment
Each category leads to a team, then the request goes to that team’s least busy agent.
Replies and actions in one click
Text with variables (customer name, ticket number…) plus actions: status, priority, tags, assignee.
Zendesk-style statuses
Create statuses under open, pending, on hold and solved. Solved tickets close on their own after 4 days by default.
Triggers and automations
React to every ticket change or act after a delay: status, team, message to the customer, email to agents.
Forward to another department
Email a request to another team or an outside body; their reply comes back on the ticket as an internal note.
How it works
- Set up your teamsLink each request category to a team and invite your agents.
- Prepare views and macrosDecide what each team sees first and save the replies you write most often.
- Add your rulesTriggers, automations, targets, fields required to solve and the auto-close delay.
- Work from the queueAgents receive handed-over requests with email or browser notifications, and can install the app.
What it doesn’t do yet
- No SLA tracking: contractual response times aren’t measured automatically.
- Attachments aren’t forwarded to email targets.
- No app store app: the interface installs as a web app (PWA).
Frequently asked questions
How does a request reach the right agent?
When the AI can’t answer, or when a rule says so, the request is handed to an agent. Klarodesk first looks at its category, which points to a team, then assigns it to the agent in that team with the fewest open tickets. A widget topic can also set its own team, priority and tags. The agent is notified by email or browser notification, depending on their preferences. Agents can always reassign a ticket to a colleague or to another team.
What’s the difference between triggers and automations?
As in Zendesk, a trigger reacts straight away to something happening on a ticket: creation, a change of status, priority or assignee, or a new message from the customer. An automation acts on elapsed time, for example a ticket pending for more than 48 hours, and runs every hour. Both share the same actions: change the status or team, add tags, write an internal note, send a message to the customer, forward to a target or alert agents by email.
Can a phone call be logged as a ticket?
Yes. The “New ticket” form lets an agent log a request received by phone: they look the customer up by phone number or email, or create them, pick the request type, team, priority and tags, then write the request or an internal note. They can apply a macro, let the AI answer first, or create the ticket directly with a status. Klarodesk doesn’t take calls itself, though: there’s no phone system.
Read next
Let the AI answer the repetitive questions. Keep your agents for the rest.
50 free requests when you sign up, every feature included. No credit card.