Help Desk Ticketing Software
Repzo Help Desk: Run support with tickets, seven SLA metrics, priority targets, saved replies, escalation workflows, and satisfaction surveys in one help desk.
Repzo Help Desk keeps each issue as a ticket with a type, priority, status, and owner. SLA policies set the deadlines, workflows handle routing and escalation, and a linked inbox conversation lets agents reply to the customer from the same record.
Support and service teams that need every customer issue tracked, on a deadline, with a clear owner.
Seven SLA metrics with targets set by priority
Intake from email, chat, social, phone, and the API
Problem and follow-up links between related tickets
What this page is built around
Run support with tickets, seven SLA metrics, priority targets, saved replies, escalation workflows, and satisfaction surveys in one help desk.
Capabilities
Core workflows teams can run inside Help Desk
These pages are anchored in the actual product shape across the frontend routes, backend models, and documented workflows in this workspace.
Teams typically use Help Desk to:
- Handle customer issues with priority queues and SLA deadlines
- Link incidents to the problem ticket behind them
- Run a service desk for teams inside your company
See what needs attention by status, priority, team, and assignee
Get a warning 15 minutes before a target is missed, and escalate with a workflow you control
Answer faster with saved replies, and keep internal notes out of the customer's view
Ask for a rating after resolution, then report on volume, status, assignee, and average score
What's included
Everything Help Desk covers
- Tickets
- Types: question, incident, problem, and task
- Statuses: open, in progress, pending, resolved, and closed
- Five priorities, from low to critical
- Custom properties, snooze, and pending reasons
- SLA policies
- Seven metrics, from first reply to total resolution
- Apply by type, priority, channel, team, category, or tag
- Pending pauses the clock, except for requester wait
- Warning and breach events that can start a workflow
- Routing and automation
- Assign by round robin, least busy, random, or AI in a workflow
- Escalate by changing priority, assignee, or status
- Create tickets automatically for each email channel
- Deploy AI agents to tickets
- Working the ticket
- Internal notes that do not count as replies
- Saved replies that insert text
- Customer replies through a linked inbox conversation
- Merge duplicates, with undo
- Satisfaction and reports
- 1 to 5 star email survey, off by default
- Sent 1 to 7 days after resolution, once per ticket
- Ready-made reports by status, priority, assignee, and time
- Average rating across tickets
- Access
- Separate view, create, update, delete, and assign permissions
- Rights limited to a person's own tickets
- Separate permissions for SLA policies
- Arabic ticket screens
Workflow
How teams typically move through Help Desk
Tickets arrive from a connected email channel, an inbox conversation, the API, or an agent
A policy sets deadlines by priority, and a workflow assigns the ticket by round robin, least busy, or AI
The agent replies through the linked conversation and resolves the ticket, and the customer can rate it
Related modules
Stronger when connected to the rest of the platform
Each feature page links back to adjacent workflows so search traffic lands on a real product ecosystem rather than an isolated marketing leaf.
Omnichannel Inbox
A team inbox for WhatsApp, email, social messages, web chat, and calls. Assign conversations automatically, match them to CRM contacts, and link tickets without leaving the inbox.
Explore moduleAnalytics
Built-in reports and dashboards give you real-time visibility into sales performance, team activity, pipeline health, and revenue trends.
Explore moduleContent Hub
Create and manage internal and external content, from customer-facing help centers to team handbooks. Rich editor, version history, scheduled publishing, and a beautiful public reader your customers will love.
Explore moduleFAQ
Questions teams ask before adopting Help Desk
Does Repzo support SLA policies?
Yes. A policy can set seven metrics: first reply, next reply, periodic update, pausable update, requester wait, agent work, and total resolution. Targets are set by priority, and a policy can apply by type, priority, channel, team, category, or tag.
Where can tickets come from?
Tickets can come from a connected email channel, from inbox conversations on chat, social, and phone, from the API, or from an agent creating one. There is no customer portal for submitting tickets today.
Can we automate escalation?
Yes. Workflows can run on ticket created, updated, status changed, SLA warning, SLA breached, and feedback received. An escalate step can change the priority, assignee, or status.
Can agents reply to customers from a ticket?
Yes, through a linked inbox conversation, and a customer's answer reopens the ticket. This needs the Inbox & Calls add-on. Internal notes stay private and do not count as SLA replies.
Can we measure customer satisfaction?
Yes. You can turn on a 1 to 5 star email survey that goes out 1 to 7 days after a ticket is resolved, once per ticket. Reports show the average rating.
Can we merge duplicate tickets?
Yes. You can merge tickets and undo the merge. Splitting one ticket into two is not available.
Which plan includes the help desk?
Tickets and workflows are part of the Pro plan. Replying to customers through the inbox needs the Inbox & Calls add-on.