Operate a public-service request inbox with Zammad
Design a Zammad public-service request inbox with routing, restricted groups, accessible intake, private notes and a synthetic service-desk acceptance set.
Last updated
In short
- A request inbox coordinates service work; it does not decide legal outcomes.
- Group access and article visibility need separate negative tests.
- Public forms and notifications must minimize unnecessary personal data.
On this page (7)
Business workflows · Part of Public sector
Synthetic routing, privacy and communication cases for a service-desk pilot.
Download the public-service intake test setDefine the service boundary and the human owner
A public-service request inbox can give incoming messages a reference, responsible team, status and visible next action. Zammad can support that coordination. It should not be presented as automatically deciding eligibility, statutory deadlines or a citizen’s legal rights. Those decisions remain with the responsible authority and its approved process.
This is a reference workflow and synthetic acceptance exercise, not a deployed public-service system or an accessibility certification. Confirm the channels, supported languages, retention policy and any statutory process requirements with the service owner before configuring automation.
Start with a small routing model
| Request category | Initial group | Human decision | Public response |
|---|---|---|---|
| General information | Service desk | Answer or route to specialist | Acknowledgement and reference |
| Infrastructure report | Operations intake | Validate location and responsibility | Receipt without promising repair time |
| Appointment request | Appointment team | Confirm available process | Next step through approved channel |
| Sensitive personal case | Restricted intake | Identify authorized case handler | Minimal acknowledgement |
| Misrouted or unclear request | Triage | Ask only for necessary clarification | Clear explanation of next action |
Do not include sensitive case details in notification subjects or broad distribution lists. The routing category can be useful without copying a complete personal narrative into every alert.
The Zammad group documentation explains that a ticket belongs to one group and group permissions control agent access. It also notes that users are global to the instance. If strict separation of customer directories is required between organizations, evaluate that architecture explicitly rather than assuming ticket groups create complete tenant isolation.
Design intake around necessary information
Collect a contact route, request category and enough information to route the case. Make optional fields genuinely optional where the service allows it. Explain why any sensitive attachment or identifier is needed and direct high-risk submissions to the approved channel.
Provide a usable alternative to the web form, such as an approved email, telephone or assisted service process. Test keyboard navigation, field labels, errors, screen-reader announcements and mobile layout with the actual intake interface. If a custom form creates tickets through the API, its accessibility, spam protection, authentication and input validation are separate implementation responsibilities.
Record supported languages and how translated messages are reviewed. An automatically translated acknowledgement should not alter a deadline or promise that the service owner has not approved.
Configure automation with explicit conditions
Zammad’s trigger documentation describes condition/action rules, their execution behavior and the default acknowledgement trigger. Review existing triggers before adding another so one request does not receive multiple acknowledgements.
| Rule | Condition | Action | Guard |
|---|---|---|---|
| Initial acknowledgement | New eligible incoming request | Send reference and next-step information | Do not repeat on every update |
| Category routing | Valid selected category | Assign intended group | Unknown category stays in triage |
| Sensitive intake | Approved sensitive category | Restrict handling group | No broad notification body |
| Waiting for requester | Agent explicitly requests information | Set agreed waiting state | Avoid implying legal closure |
| Overdue internal review | Organization-defined operational target | Notify responsible team | Separate from statutory deadline calculation |
Keep the legal or policy deadline calculation outside a generic example unless the authority supplies and validates the rule. Internal service targets and formal deadlines can differ.
Protect internal notes and outbound communication
Zammad articles have type, sender and visibility settings. The article documentation warns that an internal flag does not make an email silent: an email can still be sent. Use the correct note type and recipient behavior, and test with synthetic addresses before enabling integrations.
Create an internal case note with a unique harmless marker. Confirm that an authorized agent can read it while the requester cannot see it in the portal, email thread, attachment list or API response. Repeat with an agent outside the restricted group. Test the actual role and channel combination rather than relying on a lock icon in one screen.
Run the service-desk acceptance set
The downloadable fixture contains fictional requests only. Use it to exercise routing and communication without processing real citizen information.
| Scenario | Required result |
|---|---|
| General question | One reference, correct group and clear acknowledgement |
| Duplicate submission | Staff can identify and reconcile it without losing either message |
| Missing contact detail | Visible exception and approved follow-up path |
| Sensitive request | Restricted group and minimal notification content |
| Internal note | Hidden from requester and unauthorized agent |
| Wrong attachment type | Clear safe handling or rejection process |
| Requester replies | Correct existing ticket/thread updated |
| Agent unavailable | Ownership can be reassigned without losing history |
| Channel outage | Accepted messages are reconciled after recovery |
Measure the real handling process: receipt, triage, assignment, response and closure. Reports should distinguish unresolved work, waiting-for-requester states and completed requests. Avoid presenting a raw ticket-close count as evidence of service quality.
Plan retention, recovery and rollout
Use retention periods and access-review rules supplied by the organization. Include ticket text, attachments, email copies, exports, logs and backups. Closing a ticket is not the same as disposing of its data.
Pin Zammad and integration versions, record the selected support arrangement and verify any channel-specific dependencies. Back up the database, files, configuration and required secrets. Restore into isolation with outbound messages disabled, then reconcile mail received during the outage before resuming intake.
Pilot one service category with a named team and retain the previous intake path during the acceptance window. Assign a single owner for each channel to avoid duplicate processing. If rollback is needed, stop target sending and preserve all new requests and replies before returning to the prior process. Accept the service when routing, access, communication, accessibility review inputs and recovery all have accountable evidence.
Sources and further reading
Use the linked documentation to confirm the version, edition and contract that apply to your project.
