Zendesk
A support workspace for collecting, assigning, and routing tickets, with checked responses the team can reuse.
Find a practice for your job below. See when this tool helps and what to check before using it.
Visit the official siteBest fit
Where it can help
- Collecting issue context through custom ticket fields.
- Assigning tickets to a named person or group.
- Applying reviewed macros to repetitive cases.
Limitations
What to check first
- Form, routing, macro-sharing, and permission features vary by plan.
- Required fields can collect unnecessary personal data if the form is not reviewed.
- Macros need owners, review dates, and human judgement before use.
- AIWorkDex does not receive ticket data. Use the organisation’s approved account and retention controls.
Pricing context
Check current prices and terms
Plans and feature availability change. Check current official pricing before configuration.
Practices using this Tool
See how to use it
Customer Support
Structure, triage, and reply to a vague support message
Produce an owned issue record and a customer reply that asks only for the missing facts.
Document client support ownership and update expectations
Give clients one contact path, one owner, and a cadence the service team can sustain.
Build a checked answer and escalation map
Give routine cases an approved path and send uncertain cases to an authorised person with useful context.
Review, decide, and close a reimbursement request
Reach one supported decision, take the correct authorised action, and state the escalation route.
Sources
Read the sources for this tool
Check what the sources say about using it in these practices.