Understanding this example
The sample ticket asks to change an appointment. The workflow identifies scheduling as the category, prepares context and assigns the request to the scheduling team. Classification and a completed appointment change are separate outcomes.
Use this distinction when planning support automation. It can be useful to prepare a draft or recommend a category while keeping the final response with a person. The team needs the original request, a clear owner and a visible unresolved state if the handoff fails.
Read the complete sample sequence
Use Next step above to explore the preview, or read every stage below. Selecting a stage changes the explanation shown; it does not perform that action.
A support request
Inbox: Sample ticket #1042: I need help changing my appointment.
Sort and understand
Automation: Category: Scheduling. Priority: Normal. Suggested response prepared for review.
A person takes over
Support team: Assigned to the scheduling team with the customer's request and relevant context.
What to look for
- The incoming ticket has a specific request and a sample identifier.
- The suggested category and priority are visible for review.
- The final step assigns ownership instead of claiming the appointment was changed.
What happens when the request changes?
Test scenario: The request combines a scheduling change with a billing dispute.
A connected workflow should preserve both concerns and use the appropriate escalation path. A single scheduling label must not hide the dispute or automatically authorize a refund.
What this demonstration does and does not do
Ticket #1042 is fictional. This preview does not access an inbox, reveal customer records, assign a real ticket or reschedule an appointment.
Prepare for a connected version
A production workflow needs agreed access, ownership and recovery behavior. Bring these details to discovery:
- Ticket categories and the person or team responsible for each.
- Approved answers and the requests that always need review.
- A queue for unassigned, uncertain and failed-routing cases.
Continue with How to plan a RAG chatbot around your business knowledge for a deeper planning checklist.
Published by FindSolution. These examples explain a design choice; they are not client case studies or evidence of a live integration. Read our editorial approach.