Start with a short routing table and one fallback queue. A routing rule should answer who owns the enquiry and what happens if the intended team cannot take it.
Use categories buyers recognize
Use choices such as a new quote, help with an existing project and something else. Avoid requiring customers to know the name of your internal department. If you need an existing ticket or order reference, make it optional for people who cannot find it.
Write rules that have an owner
Send new quotes to sales, existing work to the project queue and unclear enquiries to a named triage owner. An urgent request still needs a fallback. Define which working hours apply before promising any response window.
Track delivery and acceptance separately
Record that an enquiry entered a queue and that somebody accepted it. If nobody accepts it within your agreed interval, notify the backup owner or move it into triage. Include enough context that the new owner can act without searching multiple mailboxes.
Test exceptions in staging
Send an enquiry with no selected category and another while the primary owner is unavailable. Test whether reassignment triggers an unnecessary second customer email. Keep the first version small and add categories only when you can name a consistent owner.
Run a routing table exercise
Use four columns: customer selection, primary queue, backup queue and action if unclaimed. Test an existing client who mistakenly chooses New quote. The first owner should be able to transfer the record with its history intact, and the customer should receive only the acknowledgement the workflow intends.
See the lead follow-up automation guide for what should happen after assignment. Our workflow automation services can help connect routing rules with your existing systems.
