Customer support tickets
Keep the request, its status and its discussion in one record.
Create and maintain numbered tickets with requester, priority, team, assignee, tags and a conversation separating customer replies from internal notes.
A ticket should explain what remains to be done.
A support request often outlasts the first message. A ticket keeps its subject, requester and processing state available when another colleague needs to continue. Use a clear subject and meaningful status rather than treating ticket creation itself as progress. The conversation and recorded property changes help the next person understand the case without reconstructing it from disconnected private messages.
Capture the request with the right person and priority.
Create or receive a ticket with the requester and subject, then choose the appropriate priority, team and assignee. Tags can support the team's classification. CRM references are optional; the helpdesk does not require a customer database to create a request. Check the actual requester and relevant company rather than allowing a similar name or forwarded message to establish the relationship unquestioned.
- Numbered requests with priority, assignment and optional CRM references
Use status to communicate the real working state.
New requests can move through open, pending, on-hold, solved and closed states under the allowed transitions. Waiting states are different from solved work, and closed is terminal. Keep the explanation in the conversation so a colleague knows why the status changed. Record relevant property changes rather than changing fields simply to make the queue appear cleaner.
- Meaningful lifecycle states and recorded field changes
Keep the right conversation visible to the right audience.
Use public replies for the requester and internal notes for your team. Ticket visibility can be company-wide or team-based according to settings and authority. Read-only colleagues do not gain reply or update powers. Concurrent changes are checked against ticket revisions, so an outdated edit needs review rather than silently overriding a colleague's more recent change. Reopen the latest record when a conflict appears.
- Audience-aware replies, visibility and conflict-checked changes
A concrete workflow
Record
Confirm the subject and requester before triage.
Assign
Choose priority, responsible team and next person.
Discuss
Separate the public answer from internal investigation.
Update
Choose the truthful status and review the latest record.
An illustrative working example
Illustrative scenario: investigating an incomplete handover
A client reports that a handover document is missing. The ticket records the requester and responsible team. A colleague checks the delivery internally while another prepares the public reply. The ticket waits while the customer confirms the received version, then is marked solved after the issue is addressed. The trial checks that the owner, status and explanation remain clear to a colleague who did not read the original email.
Questions about this topic
Can a ticket exist without CRM?
Yes. CRM references are optional. Helpdesk keeps its own requester and ticket records.
Is pending the same as solved?
No. Waiting indicates unresolved work or dependency. Choose the state that reflects what remains.
Can read-only colleagues update status?
No. Ticket read access does not grant update or reply authority.
What if two people edit at once?
Revision checks reject outdated changes. Review the current ticket and apply the intended update again deliberately.
Explore connections around this workflow.
Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.
Zendesk
Application concept: Select one Zendesk case to compare requester identity, status meanings and retained conversation evidence.
HubSpot
Application concept: Review the correct HubSpot company association before adding customer context to a support request.
Slack
Application concept: Prepare a Slack handover naming the ticket and next action without exposing a private internal assessment broadly.