Route a deal by territory and round robin
Classify a matching opportunity and optionally assign the next eligible territory member.
Where to goSales CRM → Deals → Open a deal → Route deal
Before you start
Use your own authorised staff account in the intended Britixo workspace. The Sales CRM module must be available and your role must include the permissions stated above. Existing leads, customers, communications and customer portal pages retain their normal access rules.
Follow these steps
- Open an active deal and review the territories listed under Matches.
- Choose Route deal and select an active matching territory.
- Choose Keep the current owner to apply a classification only, or Assign the next eligible member to rotate ownership.
- Apply routing. Review the territory, deal owner, open activities and new history event.
- To remove the classification, choose Clear territory classification and Keep the current owner.
Behavior and limits
- Routing is explicit and does not automatically run when a deal is created or edited.
- The server rechecks the current deal, its revision and its territory conditions when applying the change. A stale or non-matching request is rejected.
- Round robin cycles through eligible staff in stable staff-ID order after the last assigned member, wrapping to the beginning.
- Inactive staff, staff without Sales CRM viewing permission, and staff who cannot access a linked customer or lead are skipped.
- The initiating user must also have access to all native links when reassigning. No recipient permission is expanded by routing.
- Open activities follow the new owner. Completed activities retain their historical owner. Pending stage approvals are cancelled on owner reassignment.
- Archived deals must be restored before routing.
Check it worked
- Check that the new owner can already access the linked customer and lead through their normal role.
- Review the Deal history event and ensure the selected classification or owner was applied once.
Troubleshooting
- No eligible member means membership or existing native access needs review. The deal is not partially reassigned.
- A second submission with an old revision is rejected and does not advance the round-robin queue.
- A previously assigned territory may remain visible after its rule stops matching; clear the classification or choose a currently matching territory.
