AI System for Routing Dealer Enquiries by Territory Rules

The problem

When enquiry addresses, accounts, dealer authorisations and opportunity histories are held in separate sources, their fields must be matched by hand before dealer candidates and ownership conflicts can be prepared.

The channel sales manager must compare every suggested dealer candidate and ownership conflict with its source record; missing or conflicting evidence must not replace the final decision.

If a project location and billing address in different territories are not set aside for review, the opportunity could be given to the wrong dealer; the record must not proceed without a human decision.

What we set out to improve

• Time taken for draft dealer candidates and ownership conflicts, together with their supporting evidence, to reach the channel sales manager for review
• How records set aside for human review because the project location and billing address are in different territories are resolved
• Number of suggestions corrected after identifying a risk that the opportunity could be given to the wrong dealer

How the system works

1. 01 Retrieve the enquiry address, account, dealer authorisations and opportunity history from permitted sources using the record identifier
2. 02 Link source, date and version information to the shared work record
3. 03 Validate fields and units
4. 04 Prepare dealer candidates and ownership conflicts with their supporting evidence
5. 05 Check for an exception: the project location and billing address are in different territories
6. 06 Have the channel sales manager accept, revise or reject the suggestion
7. 07 Record the approved decision and its source in the processing log

Methods we used

• A source-identified common data schema for the enquiry address, account, dealer authorisations and opportunity history
• A decision structure that separates deterministic rules from AI suggestions
• A review screen showing dealer candidates and ownership conflicts alongside the underlying source evidence
• A mandatory human review queue when the project location and billing address are in different territories
• An event identifier that prevents duplicate processing

Where people stay involved

Data and security

Only the fields required for this decision should be processed from the enquiry address, account, dealer authorisations and opportunity history. Access to the source systems must be authorised separately from the channel sales manager role, and personal data, commercial information and technical secrets must not be passed into the model context unnecessarily. Reading, suggestions and human decisions must be logged separately.

Who this suits

Frequently asked questions