Topic / Routing

Turn context into a next step.

Routing connects a particular kind of work to an appropriate owner. The guides below consider customer intent, source permissions, impact, and the consequence of delay before assigning priority. They also discuss negative examples that keep a broad keyword from becoming an unnecessary interruption.

Begin with a narrow source and a short rule record. Write the expected action, test an ambiguous message, and keep the reason for each decision readable. A routing rule should be easier to understand after a handoff, not less clear because the message has moved between systems.

Read the guides in the context of the actual source and account involved. An example priority, receiving path, or handoff is not evidence of a live connection. Use the channel directory to compare boundaries before selecting a workflow.

8 related guides

Guides in this collection