Define a rule in four parts.
Situation:
What has happened or what the customer is asking for.
Condition:
What makes this request different from the standard case.
Next step:
Who should handle it and what they should do.
Review:
How you will check that the rule works as intended.
Start with common exceptions.
- Billing question: Route it to the team authorised to handle billing.
- Missing information: Ask for the detail needed before giving an answer.
- Unclear policy: Have a person check the case and flag the knowledge gap.
- Customer asks for a person: Provide a clear handoff.
- Test a normal request, an exception, and overlapping rules. Confirm supported triggers and actions during setup; these examples describe a process, not a guarantee of automatic execution.
