How to Triage Inquiries by Urgency: Spot Rush Orders, Shift Resources, Control Risk
1. Why you should grade inquiries by urgency
The problem for many DTC site teams isn’t too few inquiries. It’s not knowing which one to handle first. Every salesperson chases the deals that look urgent, so the genuinely urgent ones get ignored and the non-urgent ones get over-served. Without a grading system, resource allocation comes down to gut feel, and the busier the team gets, the more chaotic it becomes.
The point of grading by urgency is to put your limited sales and production resources where they matter most. When one customer says “I need it next week” and another says “I need it in three months,” your response speed, quote depth, and production priority should be completely different. Get the grading wrong and you either let a rush order die or lose money treating a regular order like a rush job.
| Tier | Response SLA | Share of inquiries | Owner | Production priority | Rush fee |
|---|---|---|---|---|---|
| P0 Critical | Within 2 hours | About 5% | Senior salesperson | Jump the queue | Required, 20% to 40% |
| P1 Urgent | Within 4 hours | About 15% | Sales team lead | Top 3 in the regular queue | Optional, 10% to 15% |
| P2 Normal | Within 24 hours | About 60% | Assigned salesperson | Scheduled by standard lead time | None |
| P3 Nurture | Within 72 hours | About 20% | Automated nurture sequence | No capacity reserved | None |
The percentages above reflect the typical inquiry mix for a B2B DTC site. Your team can calibrate them against your own historical data, but the grading logic stays the same: rush orders are always the minority, and most inquiries just need to be followed up at a normal pace. Use the grading system together with Lead Scoring and Prioritization for Inquiries When a lead scores high and is urgent, assign it to a senior salesperson first.
2. Spotting rush orders: three signals that tell you if it’s real
A customer saying “urgent” and an order actually being urgent are two different things. Plenty of customers want everything “ASAP,” and if you treat every one as a real rush, your team will burn out fast. A genuinely urgent order has three verifiable signals. All three together mean P0; two mean P1; one means P2; none means it goes into P3 nurture.
Signal 1: A clear deadline. The customer gives a specific date, like “we need it for the trade show next Tuesday” or “our line shuts down Friday.” A vague “as soon as possible” doesn’t count. Signal 2: A clear volume. The customer gives a specific quantity or annual spend, not “we might need.” Signal 3: An existing relationship. The customer is a repeat buyer, you’ve met at a trade show, or samples have already been approved. Of the three signals, two coming from a real project with an existing customer and one coming from a vague inquiry from a new customer carry completely different weight.
| Warning sign | P0 criteria | P1 criteria | P2 criteria |
|---|---|---|---|
| Deadline pressure | Specific deadline within 7 days | Deadline within 15 days | No clear deadline |
| Clear volume | Quantity or annual spend is clear and more than 10x MOQ | Quantity is clear but mid-sized | Volume is vague or very small |
| Existing relationship | Repeat customer or samples already approved | New customer but communication is smooth | First contact, incomplete information |
| Decision logic | All three signals = P0 | Two signals = P1 | One signal or none = P2/P3 |
Example: A German customer emails: “Our trade show opens in 10 days, we need 5,000 units, and we met you at the A show before.” All three signals hit: deadline pressure (trade show in 10 days), clear volume (5,000 units), existing relationship (met at the show). That’s an automatic P0 — a senior salesperson follows up within 2 hours and production is notified to reserve capacity. Another example: a US customer emails “Please send us a quote ASAP for your product” with no quantity, no deadline, and first-time contact. That’s P3 — just put it into the automated nurture sequence.
3. Shifting resources: how to slot in rush orders without wrecking regular ones
Once you’ve identified a rush order, the next step is shifting resources. The problem: rush orders cut into the lead time of regular orders. If there are too many P0 orders, every regular customer’s lead time slips, and in the end you barely profit from the rush orders while all your regular customers walk away. So you have to set a capacity cap.
Core rule: P0 orders must not take up more than 15% of the month’s capacity. Above that, you either turn down rush orders or raise the bar for rush fees. 15% is a rule of thumb — below 10% means you’re too conservative and may be losing big customers with genuine emergencies; above 20% means regular orders are being squeezed and your on-time delivery rate will fall.
| P0 share of capacity | Risk level | Your move |
|---|---|---|
| 0-10% | Security | Accept rush orders as normal, charge the standard rush fee |
| 10% to 15% | Warning | Rush fee up 5%, new rush orders need manager approval |
| 15% to 20% | High risk | Rush fee up 10%, turn down rush orders from non-repeat customers |
| >20% | Out of control | Stop taking new rush orders, clear the backlog first |
The other dimension of shifting resources is people. P0 orders must be handled by senior salespeople — don’t let new hires touch them, because rush orders leave little room for back-and-forth and new hires are liable to say the wrong thing. P1 orders go to a sales team lead, and P2 orders go to regular salespeople. Staffing and Inquiry assignment and load balancing The logic is the same: put your best resources on the deals that deserve them most.
4. Risk control: three traps of rush orders
Rush orders aren’t off-limits, but you have to work out the risk before you take one. The risk clusters in three places: missed delivery dates, quality slipping out of control, and rush fees eaten up by overtime while costs stay high. Plenty of salespeople promise any delivery date to win a rush order, then can’t deliver and pay the penalty.
Trap one: overpromising on delivery. The customer says “I need it Friday,” you say “no problem,” and by Thursday night it still isn’t done. The right move is to quote a date with buffer: if the customer wants Friday, you commit to Monday but tell them “we’ll do our best to get it out by Friday.” Leave at least 20% buffer. For the full framework on delivery commitments, see Delivery commitments and buffer design.
| Risk Points | What it looks like | Control measure |
|---|---|---|
| Missed delivery | Taking any order, then failing to deliver | Add 20% buffer to delivery, write penalty terms into the contract |
| Quality out of control | Rush orders skip QC | Rush orders still go through full QC, just prioritized in the queue |
| Profit erosion | Rush fee collected, but overtime costs more | Rush fee covers overtime plus 15% profit |
| Mismatched customer expectations | Customer thinks rush orders come with a discount | State clearly that rush orders cost more, not less |
| Existing customers squeezed out | New rush orders jump the queue and delay existing orders | Existing customers’ rush orders go first; new customers pay a higher rush fee |
Trap two: quality out of control. Rush orders are where quality problems hit most, because the schedule is tight and QC gets squeezed. The right move is to run rush orders through full QC, just prioritized in the queue, never skipped. Trap three: collecting a rush fee without working out the costs. The rush fee standard: compress delivery by 50%, add 20%; compress by 70%, add 40%. That covers overtime, schedule disruption and expedited materials, and leaves 15% profit.
5. Common misjudgments of urgency
| Misjudgment | Looks like | Actually is | How to handle it correctly |
|---|---|---|---|
| Every inquiry tagged P0 | Valuing the customer | Resources spread thin; nothing left for real emergencies | Grade strictly by the three signals |
| Customer says ASAP, so it’s rushed | Fast response | Being led by the customer’s wording | Verify the three signals before grading |
| No rush fee on rush orders | Maintaining customer relationships | Losing money on every order | Write the rush fee standard into the quote up front |
| Rush orders skip QC | Saving time | Getting it returned is slower | Prioritize rush orders in QC, don’t skip |
| No cap on P0 share | Turning no one away | Regular customers’ delivery dates all collapse | Cap P0 at 15% of capacity |
Of these five misjudgments, the most common is the second: the customer writes “ASAP” and you treat it as truly urgent. In a customer’s email, ASAP is basically a period, not a promise that they need it next week. Always ask three questions: deadline, quantity, and use. Once you have the answers, whether it’s urgent is obvious. For the full method of spotting urgency in inquiries, see Identifying inquiry intent and responding differently.
FAQ
The customer says ASAP. How do you tell if it’s really urgent?
What’s a fair way to charge a rush fee?
What share of orders should be P0?
What if a rush order jumps the queue and delays a repeat customer?
How do you tell if a rush order is a competitor fishing for information?
What do you do with a P0 rush order that comes in outside working hours?
Final thoughts
Grading inquiry urgency really comes down to one problem: your team’s resources are limited, and you can’t treat every inquiry the same. Split inquiries into four tiers, P0 through P3. Rush orders pay a rush fee, standard orders follow the normal schedule, and nurture leads get automated follow-up. Your whole team moves up a level in efficiency.
Three steps to put it in place. First, score every inquiry’s urgency using three signals, and only call it P0 when all three fire. Second, set a capacity cap: P0 no more than 15% of the total, and anything over that gets a higher rush fee. Third, write your rush fee standards into the quote template: 50% shorter lead time costs 20% more, 70% shorter costs 40% more, all clearly priced. Once these three steps are done, you won’t be led around by a customer’s “ASAP” anymore.
One line worth remembering: the loudest rush orders usually carry the thinnest margins. Rush orders pay a rush fee, P0 stays under 15% of capacity, and only an inquiry that hits all three signals deserves to be called urgent. Everything else is just “as soon as possible.”