Inquiry Sales Script Library: Five Templates for First Response, Follow-Up, Quoting, Chasing, and Objection Handling
1. Why five categories, not twenty
Lay out a sales conversation and it looks endlessly varied, but there are really only five points: the buyer comes for the first time, the buyer doesn’t reply, the need is confirmed and it’s time to quote, the quote sits unsigned, and the buyer raises a concern. Standardize these five points and you cover over 80% of inquiry conversations. The remaining 20% are low-frequency, complex scenarios that go to a manager for one-on-one handling.
Here’s the counterintuitive part: the more detailed the template, the worse it gets executed. If every word is written out and the rep just reads it aloud, the buyer can tell it’s a robot at a glance. The right approach is a fixed skeleton with open sentences, so the rep fills in their own words within the skeleton. This is consistent with website copy tone guide‘s approach: standardize the structure, not the wording.
| Scenario | Trigger | Conversation goal | Number of templates |
|---|---|---|---|
| First Response | Within 5 minutes of inquiry submission | Confirm receipt + restate the need + give the next step | 2 to 3 |
| Follow-up | Buyer hasn’t replied for 2 days | Reactivate the conversation | 3 |
| Quotation | Need confirmed | Anchor value, then give a price range | 2 |
| Nudge | No movement 5 days after quoting | Offer a reasonable next step | 2 |
| Objection handling | Buyer says it’s too expensive / wants to compare / is looking elsewhere | Acknowledge first, then break it down | 4 to 5 |
The five categories add up to 13 to 15 templates, right in the “can actually finish reading” range. Once the library passes 20 templates, reps stop opening it. This is consistent with Sales Toolkit‘s organizing principle: few and precise beats many and messy by ten times. Awareness recognition decides which branch to take, see Identifying inquiry intent and responding differently.
2. First response template: three-part fill-in-the-blank
First response is the most important template in the whole library, because it decides whether the buyer is willing to reply. The structure is fixed in three parts: confirm receipt, restate the need, give the next step and deadline. Each part has just one blank for the rep to fill in.
| Segment | Skeleton sentence | Blank | Example fill-in |
|---|---|---|---|
| Confirm receipt | We received your inquiry about [___]. | Product model | the X-200 conveyor belt |
| Restate the request | It sounds like you need [___] for [___]. | Quantity + use case | 500 units for a packaging line |
| Next steps | I will send [___] by [___]. Does that work? | Deliverable + timing | spec sheet and MOQ by tomorrow noon |
A concrete example: the buyer’s email says only “quote your A-series belt.” Don’t open with a price. Reply in three parts: “Got your inquiry about the A-series belt. Sounds like you need the abrasion-resistant version for a food production line. I’ll send the spec sheet and MOQ by tomorrow noon. Does that work?”
The buyer replies “sure,” and the conversation is underway. For the full first-response SLA setup, see First-response SLA and conversion rate for inquiries.
3. Follow-up templates: three tracks by days of silence
Silence doesn’t mean the buyer isn’t interested. They may just be busy. Never open a follow-up with “Have you thought about it?” That’s the line buyers hate most. Instead, split follow-ups into three tracks by days of silence, and give each one a new piece of information rather than repeating the nudge.
| Days of silence | Follow-up goal | Sentence frame | New information |
|---|---|---|---|
| Day 2 | Light touch, no pressure | Following up on [___]. Any questions? | Attach a link to a spec table |
| Day 5 | Add a new information point | Thought you might want this: [___]. | A case study from their industry or a test report |
| Day 10 | Final attempt to re-engage | Should I close this file? Or keep it open? | Two options force a real answer |
The day-10 line “Should I close this file?” looks aggressive, but it gets more replies than “Have you thought about it?” because it gives the buyer a clear decision point instead of an open-ended question. For follow-up cadence and when to mark a lead dead, see Inquiry Email Follow-Up Sequence. For the ideal follow-up frequency, see Optimizing inquiry follow-up frequency.
4. Quote templates: anchor first, then quote
Leading with a price is the most common quoting mistake. The buyer anchors on the first number they see, and no amount of value explanation will undo it. The right order: spend one or two sentences anchoring value (our failure rate in this working condition, our lead time), then give a price range, then end with a hook that keeps the buyer talking.
| Steps | Content | Skeleton sentence | What to watch for |
|---|---|---|---|
| 1. Anchor the value | Set expectations with one hard number | For this load case, our belts run [___] hours before replacement. | Don’t say “good quality” — say hours |
| 2. Give a range | Quote three tiers by order quantity | For [qty], unit price is in the [__] to [__] range. | Don’t give a fixed price — leave room to negotiate |
| 3. Leave a hook | Suggest a next step | Want me to adjust specs to hit your target? | Put the ball back in the buyer’s court |
A concrete example: the buyer asks “how much is X-200 per meter?” Don’t reply “$X per meter.” Start with: “Under your heavy-load conditions, the X-200 lasts 18 months on average — 6 months longer than the standard version. At 500 meters, the unit price is between $A and $B. Want me to adjust the thickness spec to hit your target price?”
Now the buyer knows your quote isn’t a bare price — it’s a plan with service life and room to adjust. For the pricing logic, see Overseas Pricing, and for competitor comparison scripts, see Inquiry Competitor Comparison Scripts.
5. Follow-ups and objection handling: acknowledge first, then unpack
Follow-ups and objection handling often go hand in hand: when a buyer stalls on signing, there is usually an unspoken objection behind it. A follow-up is not about asking “when will you pay” — it is about offering a reasonable next step. Objection handling follows a three-step structure: acknowledge how the other person feels, unpack the real concern underneath, and suggest one small step forward.
| Common objection | Surface response | Real concern | How to unpack it |
|---|---|---|---|
| Too expensive | I understand budget is tight | They don’t see the value, or they’re comparing prices | Break it down to monthly cost of use, not total price |
| Let me shop around a bit more | You absolutely should compare | They don’t trust you | Send a verifiable test report |
| I’ve already found someone else | No problem, keep us in mind | They want a backup option | Don’t ask who won — ask what they’d need to switch suppliers next time |
| We have an internal approval process | What materials do you need from me | They’re stuck in the approval chain | Send the exact list of qualification documents required for the RFP |
The worst thing you can say in a follow-up is “there’s a discount right now” — that only trains buyers to wait for discounts. A good follow-up gives a time-limited reason that has nothing to do with discounts: “The price on this batch of raw materials goes up next Wednesday, so I’d suggest locking in the price before then.”
Or: “Our production schedule is full next month, so if you want to guarantee delivery, you’ll need to place the order this week.” These reasons tie back to cost — they don’t manufacture urgency out of thin air. For scripts by decision-chain role, see Scripts by decision-chain role for inquiries. For how to tell when an inquiry has gone cold, see How to win back inquiries that went cold.
6. How to keep your script library from going stale
A script library faces two big risks: nobody updates it after it’s built, and it keeps piling up. You write 15 scripts on day one, and six months later nobody uses them — because the market changed, the product changed, and the questions buyers ask changed. You need a fixed maintenance rhythm, or the library is just a dead document.
| Frequency | Action | Judgment criteria | Department head |
|---|---|---|---|
| Weekly | Manager spot-checks 5 real replies | Was a template framework used? | Sales manager |
| Monthly | Pull 3 new templates from closed deals | The reply led to a second conversation | Senior salesperson |
| Quarterly | Retire old templates with a reply rate below 30% | Used 5+ times, second-reply rate <30% | Manager + senior sales rep |
| Every six months | Reorganize the whole library, keep the total at 15 or fewer | Merge or retire anything beyond 15 | Sales lead |
The key metric here is the “second-reply rate.” If a template has been used more than 5 times and fewer than 30% of buyers reply on their own a second time, the template itself is the problem.
Either it misses the real need, or the wording puts people off — retire it instead of forcing it. For lead scoring and prioritization, see Lead Scoring and Prioritization for Inquiries. For how to A/B test scripts, see A/B testing inquiry scripts.
FAQ
How detailed should a script library be?
What exactly are the five template types?
Can I just give the price directly when quoting?
How long should a buyer be silent before I follow up?
How do I respond when a buyer says it’s too expensive?
How do I maintain the playbook so it doesn’t become a dead document?
Final thoughts
When it comes to playbooks, a lot of teams get it backwards: they spend two weeks writing a 50-template manual, drop it in the group chat, and then nobody ever looks at it again. The problem isn’t that they didn’t write enough — it’s that they wrote too much.
Your reps can’t memorize the scripts, and they won’t dare change them. A script library that actually gets used is a living document: 15 lines or fewer, a fixed skeleton, and three blanks for the rep to fill in. And it grows every month from replies that actually closed deals.
Three steps to roll it out. First, write 2-3 skeletons for each of the five scenarios, keeping the total under 15. Then have new reps practice by filling in the blanks for a week, with managers spot-checking whether their replies follow the skeleton.
Finally, set a maintenance rhythm: refine monthly, retire quarterly, using second-reply rate as the cutoff. Once the library is alive, new reps get up to speed in a week instead of relying on a veteran to coach them for a month.
One line worth remembering: a script library’s value isn’t in how many lines you write, but in whether reps will use it. Fixed skeleton, blank sentences, grows monthly, retires quarterly. 15 living templates beat a 50-page dead manual.