Routing Manufacturer Enquiries to the Right Regional Rep: Setting It Up Step by Step
Short answer: Define each territory as a simple rule your form can evaluate, usually a postal code range or a state, add a fallback owner for anything that does not match, and let the system assign the enquiry, notify the rep and start a response clock. Then test with real addresses. The steps below take a small manufacturer from a shared inbox that someone forwards by hand to a routed queue where each rep sees only the enquiries they own and nobody waits for a manager to decide.
Step 1: Write the territory map as rules, not as a PDF
Many companies have a territory map that exists only as a coloured image or in a sales manager's head. A form cannot read that. Convert it into explicit rules:
- Each rep owns a list of states, provinces or postal code ranges.
- Where a rep owns a product line across all regions (for example, a specialist for marine fittings), record that as a separate rule that takes priority.
- Large accounts handled by a national account manager are listed by company name and override geography.
Write the rules in a spreadsheet with columns: rule order, field tested (postal code, state, product line, company), value, owner. Rule order matters, because the first matching rule wins. Put specialist and named-account rules at the top, then geography.
Step 2: Collect the fields the rules need
The form can only route on information it has. At minimum ask for:
- Company name.
- Postal code (or state) of the delivery or project location. Not the head office, which may be in a different region.
- Product line or application of interest, from a short list.
- Name, email and phone.
- A free-text description, optional.
Use proper autocomplete attributes on name, address and phone fields so phones can fill them in, as the MDN autocomplete reference lists. web.dev's address form guidance covers labelling and field order.
Make the postal code mandatory, and validate its format. A typo here sends the enquiry to the fallback queue and delays it.
Step 3: Add a fallback owner
Some enquiries will match no rule: a postal code you have not mapped, an overseas request, a missing field. Name a fallback person or shared queue, not a generic inbox nobody watches. Give the fallback a shorter response clock than a normal rep queue, since its job is to reassign quickly.
Also define what happens when the assigned rep is away. Options include a named backup per territory, or a rule that reassigns the enquiry after a set time without a first response.
Step 4: Assign, then notify in two places
When the form is submitted, the system should:
- Create a record in your CRM or tracker with all form answers.
- Assign the owner according to the rules.
- Notify the owner through the channel they actually read, usually email plus a mobile push or message in your chat tool.
- Copy a manager or sales coordinator for visibility, without making them a bottleneck.
Include in the notification a short summary: company, location, product, the enquirer's own words and a reply link. A rep who can answer from the notification alone is quicker than one who must log in first.
Step 5: Send the enquirer a useful acknowledgement
Within a minute, the enquirer should receive a message saying who will contact them and by when. Name the rep if you can. "Maria Torres in our Midwest team will reply within one working day" reassures far more than "we have received your enquiry". If the enquiry went to the fallback, say a team member will reply with the right contact, and do not pretend a specific person owns it.
Step 6: Start a response clock and escalate
Decide a first-response target, for example four working hours for enquiries marked urgent and one working day for others. Then make the system enforce it:
- At the halfway point, remind the owner.
- At the deadline, notify the manager and offer reassignment.
- After a second deadline, reassign automatically to the backup.
Keep the targets realistic for your staffing. A promise your team cannot keep is worse than a slower, honest one. Record the time of the first reply so you can report on it.
Step 7: Handle the awkward cases deliberately
- Distributors and existing customers. If the enquirer already exists in your CRM, route to their existing owner, not by geography. Match on email domain or company name.
- Enquirers from two regions. A company with plants in several states may want one contact. Put such accounts on the named-account list.
- Competitors and students. Add a quick triage option in the queue for non-commercial requests so reps are not distracted.
- Duplicate submissions. If the same email submits within a day, attach it to the earlier record instead of creating a second one.
Step 8: Test before launch
Create a test sheet of at least twenty cases covering each territory, each product specialist rule, a named account, a missing postal code, an overseas address and a duplicate. Submit each, and check:
- The right person was assigned.
- The notification reached them in under a minute.
- The acknowledgement named the right contact.
- The record contains every form answer.
Run the same test again whenever you change a territory. Reassigning territory changes is the most common time for the routing to quietly break.
Step 9: Review monthly
Look at three numbers: the share of enquiries that reached the fallback, the share reassigned after the first assignment, and the median time to first reply by rep. A high fallback share means the map has gaps or the form is collecting poor data. A high reassignment share suggests the rules do not match how the team actually works.
Keeping the map alive
Territories change when reps join or leave. Name one person who owns the spreadsheet, and require that any change goes through that person. Keep a dated copy of each version so you can see why an enquiry was routed as it was.
FAQ
Should enquirers choose their own region?
Better to let them enter a postal code and derive the region. A drop-down of regions invites mistakes, and visitors often do not know which territory they fall into.
What if two reps share an area?
Use alternation (round robin) between the two, or a rule by product line. Record which method you chose so reps accept the outcome.
Is it acceptable to assign by lead size?
Yes, if the rule is clear and written down. For example, route enquiries mentioning large quantities to a senior rep. Keep the rule visible to the whole team.
Do we need a CRM for this?
A shared sheet with an automation tool is enough to start, but a CRM keeps history and reporting in one place as the volume grows.
If your enquiries are still forwarded by hand, ask us to map your territories into a routing setup.