Inquiry Response Workflow: Forms, WhatsApp, Email, and CRM

The short version #

An overseas inquiry is rarely a single inbox problem. Four channels have to work as one pipeline. Forms collect structured fields. WhatsApp carries the conversation. Email handles formal follow-ups. CRM is the single source of truth. First reply within one hour during business hours, by 10am next business day otherwise. Three-part template: acknowledge, ask one or two qualifying questions, commit to a timestamped next step. Grade leads into four buckets (urgent, normal, nurture, junk), each with its own SLA. With multiple reps, you need a rotation, a locking convention, and someone in the team chat saying "I've got this one." Otherwise two reps end up quoting the same buyer in two different ways and the buyer goes quiet. WhatsApp avatar, bio, and company name have to match the website exactly. Every week, mine the past seven days of inquiries for three signals and feed them back into the site. The table at the bottom is the version you paste into Notion for the sales team.

The pattern on most overseas launches: site goes live, WhatsApp button works, LinkedIn post gets traction. Then a buyer in Düsseldorf taps the WhatsApp icon, types "Hi, interested in your product," and waits. Nine hours later the sales lead picks it up in Beijing and replies "Hello, can you tell me more?" By that point the buyer is talking to three other suppliers. The deal is gone, and the website wasn't the reason. The workflow behind it was.

This post is for teams who've shipped the overseas site and the WhatsApp setup but haven't wired the sales process behind them. Not a CRM buying guide. Not a WhatsApp tutorial. The layer in between: who answers what, what the first message says, when to escalate, when to walk away.

Channel roles #

The four channels do different jobs. Treating all of them like "another contact form" is the first mistake.

• Form: collects structured fields. Name, company, email, target market, one-line need. The value is the schema. You know country, product line, and budget tier before the buyer says a word. More fields, lower conversion. Cap at five.
• WhatsApp: carries conversation. Buyers send "price?", "MOQ?", "still in stock?", not paragraphs. Optimize for response time and conversational quality, not field collection.
• Email: handles formal follow-ups. Quotes, contracts, spec sheets, PIs. After WhatsApp closes a point, restate it in email for the paper trail.
• CRM: holds the single source of truth. Every lead lands in one record, whether it came from the form, WhatsApp, or a trade show business card. CRM isn't a fifth channel. It's the glue.

A 2–3 person team should run form, WhatsApp, and email at minimum, with HubSpot Free or Pipedrive for the CRM layer. A solo founder can substitute a Notion table, but the schema has to be fixed.

For wiring WhatsApp into the website with form fields preserved, see How to Add WhatsApp to a Company Website.

First-reply templates #

Speed beats polish on the first reply. We benchmarked one client's pipeline: leads answered within 30 minutes converted to a quote at more than twice the rate of leads answered after four hours. Most reps still wait until the next morning, not because they're lazy but because they don't know what to put in the first message. Afraid of misquoting. Afraid of getting screenshotted. The fix is to make the first reply a template. Three parts:

1. Acknowledge: in the buyer's language, in one sentence. Skip "Dear Sir/Madam." Open with "Hi {name}, thanks for reaching out about {product}."
2. Ask one or two qualifying questions: don't quote yet. Pick the two that move the price the most. Target market, volume, repeat or first-time buyer.
3. Commit to a timestamped next step: "I'll send specs and a quote to your email within 24 hours." A specific time reads ten times more professional than "as soon as possible."

Version the template by channel:

• Form replies: quote the buyer's own fields back. "Saw you're sourcing for the {market} {industry} segment. We worked with a similar customer last quarter, here's the case." References like this outperform a generic template by a wide margin.
• WhatsApp replies: short sentences, no more than two lines each. A three-paragraph email template on WhatsApp reads as cold.
• Email replies: the full three-part template is fine, under 150 words. Attach a spec sheet or link a relevant case study below the signature.

After-hours, set an auto-reply naming the timezone and the next business hour: "It's outside business hours in {timezone}. We'll respond by {tomorrow 10am local}." Avoid the ChatGPT-flavored "Thank you for your inquiry, our team will respond as soon as possible." Buyers know what an LLM autoresponder reads like, and they read it as "this company doesn't care."

Lead grading #

Not every inquiry deserves the same time. Sort incoming leads into four buckets, each with its own SLA:

Stick this table next to every rep's monitor. The most common rookie mistake is treating junk as urgent (drafting a two-hour quote for someone who sent three emoji) while letting a real urgent lead slip until the next day.

Read the signals in the buyer's voice, not yours. A German buyer writing "We need a quote for {qty} units, delivery by Q3" is urgent. A Southeast Asian buyer asking "boss, best price?" might be price-shopping, or might be ready to issue a PO. Don't apply a domestic Chinese mental model to overseas leads.

Multi-rep rotation #

Two reps replying to the same WhatsApp inquiry from different angles, sending two different quotes. We've seen this more than once. The buyer's reaction is usually silence. They don't see your handoff; they see a chaotic supplier and move on.

Three things prevent the collision:

• Rotation schedule: in the buyer's timezone, not yours. Public LinkedIn data on German manufacturing buyers puts the procurement window at 9–11am and 2–4pm CET. Cover those slots with a primary and a backup, even if it means a 4pm-to-midnight shift in Beijing.
• Locking convention: rep A drops "I've got #INQ-2026-0428-03" in the team chat before replying. If your CRM has an owner field, set it first.
• Naming convention: every inquiry gets a unique ID like INQ-{YYYYMMDD}-{seq}. Use it in WhatsApp, the CRM, and the quote filename. When the buyer changes scope or the rep rotates, the ID holds the thread together.

For multi-rep WhatsApp, do not share one phone number across logins. Accounts get banned and history gets wiped. The WhatsApp Business Help Center states the Business App supports one primary device plus up to four companion devices, and treats long-term shared logins as a TOS violation. The right path is the WhatsApp Business Platform (API tier), routed through a CRM or a tool like Wati or AiSensy, so each rep has their own agent identity. See WhatsApp Business Setup Checklist and UTM Tracking for WhatsApp, X, Forms, and Email Leads.

Brand consistency #

When a buyer taps the WhatsApp button on your site, the avatar, company name, and bio they land on must match what they just left. This is the first trust check, and a lot of teams fail it before the conversation starts:

• Avatar on site is the brand logo. Avatar on WhatsApp is the rep's selfie.
• Company name on site is "Mansion Tech." On WhatsApp it's "Manxiang." On LinkedIn it's "Beijing Manxiang Technology Co., Ltd."
• WhatsApp bio is one machine-translated sentence: "We are a leading manufacturer providing high-quality products with global services." Reads like a template at first glance.

Before launch, build a brand-consistency table covering at least five surfaces: website hero, About page, WhatsApp Business profile, LinkedIn Company Page, X Professional Account. For each surface, lock the company name, logo, tagline, one-line description, address, and website URL. The setup specifics live in How to Set Up an X Professional Account for a B2B Brand and Overseas Social Profile Consistency Checklist.

Data flowback #

The last step in the workflow isn't closing the deal. It's feeding what buyers asked back into the website. Most teams skip this, which is exactly why doing it compounds.

Run a weekly inquiry review (30 minutes, Friday EOD) and pull three signals from the past seven days:

1. Questions buyers asked most: if five leads asked "do you ship to Europe by sea or air?", your service page doesn't answer that question. Add it to the FAQ.
2. Fields buyers filled in the "notes" box: your form doesn't have a "spec" field, but five leads pasted specs into "needs." Add the field. Next week's first-reply time drops by half.
3. Things buyers said they "didn't see": a lead asked "do you have ISO 9001?" The cert is on your About page, third scroll. Move it to the trust strip on the homepage.

Thirty minutes a week. After three months your service pages and FAQ will read noticeably more concrete than competitors'. SEO benefits in parallel — Google's Helpful Content guidance keeps making the same point: pages that answer real user questions tend to outrank pages built around keyword targets, which is the same content AI summaries look for. Page-level moves are in Corporate Website Conversion Checklist and How to Write Answer-Ready Service Pages.

Tool stack #

We don't promote any specific SaaS. Three typical combinations:

• Minimal (1–3 sales): site form → email + Notion + personal WhatsApp Business App. Near-zero cost, ~50 inquiries/month.
• Standard (4–10 sales): site form → HubSpot Free or Pipedrive + WhatsApp Business Platform via Wati/AiSensy + Google Workspace. $200–500/month, 200–500 inquiries/month.
• Advanced (multi-market): site form → Salesforce or HubSpot Pro + WhatsApp BSP + custom webhooks pushing UTM and form fields into CRM. $1,000+/month, unlocks real channel attribution.

Don't start with Salesforce. The most common failure mode isn't budget — it's process. Ninety percent of CRM fields end up empty and reps go back to Excel. Run the workflow on cheap tools first.

Reference table #

Paste this into Notion or a Lark doc. Hand it to every new rep on day one.

FAQ #

How fast does first response have to be? #

One hour during business hours, 30 minutes for urgent leads. Buyers usually talk to two or three suppliers in parallel. Replying first doesn't guarantee the deal, but replying late guarantees losing it. If the team can't sustain one hour, set up auto-reply plus a business-hours rotation first.

One WhatsApp number or several? #

Depends on team size. 1–3 reps can share a WhatsApp Business App number. Four or more requires the Business Platform (API tier) so each rep has an independent agent identity. Sharing a number across multiple logins is the fastest way to get banned.

Should the form ask for budget? #

Depends on the market. Western European and North American B2B buyers will fill in a budget field without much friction. Southeast Asian and Middle Eastern buyers tend to bounce. If unsure, A/B test for two weeks.

Can missed inquiries be recovered? #

Within 24 hours, yes. A "hey, sorry for the delay, still interested?" email pulls back about a third of cold leads. After seven days, don't push for the original deal — add them to the newsletter list instead.

Get a diagnosis #

If your overseas site and WhatsApp are live but inquiry conversion hasn't picked up, bring the past 30 days of inquiry logs, a screenshot of your CRM fields, and your sales rotation. We'll run this workflow against your real numbers in a free initial review under our overseas website build and SEO/GEO support service, and tell you which items are P0 (missed first replies, dropped WhatsApp threads) versus what can wait until next quarter (CRM upgrade, automation).