These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Public Grievance System
- Features
- Assignment
Assignment
Give each complaint an accountable person.
OverviewMy Assigned Tickets×
Public Grievance System · Assignment
New
My Assigned Tickets
Tickets
| Record number | Subject | Owner | Status | Resolution due at | |
|---|---|---|---|---|---|
| TCK-58774 | New tck-669 | New | 26 Oct | ||
| TCK-25111 | Triaged tck-870 | Triaged | 25 Oct | ||
| TCK-86155 | Assigned tck-557 | Assigned | 21 Oct | ||
| TCK-66041 | Waiting tck-863 | Waiting | 22 Oct | ||
| TCK-98072 | Resolved tck-738 | Resolved | 11 Oct |
6 of 6 records
New tck-669Tickets · TCK-58774
NewResolution due at26 Oct
What you can do
Keep the working record clear
A new complaint may be correctly registered yet still wait for a person to act. The Operations Manager checks the organization, priority and team roster before putting the ticket with a Service Agent. The agent receives the complaint record, its deadline and the context of the complainant. Assignment is a responsibility decision, so the chosen person must be active and within the relevant organization.
An agent’s personal work list follows the owner recorded on tickets. The broader board shows active states to help the manager see work across owners. If a case is waiting on information, the owner stays visible; waiting is not an excuse to lose responsibility. Reopened work returns to attention under the same record number, with its prior events available to the person now responsible.
How the work is organized
- Owner. The manager chooses an active service agent whose staff record belongs to the ticket’s organization.
- Work list. The agent follows assigned complaints by owner; the manager scans the active board across staff.
- Handoff. A changed owner takes over the same ticket and reads its earlier events before responding.
A waiting complaint stays with its named owner. When another agent takes over, the record number and due date give both people a common point of reference.
What to agree during setup
Agree who maintains team members and their linked users identities, which role names are eligible for case work, and how organization boundaries affect assignment. Set a practical handover routine for absence or overload. The manager should review priorities and deadlines along with the ticket count before moving work.
Check the handoff on an actual case
Give a sample ticket to an active agent, then inspect that person’s work list and the active board. Change the owner with an authorized manager and verify that the current ticket names the receiving person. Review the event record to explain what happened before handover.
Use the same sample to test a conflicting instruction and an authorized correction. The resulting record should tell the next handler what remains to do. Keep the earlier event or decision available when a case returns to work; otherwise the apparent current status can conceal an unresolved question.
What your team sees
- My Assigned Tickets — Find complaints owned by the signed-in agent and read the next due date.
- Active Ticket Board — Compare open work across owners and priorities.
Follow the work through
Follow complaint intake and case review to see how these records move between people. Use the data model when importing the first complaints and the roles page before granting access.
What it keeps track of
Data model- Tickets
- Intake and lifecycle record for each grievance ticket, with SLA dates, priority and revision guard.
- Team members
- Staff handling and reviewing grievances, resolved to an authenticated platform identity.
- Organizations
- Public bodies operating the grievance service, with their local time zone and reporting currency.
- Customers
- Complainants and affected parties who file grievances, with service address and eligibility note.
Who uses it
Permissions- Operations Manager
- , Service Agent, Intake Coordinator.
Set up Public Grievance System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.