Inquiry Status Management: Lifecycle Definitions, Transition Rules, and Stalled-Deal Alerts
1. Six Statuses: Why Not Eight or Ten
Many teams run a dozen or more inquiry statuses in their CRM: Unassigned, To Be Contacted, Contacted, In Discussion, Quoted, Sample Stage, Sampling in Progress, Negotiating, Won, Lost, Invalid, Duplicate, Spam… It looks thorough, but in practice reps simply don’t update them. Changing a status takes three clicks, so they’d rather not click at all. The result: every inquiry sits at “In Discussion” and you have no idea where things actually stand.
| Status | Definition | Entry Condition | Exit Condition | Maximum Time Allowed |
|---|---|---|---|---|
| New inquiries | Just received, not yet assigned | Form submitted | Assign to a sales rep | 24 hours |
| Contacted | First response sent, waiting on the buyer | Sales rep sends the first reply | Buyer replied | 48 hours |
| In Discussion | Back-and-forth on needs and options | Buyer replied to the first response | Quote sent | 7 days |
| Quoted | Quote sent, waiting on the buyer’s feedback | Quote email sent | Buyer accepts or declines | 7 days |
| Closed deals | Order confirmed, contract signed | Buyer confirms the order | Final status, no further transitions | — |
| Close | No deal, follow-up ends | Clear rejection / invalid / timed out | Final status, no further transitions | — |
The design principle behind these six statuses: each one maps to a specific action, and the rep just clicks when that action happens. First response sent, click “Contacted”; buyer replies, click “In Discussion”; quote sent, click “Quoted”; won or closed, click the final status. You don’t need fine-grained stages like “Sample Stage” or “Sampling in Progress” in between. Those belong in the notes, not in the status field. The fewer the statuses, the more willing reps are to update them, and the more accurate your data becomes.
Example: an inquiry comes in, and the system starts it at “New Inquiry.” The rep sends a first response within 5 minutes and clicks “Contacted.” The next day the buyer replies asking for 500 units to Hamburg, and the rep clicks “In Discussion.” On day three the rep sends a quote and clicks “Quoted.” A week later the buyer confirms the order, and the rep clicks “Won.” The whole process took just four clicks, each one tied to a real action. That’s what makes the six statuses workable. For how the first-response SLA and status flow fit together, see First-response SLA and conversion rate for inquiries.
2. Flow rules: move forward only, no going back
Status flow has one hard rule: move forward only, never backward. You can’t jump from “Contacted” back to “New Inquiry,” or from “In Discussion” back to “Contacted.” If the buyer says “let me think about it,” that’s not going backward, it’s staying put — in “In Discussion” or “Quoted,” waiting for the next follow-up. Only two situations allow a rollback: the inquiry was assigned to the wrong rep, or it’s a duplicate. A rollback requires a reason; you can’t just click it.
| Flow action | Trigger | System action | Needs manual confirmation? |
|---|---|---|---|
| New Inquiry → Contacted | Rep sends first-response email | Timestamp logged automatically | No, one click by the rep |
| Contacted → In Discussion | Buyer replied to the email | Buyer reply detected, status updates automatically | No, automatic |
| In Discussion → Quoted | Rep sends the quote | Quote time logged automatically | No, one click by the rep |
| Quoted → Won | Buyer confirms the order | Triggers the contract process | Yes, manager approval required |
| Any → Closed | Clear rejection / invalid / timed out | A close reason is required | Yes, close reason required |
| Any rollback | Wrong rep / duplicate inquiry | A rollback reason is required | Yes, manager review |
The point of these rules is to prevent “status drift” — a rep dragging an inquiry that’s been open for three weeks from “Quoted” back to “In Discussion” just because nothing’s happened lately, pretending it’s still moving. That kind of drift makes you think the inquiry is alive when it’s actually dead. That’s why rollbacks need a reason and manager review — a rep can’t just roll one back whenever they feel like it.
A close reason is required, and it has to be categorized. There are five common close reasons: buyer declined (price too high / chose a competitor / no need right now), invalid buyer (spam / competitor / wrong contact info), no reply after timeout (three or more follow-ups with no response), duplicate inquiry (same buyer submitted twice), and other. Only by tracking close reasons by category can you see where your inquiries actually die — is the quote too expensive, or are you not following up enough? For how to design a follow-up sequence, see Inquiry Email Follow-Up Sequence.
3. Stalled inquiry alerts: a three-tier warning system
The real danger in status management isn’t messy statuses, it’s statuses that stall with no one watching. An inquiry sits in “Contacted” for two weeks, the rep forgets to follow up, and you have no idea. That’s how deals are truly lost. Stagnation alerts set a maximum dwell time for each status. Exceed it and an alert fires automatically, so no inquiry quietly dies.
| Alert level | Trigger | Notify | Required action | Escalation deadline |
|---|---|---|---|---|
| Yellow alert | 50% past maximum dwell time | The rep who owns the inquiry | Follow up within 24 hours | No follow-up in 48 hours, escalates to orange |
| Orange escalation | 100% past maximum dwell time | Rep + sales manager | Manager steps in to assess | No action in 72 hours, escalates to red |
| Red escalation | 200% past maximum dwell time | Manager must act | Manager follows up personally or closes | Must have a result this week |
Here’s a concrete example: the maximum dwell time for “Contacted” is 48 hours. Yellow fires at 72 hours (48 x 1.5), notifying the rep: “This inquiry hasn’t moved in 3 days, follow up.” Orange fires at 96 hours (48 x 2), notifying the manager too. Red fires at 144 hours (48 x 3), and the manager must handle it personally, either following up or closing it outright. This three-tier system keeps inquiries from dying unnoticed.
Maximum dwell time differs by status. “New inquiry” is 24 hours, because it hasn’t been assigned yet, and a slow assignment breaks your first-response SLA. “Contacted” is 48 hours, because if the buyer doesn’t reply in two days, they’re basically not interested. “In conversation” is 7 days, because if a week of back-and-forth hasn’t produced a quote, the needs aren’t aligned yet. “Quoted” is 7 days, because if a week passes with no feedback, either the price is too high or the buyer is comparison shopping. Every status’s maximum dwell time maps to the point where waiting any longer is pointless. For the full approach to lead scoring and prioritization, see Lead Scoring and Prioritization for Inquiries.
4. Common status management mistakes
| Mistake | What teams do | What actually happens | The right way |
|---|---|---|---|
| Too many statuses | 10+ granular statuses | Reps don’t update, everything sits in “In conversation” | 6 statuses, each tied to one action |
| No maximum dwell time | Statuses can sit forever with no oversight | Inquiries die quietly and no one notices | Set a maximum dwell time + alert for each status |
| Closing without a reason | Click close and you’re done | You don’t know where inquiries die | Closing reason required, tracked by category |
| Rolling back statuses freely | Reps roll back whenever they want | Status drift, unreliable data | Rollback requires a reason + manager approval |
| Alerts by email only | Alerts rely on email | Reps don’t read email, alerts fail | In-app popup + DingTalk/WeCom push |
Of these five mistakes, the sneakiest is the last one: alerts by email only. Reps get dozens of emails a day, and stagnation alerts get buried in the pile. The right approach is to push alerts to the rep’s home screen. The CRM dashboard shows “You have 3 yellow inquiries, 1 orange inquiry” the moment they open the CRM, no digging through email required. For dashboard design, see AI Engine Citation Monitoring Dashboard dashboard mindset.
The point of status management isn’t to make your CRM look tidy. It’s that one glance at the dashboard each week tells you how many inquiries are stuck, at which status, for how long, and which ones need a manager to step in. Status management without stall alerts is just a pile of numbers nobody reads. Connecting your website to your CRM is what makes status changes happen automatically; see Website leads to CRM.
FAQ
How many inquiry statuses should we set up?
How long can an inquiry sit in one status before it counts as stalled?
What status is it when the buyer says “let me think about it”?
Do we have to fill in a reason when closing an inquiry?
What if sales keeps changing statuses however they like?
How do you push stalled-deal alerts to sales so they actually work?
Final thoughts
Inquiry status management sounds like a CRM configuration issue, but it’s really your window into the pipeline. Without it, you only know how many inquiries came in this month and how many closed, not where you lost them along the way. With it, you can see at a glance: 30 inquiries are stuck in “Quoted” this month, and 12 of them have been sitting there for over a week. Those 12 are your bottleneck.
Three steps to make it work: first, cut your statuses down to 6, each tied to one action; then set a maximum time-in-status for each one, with three tiers of stall alerts; finally, require a reason for closing and track them by category. Once this is running, one look at the dashboard each week tells you who to talk to and where to push harder.
One line worth remembering: status management isn’t about making sales fill out forms. It’s about seeing at a glance which inquiries are stuck and for how long. Six statuses with three alert tiers will do ten times more for you than fifteen statuses and a dashboard nobody reads.