WhatsApp Sales Workflow Example: From Website Click to Follow-Up

The short version #

WhatsApp is a workflow, not an "add the button and the orders show up" channel. The workflow has seven stages: where the button lives, what it pre-fills, the five-minute first reply, a 48-hour qualification pass, structured quote and assets, two scheduled follow-ups, and a monthly loop that feeds buyer questions back into FAQs and service pages. Every step gets a UTM, a tag, and a timestamp. Otherwise at month-end you only know "WhatsApp pulled in 28 messages." You don't know which became a PI, which stalled at quote, which was never a fit. The piece below walks through the SOP we built for an anonymized client, a hydraulic-fitting exporter in Zhejiang. Button copy, message templates, and CRM fields are written out, not abstracted.

We rebuilt the English site for that factory in 2025. Their WhatsApp setup before we got involved was familiar: a green floating widget on every service page, no pre-filled message, replies sent from sales staff's personal numbers, customer notes kept in each rep's notebook. Once a week the boss asked "how's WhatsApp going?" and got "still chatting with a few." Three months in, they discovered a buyer in Singapore had exchanged 11 messages over three weeks and ended up ordering from a competitor. The rep handling that thread had traveled, nobody picked it up, and the trail went cold on day twelve.

That's not a communication problem. The workflow was just never defined. The SOP below replaced it. It has been running for almost a year, and dropped follow-ups are essentially zero.

1. Entry #

Three decisions determine the quality of every conversation that follows: where the button lives, what the copy says, and what message it pre-fills.

Put the button at the bottom of every service and case-study page, below the spec table on product pages, and above the second fold on the homepage. The little green icon in the global footer almost never gets clicked, so don't plan around it. One common mistake we see is putting the WhatsApp button in the top nav. Visitors who haven't even seen a product yet land in chat saying "Hi, I want to know more," and the rep restarts qualification from zero every time.

Skip "Chat with us on WhatsApp" as button copy. Use action verbs tied to the page:

• Service pages: Get a quote on WhatsApp →
• Spec pages: Ask about MOQ & lead time →
• Case studies: Discuss your project →

Use the official wa.me short-link format: https://wa.me/<number-with-country-code>?text=<URL-encoded-message>. The pre-filled text isn't "Hello." It carries the page context:

Hi Mansion Tech, I'm looking at the [Hydraulic Hose Series H320] page and would like a quote for [country/quantity].

The product name in that message gets injected dynamically through GTM or a server-side template. The visitor opens WhatsApp and the sentence is already typed; they fill two blanks and hit send. The cognitive cost of opening a conversation moves from buyer to seller, and you know which product page brought them in before they say a word.

For the button setup, How to Add WhatsApp to a Company Website has the field-level instructions. For the number itself, including business profile, catalog, and away messages, see WhatsApp Business Setup Checklist for Overseas Sales.

2. First reply #

Five minutes. That's the hard target we set for every overseas inquiry, on any channel. On WhatsApp the number matters more, because the buyer has their phone open right now. Miss the window and you wait for them to reopen the app, which might be tomorrow.

Five minutes doesn't mean send a quote. It means do three things:

1. Acknowledge: a short reply that proves a human is on the other end. Hi [Name], thanks for reaching out about the H320 series. I'm [Your Name] from Mansion Tech.
2. Ask one specific question: not open-ended. Could you share your country and the rough monthly volume you're planning? or Are you sourcing for a project, or for stock?
3. Set the next expectation: I'll send a detailed quote and the spec sheet within 4 hours during my working time (GMT+8).

We keep three first-reply templates pinned in the sales group: quote requests, technical questions, partnership inquiries. The rep picks one based on which page sent the pre-fill and is back to the buyer in two minutes. This isn't bot scripting. It saves the rep from rewriting an opener thirty times a day, so their attention goes to the parts that actually need judgment.

3. Qualification #

Once the buyer replies, you have 48 hours to decide whether this lead deserves more time. Roughly 30 to 40 percent of overseas B2B inquiries aren't a fit. MOQ too low, market we don't serve, the buyer is actually shopping for an agent rather than purchasing, or it's pure price comparison.

A minimal qualification table, five fields:

You don't ask all five at once. The first two go in the next message after the first reply; the rest get woven in alongside the spec sheet and quote. Push these into your CRM (we use HubSpot's free tier now; we used Lark Bitable before) and every later decision references this row.

A "not a fit" lead isn't deleted. We send a polite email explaining why this round doesn't work, with one hook for staying in touch. Plenty of teams skip this and call it a waste of time. We've watched it pay off enough times to keep doing it. Today's small agent who can't hit MOQ becomes the largest distributor in Vietnam two years later.

For the wider multi-channel triage logic, see Inquiry Response Workflow: Forms, WhatsApp, Email, and CRM.

4. Assets #

Once qualified, send the assets. WhatsApp has its own traps here:

• Don't push a 50 MB PDF. WhatsApp caps file sizes and overseas networks make downloads painful. Break the spec sheet into a one- or two-page summary and link to your product page (you'll see clicks in GA4 too).
• Don't dump twelve photos. Pick two or three that matter. Everything else lives behind a case-study link.
• Quote in structured text, not Excel screenshots. Type it directly into WhatsApp:

Quote for H320-12 Hydraulic Hose
- MOQ: 500 m
- Unit price: USD 2.40 / m (FOB Ningbo)
- Lead time: 18 working days
- Payment: 30% deposit, 70% before shipment
- Sample: 5 m free, freight on you

Full spec sheet: https://yourdomain.com/products/h320-12
Project case in Vietnam: https://yourdomain.com/cases/vn-2024-hydraulic

Every link carries UTM. Our format is ?utm_source=whatsapp&utm_medium=chat&utm_campaign=h320-quote&utm_content=<sales-id>. A month later we can answer: which rep's links get clicked most, which product line converts best post-quote, which case studies actually move deals. Field-level UTM patterns in UTM Tracking for WhatsApp, X, Forms, and Email Leads.

After the assets ship, tag the lead in the CRM: stage:quoted and next-action:follow-up-d7.

5. Follow-up #

After the quote, three reactions are possible: same-day reply, reply within 3–5 days, or no reply. The first two follow normal conversation rhythm and don't need a SOP. The third one (silence) covers most leads, and it decides whether this whole workflow ships orders.

Our cadence is 7-21-60:

• Day 7: a specific, non-pushy message. Hi [Name], wanted to share — we shipped a similar order to a Vietnamese client last week and they confirmed the quality. Happy to send photos if useful. Or: Hi [Name], MOQ on H320 goes up to 800m next month because of the raw material schedule. Wanted to give you a heads up in case timing matters. Always with new information, never a bare "just checking in."
• Day 21: change angle. If they're a buyer, send technical content their engineering team would care about. If they're an engineer, send a simplified procurement-process or payment-terms note.
• Day 60: the final one. Say it explicitly: if timing isn't right now, we'll stop here, just keep our number. Roughly 10% of silent leads wake up at this message.

Each touch updates last-touch and touch-count in the CRM. Three silent touches and the lead moves to stage:cold. Out of the active pipeline, but still in the database for quarterly content sends.

We keep all follow-up scripts in a shared library, but every send has to replace [Name] and at least one specific fact, whether that's a product, a case, or a market shift. Templated but not robotic. That's the whole difference between WhatsApp and a mass email, and recipients can feel it.

6. Feedback loop #

Run the workflow for a month or two and the questions converge. On that hydraulic-fitting account, by the end of month two we'd logged 87 conversations and tallied:

• 41% asked about MOQ and minimum order
• 35% asked about lead time and shipping schedules
• 28% asked about samples and who pays freight
• 22% asked about warranty and testing standards

We pushed those four answers straight into the FAQ section of the product and service pages. Three months later the share of WhatsApp conversations re-asking MOQ dropped from 41% to 18%. The questions got answered before the buyer ever clicked the WhatsApp button, so that's not "improved communication" so much as removed friction. The visitors who did open chat were asking sharper, project-specific questions, and the close rate climbed from 6% to 14%.

This step has the highest ROI in the whole workflow and gets skipped most often. Sales says "that's marketing's job," marketing says "sales never sends us the raw questions." Our fix: last week of each month, sales exports the WhatsApp transcripts (the Business app has a built-in export), we run topic clustering through any LLM, the top five recurring questions get listed, and sales and marketing review together. Some go to FAQ, some to service-page body, some deserve their own blog post.

For writing service pages and FAQs that search engines and AI summaries actually want to quote, see How to Write Answer-Ready Service Pages.

7. Measurement #

Bosses ask "how many WhatsApp inquiries this month?" That's the wrong question. These five are the right ones:

We wire these into a Looker Studio dashboard built from GA4 events and CRM fields, and it auto-emails the sales and marketing channels every Monday morning. No "how the rep felt." Just numbers and the matching next actions.

UTM setup, event tracking, and cross-domain attribution live in UTM Tracking for WhatsApp, X, Forms, and Email Leads.

The whole flow on one page #

The table summarizes everything above. Print it and pin it next to the rep's monitor. That beats any "sales process training" deck.

FAQ #

WhatsApp Business or WhatsApp Business API for a small export team? #

Start with the WhatsApp Business App. It's free, runs on a single device plus the Web client, and is fine up to about 200–300 conversations a month. Beyond that, or once multiple reps need to handle the same number, move to the WhatsApp Business Platform (API). Access goes through a Meta-approved BSP, with per-conversation and template-message fees. Most small to mid-sized exporters don't need API in their first 12 months.

What happens when a rep leaves? The chat history is on their personal phone. #

This is the single biggest risk in running sales on WhatsApp. Three mitigations. First, every WhatsApp account runs on the Business App, never a personal number. Second, reps sync the 5-field qualification row and quote summary to the CRM weekly. Non-negotiable. Third, the company-owned number (not the rep's personal one) is the only outward-facing line, so the number stays when the rep leaves.

Buyers move from email to WhatsApp to phone. How do you track them? #

Stitch them in the CRM under one Contact ID; each channel is an Activity under that ID. Email links carry UTM, WhatsApp links carry UTM, phone calls get logged manually with date and a one-line summary. First-touch attribution is enough. Don't install a multi-touch attribution model on a small team. The maintenance cost outweighs the insight.

Any compliance concerns running WhatsApp into the EU? #

Yes. Under GDPR, you need explicit opt-in before contacting EU buyers (a buyer initiating chat counts as opt-in); storing WhatsApp conversation history has to be disclosed in the privacy policy; and you must offer deletion. The WhatsApp Business Platform docs spell this out. Get legal eyes on it before you go live in the EU.

Get a diagnosis #

If you're already running WhatsApp inquiries but the close rate is under 10%, or the reps each work in isolation and no one can give the same number twice, bring 30 days of conversation samples and a CRM screenshot. We'll walk through the table above with you in a free initial review under our overseas website build and SEO/GEO support service, and tell you which step is leaking leads, which can be patched with the tools you already have, and which actually justifies new tooling.