What you’ll get

Get a copy-paste RFQ blueprint that produces complete submissions and faster approvals.

• Fields that matter: the 7–9 inputs that reduce callbacks.
• Microcopy that calms: confidentiality, lead times, next-step promise.
• Routing that moves: on-site vs lab logic, timers, and SLAs.

Field spec (what to ask)

What you’ll get: A form spec you can copy—the few fields that get complete RFQs on the first pass.

Field	Why it matters	Example prompt (copy-ready)
Method(s) (multi-select)	Routes to the right team; drives required controls and quote logic.	Select: UT / RT / MT / PT / ET · Advanced: PAUT / TOFD
Material & geometry / thickness	Confirms feasibility and setup; affects dwell, magnetization, RT energy, UT technique.	Material + max thickness + longest dimension (e.g., “6061 Al, 12 mm, 520 mm length”).
Standard / customer spec	Sets acceptance criteria and documentation level; avoids rework.	List the spec (e.g., “ASTM E1417 Level 2; customer spec ABC-910, Rev C”).
Quantity & lots	Determines cycle time, batching, and price breaks.	How many parts? One lot or multiple? (e.g., “36 parts, 3 lots of 12”).
Access constraints	Impacts probe selection, MT/ET reach, RT setup; reduces surprises on-site.	Hidden surfaces? Weld length? ID/OD access notes (e.g., “ID access 50 mm only”).
Due date / need-by (+ rush toggle)	Sets SLA and staffing; shows rush capacity and fees before submission.	Target date + Rush? Y/N (we’ll show rush options if Y).
On-site vs. ship-to (+ address/region)	Triggers dispatch vs. lab routing and safety requirements.	Choose: On-site (city/site) or Ship to lab (we’ll send RMA).
Surface condition / finish	Determines PT/MT sensitivity and prep; affects timing and cost.	Machined, as-cast, painted, anodized, coated? (e.g., “as-machined, no coating”).
NDT level / sensitivity	Locks the correct technique (e.g., PT Level 2, MT fluorescent wet).	If known, specify: “PT Level 2, fluorescent; MT wet fluorescent; UT shear-wave.”
Previous findings / NCRs	Guides focus areas and reduces repeat discovery calls.	Known defect risks or prior reject notes? (attach page if helpful).
Uploads (drawings/specs/photos)	Lets engineering scope correctly on the first pass.	Upload PDF/DWG/STEP/JPG (≤25 MB each, up to 5). Please highlight acceptance notes.
Contact + company + role	Gives a responsible owner and sets the right follow-up (buyer vs engineer).	Name, work email, phone, role (Buyer/Engineer/QA). Extension if applicable.

Copy block (paste under your form)

Get a same-day scope check.
We quote to your standard (e.g., E1417, E1444, E213) and confirm turnaround before you commit.
On-site? Pick your region and we’ll route to Dispatch. Ship-to lab? We’ll send RMA + packing tips.

Microcopy & expectations

What you’ll get: Short lines that prevent hesitation—so more RFQs complete and approvals move faster.

Issue → Solution mini-blocks

• Issue: “Will you keep our drawings confidential?”
  Solution: Add a one-line promise + MNDA option.
  Paste: We sign MNDA on request. Drawings are stored in a restricted project workspace.

• Issue: “How long will this take?”
  Solution: Publish realistic ranges by method; show rush logic.
  Paste: Typical turnaround: PT/MT 2–3 days, UT/PAUT 3–5 days, RT 4–6 days. Rush shown after upload.

• Issue: “Who calls whom—and when?”
  Solution: Promise a named owner + time-bound next step.
  Paste: A project owner will contact you by 3pm local to confirm scope and schedule.

• Issue: “Do you actually meet the spec?”
  Solution: Put the spec ID in view and link proof.
  Paste: We perform per ASTM E1417/E1417M (see sample report) and maintain Nadcap AC7114 oversight.

• Issue: “What if this needs to be on-site?”
  Solution: Make dispatch criteria explicit.
  Paste: On-site work covers [regions]. Include access/badging and lift/safety notes for arrival readiness.

Microcopy examples (H4, drop-in)

Confidentiality (short)

We sign MNDA on request. Files are stored in a restricted workspace and never shared outside your project team.

Lead time (set expectations)

PT/MT 2–3 days · UT/PAUT 3–5 days · RT 4–6 days. Rush options appear after we review your files.

Next step (who/when)

Expect a scope confirmation call by 3pm [timezone] from your assigned project owner.

On-site work (what to include)

Add site access notes (badging, PPE, lift), work area photos if possible, and any safety brief timing.

Standards in view (trust)

We quote to your specified standard (e.g., E1417, E1444, E213/E273). See our certificates and sample reports before you submit.

Upload & safety notes

What you’ll get: Short callouts that reduce back-and-forth and keep on-site crews safe.

Accepted file types (keep quotes clean)

• PDF, DWG/DXF, STEP/IGES, JPG/PNG (≤ 25MB each, up to 5 files).
• Include: drawing with views, callouts for acceptance criteria, any prior NCRs or customer spec page.

Helpful photos (optional but valuable)

• Overall part (with scale), areas of interest, access constraints (e.g., manway, flange, weld run).
• For on-site work: work area (lighting, clearance), badge/PPE notes, lift/rigging situation.

Bold with a job: If a file affects safety or technique, call it out in the RFQ next to the upload.

Routing & SLAs

What you’ll get: Simple rules + timers so RFQs land with the right owner and move on time.

Process (1–2–3)

1) Intake & triage

• Auto-route by selections:
  • On-site = Yes → Dispatch (tag: region).
  • Method includes PAUT/TOFD → add Level III review.
  • Includes RT → add Radiation safety checklist.
• Timers: start T+0 SLA when form submits; set owner by T+1 hr (business hours).

2) Scope confirmation

• Owner calls by T+4 hr (or by 3pm local, whichever comes first).
• Confirms: standard, access constraints, files complete, turnaround.
• If gaps: send one-click request for missing items (templated email with upload link).

3) Quote & scheduling

• Send quote with options (standard vs rush) and earliest slot; include PO/credit terms.
• Thank-you page already shows ETA and owner; email includes calendar link.

Phone & email rules

• Regional DID on service-area pages → tagged as phone_click_region.
• Main RFQ line → IVR option “1: Mobile Dispatch / 2: Inside Sales.”
• After-hours: autoresponder promises callback window; voicemail transcribed to owner’s queue.

Autoresponder (copy-ready)

Subject: We’ve received your NDT RFQ — next step
Hi [first_name],
We’ve assigned [owner_name] to your request ([methods]). You’ll get a scope confirmation call by [callback_time].
What we have: [files_list]
What we still need (if any): [missing_items]
Need this on-site? We cover [region]. Otherwise we’ll send RMA + packing tips.
— [lab_name] | Certs & samples: [certs_url]

Thank-you page (what it should say)

• Header: Thanks — here’s what happens next.
• Owner + clock: Your project owner is [owner_name]. Expect a call by [callback_time].
• Links that help now: Certificates, Sample report (matching method), Turnaround times.
• If on-site: short arrival checklist (badging, PPE, lift, exclusion zone if RT).

SLAs (set & measure)

• Owner assigned: ≤ 1 hr.
• Scope call: ≤ 4 hrs (biz hours) or next business morning.
• Quote out: ≤ 24 hrs after complete files (≤ 4 hrs for repeat jobs).
• Tracking events: rfq_view, rfq_start, rfq_submit, owner_assigned, scope_call_done, quote_sent.

Do this → you get X: Clear routing + visible timers turn submissions into approved quotes faster, with fewer “any update?” emails.

Checklist + FAQ

What you’ll get: A final pass to catch missing fields, copy, and routing—plus quick answers to common objections.

☑ Final checks (ship-ready)

• ☑ Fields: Method(s), material/geometry, standard/spec, qty/lots, access constraints, due date/rush, on-site vs ship-to, uploads, contact/company/role.
• ☑ Copy: Confidentiality line, lead-time ranges, named owner + callback time, standards-in-view with links to proof.
• ☑ Uploads: File types/size listed (PDF/DWG/STEP/JPG, ≤25MB, up to 5), guidance on what to attach.
• ☑ Safety notes: RT exclusion zone checklist (if applicable), PT/MT cleanliness, UT/ET calibration/fixtures.
• ☑ Routing: On-site → Dispatch, advanced UT → Level III, RT → safety checklist; after-hours rule in place.
• ☑ Thank-you page: Owner + ETA shown, links to certificates, sample report, turnaround times, arrival checklist if on-site.
• ☑ Tracking: rfq_view, rfq_start, rfq_submit, owner_assigned, scope_call_done, quote_sent.
• ☑ Accessibility: Alt text on proof images, semantic table markup, readable contrast.

FAQ

Do we really need all these fields?

Yes—but keep it to 7–9 essentials. Each field prevents a follow-up email and speeds scoping. If it’s not used to route or price, cut it.

Should we show turnaround ranges publicly?

Yes. Simple ranges (PT/MT 2–3 days, UT/PAUT 3–5, RT 4–6) set expectations and reduce “is it done yet?” emails. You can still offer rush after review.

What if the buyer doesn’t know the standard?

Offer a “Not sure” option and ask for the customer spec page or acceptance notes. Your team can map it to the correct ASTM/NAS in the scope call.

Will posting certificates and sample reports create security risks?

Share redacted documents and limit identifiers. The upside—faster approvals and fewer procurement emails—outweighs the risk when handled properly.

Need Some Help Getting Started?

labDemand works with NDT labs just like yours to remove frictions in the funnel and get leads in your, or your SDR’s, inbox.