Support
Support tickets with deadlines that the whole team can see.
Client tickets are triaged into the right project and person, with response and resolution SLAs set by ticket type. Work on a ticket is tracked like any other task, so support effort shows up in timesheets and project costs.
Support · Tickets
SLA 96%- Payment page timing outUrban Grocer · Critical incident4 h left
- Can’t reset admin passwordBackwater Stays · How-toIn progress
- Export missing GST columnFinEdge · BugWaiting on customer
- Add a new clinic locationPhysio Plus · How-toResolved
Ticket status
- 01Open
- 02In progress
- 03Waiting on customer
- 04Resolved
- 05Closed
What you can do. Day one.
Triage queue
Team leads, PMs or the CTO set type, project, hours and assignee from a Needs Triage tab.
SLAs by ticket type
From 1 business day for how-to questions to 4–72 hours for critical incidents. Nothing is due more than 7 days out.
Tickets become tasks
Triage creates a task in the project’s Support module, and its timer feeds effort.
Breach warnings
Warnings as an SLA approaches, breach checks, and auto-close 7 days after resolution.
Public and internal replies
Reply to the client, or note something for the team only.
SLA health at a glance
A dashboard widget shows SLA health across the team.
Connected
Works with the rest of Apro OS. No integrations to maintain.
Each ticket lands as a task in the right project.
Explore ProjectsTicket history informs the AMC annexure the AI proposes.
Explore Contracts & AMCResolving within SLA earns points.
Explore GamificationMore in Deliver it
See your company
in one system.
Thirty minutes with the team that builds Apro OS and runs its own company on it every day.
- A walkthrough of Apro OS using a company like yours
- Your current tools mapped to modules, and what you can switch off
- Pricing for your team size