Customer support / Example workflow

Customer support

Verify the ticket. Confirm the follow-up.

Check that the ticket exists and has an owner. Test the next action and the update the agent sends to the customer.

Try the workflow Book a workflow review

Record who will
follow up, and when.

Try a case

Check the next action.

Change either check.
Read the next step.

Check whether the ticket exists.

Tickets & follow-upC–041

“Please create a ticket and make sure someone follows up.”

Customer request: Captured
Ticket creation: Attempted

Confirmed factsTicket ID verifiedA real ticket exists in the system of record.Follow-up owner assignedA responsible person has the case context.

Expected next step

Ticket creation unconfirmed

Check whether the ticket exists.

Check whether the ticket was created before retrying. Keep the assigned owner informed. Tell the customer that creation is still being checked; send a ticket ID only after verifying it.

The rule

Check the system result before reporting success.

Case statusCreation unconfirmed

See the records and open checks

Available recordsCustomer request, attempted action, system result and follow-up ownership.

Still to confirmA verified ticket ID from the system of record.

Do this nextFind or create the ticket, verify its ID, then confirm it to the customer.

Why this check matters

Check the result before you report success.

Check the ticket record after requesting creation. A timeout or missing ID means you still need to confirm whether the ticket exists.

Assign someone to follow up and agree when the customer will next hear from them.

Give the agent instructions for each failure: what to check, who to contact and what to tell the customer. Test these steps before using the workflow.

Service intake workshop with a tagged device and open repair case awaiting review. — Service intake is one setting where a ticket needs a clear owner.

Turn the case into a test

Show the reasoning
behind the rule.

Have your team approve the rule. Give developers the case, the action to expect and the result to check.

01
Check the records.
Read the customer’s request. Check the ticket system for a real ticket ID and the assignment record for the person responsible for follow-up.
02
Ask the expert to explain.
Ask the support specialist when to retry, how to avoid duplicate tickets and which team to contact when the result is unclear.
03
Agree the rule.
Verify the ticket ID before confirming creation. Assign someone to follow up. Promise only an update time that person has agreed.
04
Write and review the test.
When a creation attempt returns no ticket ID, check whether the ticket exists. Tell the customer that creation is still being checked. Do not report success.

When someone must take over

Make the handoff clear.

Send the records and completed checks. Tell the reviewer what is missing and what they need to decide.

Put these instructions in the development brief. Test that the agent follows them.

Example testNot run