Skip to content
Splice Work

The Splice field guide

Email Template for Inquiry: Ask Once, Act Fast

Use the right email template for inquiry—service availability, scope, pricing, or a missing detail—with intake fields and reply-to-record guidance.

11 min readBy Splice Work

A cobalt clay clipboard leaning slightly left on an ivory floor viewed from a low three-quarter angle, four cream square tiles in a horizontal arc in front of it marked with an orange exclamation mark, a lavender checkmark, a crimson X, and a mint question mark, thin cobalt clay lines curving from the clipboard base to each tile.
Four fields requested, four fields to verify. One blank cell means one follow-up question.

Picture this: you send a supplier a quick note asking whether they can handle your project, leave out the dates and location, and spend the next week trading single-sentence replies before anyone has a real answer. The fix is not better writing skill — it is structure: knowing which fields to request, how to make a reply easy, and what to do with the answer once it lands.

This guide gives you four original templates built around that structure. Use an email template for inquiry to cover service availability, project scope, pricing, or a missing specific question. If you are looking for an email template for enquiry in a more formal or British-English context, these structures apply equally. Each template pairs with a simple intake record so the reply populates a form rather than disappearing into a long thread.


Your turn · A one-minute experiment

Which version of the intake record is correct after reading this supplier reply?

Fictional one-minute exercise. All business names, supplier names, dates, addresses, and quantities below are invented for practice.

The situation

FICTIONAL INTAKE RECORD SCENARIO Business: Renwick Events Co. (fictional) Operator: fictional character Sasha Teel, logistics coordinator Supplier contacted: fictional Brightside Tent Hire Template sent: Service Availability (Template 1) FIELDS SENT IN EMAIL: — Service: tent hire for outdoor reception — Dates: 6–7 June 2028 — Location: Calloway Park, fictional city Mervale — Quantity: two 10m x 15m frame tents — Constraint: setup must complete before 09:00 on 6 June SUPPLIER REPLY RECEIVED: "Hi Sasha — yes, we have both frame tents available for 6–7 June. We cover Mervale and can be on site by 07:30 on the 6th, so the 09:00 deadline is fine. One note: we will need a 3-metre vehicle access lane to the setup area. Crew confirmation will follow by 25 May." INTAKE RECORD RULES (from article): Mark Verified only when the reply explicitly confirms the field. If a field is not addressed in the reply, leave Verified blank. A blank Verified cell means send Template 4 for that field only.

Choose what you would do, then open it to see the reasoning. You can explore every option.

A · Version A — all five fields verified, plus next step.

Correct. The reply explicitly addresses every sent field. Dates: 6–7 June confirmed. Location: Mervale covered. Quantity: 'both frame tents available' confirms two tents. Constraint: 07:30 arrival confirms the 09:00 deadline is met. Service: tent hire confirmed. Next step: crew confirmation by 25 May. The article's intake record requires marking Verified only when the reply explicitly confirms the field — all five pass that test, and the next-step row is also populated. No Template 4 follow-up is needed.

B · Version B — quantity and constraint left unverified; send Template 4 for both.

Wrong. The supplier's reply does address both fields. 'Both frame tents available' directly confirms the two-tent quantity. '07:30 on the 6th, so the 09:00 deadline is fine' directly confirms the constraint. Leaving these cells blank misreads the reply and generates an unnecessary follow-up. The article is clear: a blank Verified cell is the trigger for Template 4 — only genuinely missing fields qualify. Sending Template 4 when the reply already answered the question wastes the supplier's time and undermines the one-question-only discipline the template is built around.

Verifying an intake record means reading the reply against each sent field explicitly — not assuming omission when the answer is present in different words. A misread reply that triggers an unnecessary Template 4 follow-up defeats the article's core goal: ask once, get what you need, act.

Why Most Inquiry Emails Stall

A vague subject line, a paragraph of context nobody asked for, and a closing question like "just let me know what you think" are a guaranteed recipe for a delayed, incomplete reply.

Salesforce's sales email template guidance frames a template as a starting point, not a finished email, built from four elements: a greeting, a low-stakes opening question, your contact information, and one clear call to action. That four-element skeleton keeps the message scannable and makes it easier for the recipient to reply completely the first time.

The other common failure is omitting the fields you actually need. If you ask "are you available?" without specifying dates, service area, or quantity, the reply is "probably yes, tell me more." You have created a loop, not an answer.


Four Original Templates

Each template below includes annotated placeholders in [brackets]. Each placeholder is labeled by type — (date), (location/service area), (quantity), or (constraint) — so you understand why the field is present, not just what to fill in. Replace every placeholder with a real value before you send. The templates do not assume purchase intent — an inquiry is a request for information, not a commitment from either side.

If your inquiry includes promotional content or is primarily commercial in purpose, the FTC CAN-SPAM Compliance Guide is worth reading before you send. Its rules cover commercial messages regardless of whether you are emailing a business or a consumer, and primary purpose determines whether a message qualifies as commercial — an honest question about availability with no promotional content could be treated differently from a pricing inquiry paired with a product pitch. When a message is or may be commercial, include an opt-out line and a physical address; the templates below do this so you stay consistent regardless of how any particular message is categorized.


Template 1 — Service Availability

Subject: Availability check — [service type], [date range], [location or site]

Hi [first name],

I'm looking into [specific service] for [project name or brief description].

A few details to help you respond:

  • Dates needed: [start date] to [end date] (date)
  • Location / service area: [city, postcode, or site address] (location/service area)
  • Estimated quantity or scope: [e.g., 40 hours, 200 sq ft, 3 rooms] (quantity)
  • Constraint: [any hard deadline, site access restriction, or equipment requirement] (constraint)

Could you confirm whether you have availability for those dates and whether the location is within your service area?

If you need anything else from me to give a firm answer, please list it and I'll get it to you the same day.

[Your name] [Title, company] [Phone] [Physical address]

To stop receiving emails from us, reply with "unsubscribe" and we will remove you promptly.


Template 2 — Project Scope

Subject: Scope question — [project name], [your company]

Hi [first name],

We're planning [one-sentence description of the project] and want to confirm a few scope details before we go further.

What I'd like to clarify:

  1. Does your service include [specific deliverable or phase]?
  2. What is excluded from a standard engagement of this type?
  3. Is there a minimum [quantity / duration / value] (quantity) that applies?

Background that may help you answer:

  • Site or context: [location, environment, or platform] (location/service area)
  • Timeline target: [target completion date] (date)
  • Existing setup: [any relevant system, contract, or condition already in place] (constraint)

A two or three sentence reply is completely fine — I just need to know the scope boundary before we move to the next step.

[Your name] [Title, company] [Phone] [Physical address]

To stop receiving emails from us, reply with "unsubscribe" and we will remove you promptly.


Template 3 — Pricing Information

Subject: Pricing inquiry — [product or service], [quantity or scale]

Hi [first name],

I'm putting together an internal estimate for [project or purchase] and need pricing information to complete it.

What I'm looking for:

  • Unit or package price for [specific item or service tier]
  • Whether volume applies at [quantity] (quantity) units / hours
  • Payment terms you offer (net 30, deposit, milestone, etc.)

Context for your quote:

  • Quantity: [number] (quantity)
  • Delivery or start date: [target date] (date)
  • Location or delivery address: [location] (location/service area)
  • Any special requirement: [e.g., certification, format, lead time] (constraint)

I'm not asking for a formal contract — just enough to know whether the numbers work before we take the next step together.

[Your name] [Title, company] [Phone] [Physical address]

To stop receiving emails from us, reply with "unsubscribe" and we will remove you promptly.


Template 4 — Unanswered Specific Question

Use this when you have already received a reply but one critical field came back blank or ambiguous.

Subject: Quick follow-up — [the missing detail], re: [original subject line]

Hi [first name],

Thank you for your earlier reply. One detail I still need before I can move forward:

[State the single missing field plainly — e.g., "the lead time for the custom size," "whether the price includes installation," or "the service area boundary for your northern team."]

If the answer depends on something I haven't told you, let me know what you need and I'll send it straight back.

[Your name] [Title, company] [Phone] [Physical address]

To stop receiving emails from us, reply with "unsubscribe" and we will remove you promptly.


Turning the Reply Into an Intake Record

The real failure mode is not a bad template — it is a great reply that disappears into an inbox. Before you send any inquiry, write down the fields you need the reply to confirm. When the reply arrives, check each one.

Here is a minimal intake record you can keep in a spreadsheet or copy into your CRM notes. Mark only the fields you actually sent in your chosen template — the table below uses Template 1 (Service Availability) as the example:

FieldSent in emailReturned in replyVerified
Service / product requested✓
Dates / delivery window✓
Location or service area✓
Quantity or scope✓
Constraint or hard requirement✓
Next step from supplier

Worked example — reply arrives, record fills in.

Imagine you sent Template 1 to availability@example.com asking about landscaping availability for 12–14 March in Bristol, covering roughly 400 sq ft, with a gate-access constraint. The reply comes back:

"Hi — yes, we can do 12–14 March in Bristol. Our Bristol team covers that postcode. For 400 sq ft we'd schedule a half-day. Gate access is fine as long as we have a key or a code in advance. We'll confirm the crew by 5 March."

You fill in the record:

FieldSent in emailReturned in replyVerified
Service / product requested✓landscaping, half-day✓
Dates / delivery window✓12–14 March confirmed✓
Location or service area✓Bristol postcode covered✓
Quantity or scope✓400 sq ft, half-day✓
Constraint or hard requirement✓key/code needed by 5 March✓
Next step from suppliercrew confirmed by 5 March✓

Every field returned. Nothing to chase. If any cell in "Returned in reply" were blank, that is your cue to send Template 4 — one question, the missing field only.

What this record is not: It is not a purchase order or a contract. A supplier's reply confirming availability is information, not authorization to proceed. Keep the intake record separate from your approval workflow.

Quotation Follow-Through

Once you have a complete reply — every field checked — the natural next step is a formal request for quotation (RFQ) or a proposal. At that stage, the intake record becomes the brief: you already know the scope, the dates, the location, the quantity, and any constraints, so the RFQ does not need to re-ask them.

A few things that belong in an RFQ but not in an inquiry email:

  • Delivery specifications and acceptance criteria
  • Payment schedule and invoicing requirements
  • Insurance, certification, or compliance requirements
  • Validity period for the quoted price

An inquiry email gets the facts. An RFQ locks them into a format a supplier can formally respond to.



Review Checklist Before You Hit Send

  • Subject line names the service or product and the date range or quantity — no vague "checking in"
  • Every field the reply must cover is stated explicitly in the body
  • The email asks one clear question (or a numbered list of three or fewer)
  • No language implies commitment or authorization from either side
  • Contact information is complete — name, title, phone, physical address
  • An opt-out line is included
  • You have created the intake record row before sending

When the Reply Arrives — and What Happens Next

Once replies start coming in, the second loop begins: reading each one, spotting interest, logging the outcome, and deciding who follows up. That is where a lot of small teams lose track.

If you are running outbound campaigns rather than one-off inquiries, Beep Beep — Splice Work's automated email follow-up agent handles the send-and-watch portion: it runs up to three follow-up waves, reads replies, and posts interested responses in Slack for a person to take over. On the reply side, the human boundary is just as firm: when a reply sounds like interest, Beep Beep surfaces it in Slack and tells your team to take over — it does not negotiate, set pricing, or book anything. That conversation stays with a person. It writes back every contact, wave, and reply status to Salesforce, so the intake record fills in without a second round of manual logging. Nothing sends until you approve the campaign card, and it stops the moment you say stop.

It reports what it can actually count from the send log — not open rates, which have been unreliable since mail clients started pre-fetching images — so the numbers you see are true ones.

For guidance on what to do when a specific reply arrives and you need to decide whether to draft a response, escalate, or hold, the AI email reply guide on the Splice Work blog walks through that decision.


Try It Now

Pick one inquiry you are currently stalling on — a supplier you haven't contacted, a subcontractor whose availability you need, a vendor whose pricing you haven't confirmed. Use Template 1 or Template 3 above. Fill in every bracketed field before you write a single original sentence. Send it.

Then open your intake record and check whether every field you need came back in the reply. Fill in the placeholders first, then personalize — the bracketed fields are a starting point, not a substitute for a sentence written to a real person. If one field is missing from the reply, send Template 4 — the single-question follow-up — the same day.

That is the whole system. One send, one record, one follow-up if needed.

More in this topic

Practical AI for small business

Show us one workflow. We'll show you the agent for it.

A 30-minute walkthrough on your actual systems, not a demo account. No deck.