Customer notifications can’t be tailored per request type
Make a password reset and a major change read differently to the customer.
One notification voice for every request type confuses customers. Here is how to tailor the wording per request type.
The symptom
A simple access request and a high-risk change produce identical customer emails. The sameness buries the updates that actually matter and reads as generic.
Why Jira Service Management behaves this way
Customer notifications are configured once per project, not per request type, so every request type inherits the same content.
The manual workaround — and why it falls short
Admins write one notification that tries to cover every case, which ends up vague, or split request types across separate projects just to vary the wording.
How Patcher fixes it
Patcher lets you customise customer notification content per request type, so each request speaks to the customer in the right words and tone.
Turn it on
- Install Patcher for Jira Service Management from the Atlassian Marketplace.
- Open Patcher › Patches from your Jira Service Management admin.
- Find Per-request-type notifications in the list and switch it on.
- Scope it to the projects you choose, then save — the fix is live immediately.