Build a demo-request triage rule for a small sales team

A short routing rule that gets each demo request to the right seller before the buyer cools off.

Build a demo-request triage rule for a small sales team

Start with the decision the queue must support

A demo request queue exists to answer one question quickly: who should talk to this buyer, and when. Write that question at the top of the rule so the team does not turn triage into a second qualification process. The rule should produce an owner and a response deadline, not a long debate about whether the lead is good. When the queue cannot answer that question, it becomes a place where requests wait for a meeting.

Ask the sales leader which requests currently sit unresolved and why. Most delays come from a missing account owner, an unclear segment, or a request that arrived after hours. Use those examples as the test cases for the rule. If the rule cannot route the examples, it is not ready to publish, even if the spreadsheet looks complete.

Define a qualified demo request

A qualified request has a named person, a work email, a company, and a reason to see the product. The reason matters more than the job title because it tells the seller what to prepare. Requests that only ask for a brochure or a recording belong in a different queue. Keeping those out protects the calendar without insulting the buyer.

Write the definition in plain language and put it beside the form, not only in the sales playbook. Buyers should know what happens after they submit, including the expected response window. A definition that the marketing team cannot apply consistently will create arguments at the handoff. Test the form against the definition before changing the routing rule.

Route by segment before round-robin

Segment rules should decide the pool of sellers before round-robin decides the individual. If enterprise requests go to a general queue, the most junior seller may receive the largest account by accident. Define the segment from fields the form already collects, such as company size or region, and keep the number of segments small. Every extra segment adds a failure point at the moment of routing.

Round-robin within a segment only when the sellers have comparable capacity and coverage. If one seller is on leave or already at capacity, the rule needs an explicit fallback. Record the fallback so the request does not bounce between owners. A simple overflow owner is more reliable than a perfect capacity model that nobody maintains.

Set a response clock and an owner

The clock should start when the request is submitted, not when someone notices it. Define the response as a real attempt to contact the buyer, such as a call or a personal email, rather than an automated acknowledgment. Give each segment a target that the team can meet on a normal day. Targets should reflect coverage, not aspiration.

Name one owner for the queue and one backup for each shift. The owner is accountable for exceptions, not for every message. When a request passes its target, the owner should see it on a short daily list. A visible exception list is more useful than a dashboard that nobody opens.

Handle requests that arrive out of hours

Decide whether the team will respond after hours or on the next business morning. Write the answer into the buyer-facing confirmation so expectations match reality. If the team promises same-day response, the shift schedule must support it. A promise the team cannot keep is worse than a slower, honest window.

For high-value requests that arrive late, use a simple on-call rule rather than a general expectation that everyone watches their phone. The on-call seller should have the context needed to reply, including the form answers and account history. Record who was on call so the handoff is clear the next morning. Out-of-hours coverage should be a deliberate choice, not an unspoken habit.

Record the reason for every reassignment

Reassignments are where routing rules quietly fail. Require a short reason when a request moves to another seller, such as wrong region, capacity, or existing relationship. The reason should take seconds to select, not a paragraph to write. Without it, the team cannot tell whether the rule is working or the sellers are correcting it by hand.

Review reassignment reasons once a month and group them into a few categories. A recurring reason usually points to a field the form does not collect or a segment the rule does not cover. Fix the rule before asking sellers to be more disciplined. The goal is fewer manual corrections over time, not a perfect audit trail.

Review the rule when pipeline changes

Routing rules age quickly when the team hires, changes territory, or launches a new product. Put a review on the calendar after any change to coverage or segment definitions. The review should check a sample of recent requests against the current rule. A rule that was correct last quarter may send the wrong buyer to the wrong seller today.

Invite one seller and one marketing owner to the review, because each sees a different failure mode. Sellers see slow handoffs while marketing sees incomplete forms. Compare their examples and change one thing at a time. A small, tested change is easier to reverse than a full rewrite.

Publish the rule where the team works

Keep the rule in the same place as the queue, not in a folder that only managers open. A one-page version with the definition, segments, clock, and fallback is enough for daily use. Link the longer playbook from that page for anyone who needs detail. The team should not have to remember a rule they cannot see.

Review the page at onboarding and after every change, and note the date of the last revision. Retire old screenshots and outdated routing tables so nobody follows a stale version. The test is simple: a new seller should be able to route a request correctly without asking a colleague. If they cannot, the page is not finished.

Sources

  1. Occupational Outlook Handbook: Sales managers, U.S. Bureau of Labor Statistics. Describes sales manager responsibilities and the operating context for lead routing.
  2. Market research and competitive analysis, U.S. Small Business Administration. Outlines a practical process for understanding customer demand before sales investment.
  3. Business Trends and Outlook Survey, U.S. Census Bureau. Provides business conditions context for demand and coverage planning.

Related GTM guides