Custom orders on WhatsApp
Spec capture, drawing approval, fabric / wood selection, milestone updates and final dispatch confirmation \u2014 turn 6-week custom orders into a single thread.
- Spec capture
- Drawing approval
- Milestones
- Dispatch confirm
Key things to know
Spec capture
Drawing approval
E-sign.
Fabric / wood select
Milestone updates
People also ask
Q.E-signature?
Yes.
Q.CAD / drawing format?
Image / PDF.
Q.Multi-language?
Yes.
Q.Milestone customisation?
Per-SKU.
Q.CRM sync?
Yes.
Q.Pricing?
See /pricing.
Custom orders fail when the thread breaks
A custom bedroom set takes 4–8 weeks. In that window 60% of customer anxiety is 'where is my order?'
WhatsApp milestone updates + drawing approval keep the customer informed and the thread closed.
Built for serious growth teams
Spec capture
Drawing approval
E-sign.
Fabric / wood select
Milestone updates
Dispatch confirm
Final invoice
Get live in days, not months
- 1
Spec capture in chat
- 2
Drawing + fabric approval
- 3
Milestone updates auto
- 4
Dispatch + delivery confirm
What teams ship with this
Custom sofa
Built-in wardrobe
Modular kitchen
Office bulk
Frequently asked questions
Why Custom orders on WhatsApp is the highest-leverage move for growth teams
WhatsApp is where growth teams customers actually reply. Open rates sit at 85–98% inside 15 minutes versus 18–22% on email and sub-2% on SMS, and the medium is conversational — a customer can ask a follow-up, share a photo, or pay without leaving the thread. That is the entire premise behind custom orders on whatsapp: stop losing the conversation to slow channels and let intent convert while it is warm.
Most growth teams teams treat WhatsApp as a broadcast megaphone. The teams that win treat it as a workflow surface — every notification is also a decision point where the customer can act. The capabilities below are wired to do exactly that: each one collapses a multi-step off-platform detour into a single in-thread reply.
The impact numbers on this page — -40% customer chase time, +0.6 csat lift, 85% read rate, 3× reorder rate — are pulled from LandinChat customers running this workflow for at least 90 days. They are directional; your mileage depends on list quality, template approval speed, and how aggressively you route qualified conversations to a live agent.
Each capability, in plain terms
Spec capture
Spec capture is delivered as a native LandinChat module — no external plug-ins, no separate dashboard. It ships pre-wired to the growth teams data model, so the first working version is minutes of setup, not a sprint. You can override defaults per campaign, per agent, or per customer segment. In practice this means the growth teams operator running custom orders on whatsapp does not need to compose the logic themselves; they pick the trigger, review the copy, and let LandinChat handle rate-limits, template compliance, and retry behaviour.
Drawing approval
Drawing approval is delivered as a native LandinChat module — no external plug-ins, no separate dashboard. It ships pre-wired to the growth teams data model, so the first working version is minutes of setup, not a sprint. You can override defaults per campaign, per agent, or per customer segment. In practice this means the growth teams operator running custom orders on whatsapp does not need to compose the logic themselves; they pick the trigger, review the copy, and let LandinChat handle rate-limits, template compliance, and retry behaviour.
Fabric / wood select
Fabric / wood select is delivered as a native LandinChat module — no external plug-ins, no separate dashboard. It ships pre-wired to the growth teams data model, so the first working version is minutes of setup, not a sprint. You can override defaults per campaign, per agent, or per customer segment. In practice this means the growth teams operator running custom orders on whatsapp does not need to compose the logic themselves; they pick the trigger, review the copy, and let LandinChat handle rate-limits, template compliance, and retry behaviour.
Milestone updates
Milestone updates is delivered as a native LandinChat module — no external plug-ins, no separate dashboard. It ships pre-wired to the growth teams data model, so the first working version is minutes of setup, not a sprint. You can override defaults per campaign, per agent, or per customer segment. In practice this means the growth teams operator running custom orders on whatsapp does not need to compose the logic themselves; they pick the trigger, review the copy, and let LandinChat handle rate-limits, template compliance, and retry behaviour.
Dispatch confirm
Dispatch confirm is delivered as a native LandinChat module — no external plug-ins, no separate dashboard. It ships pre-wired to the growth teams data model, so the first working version is minutes of setup, not a sprint. You can override defaults per campaign, per agent, or per customer segment. In practice this means the growth teams operator running custom orders on whatsapp does not need to compose the logic themselves; they pick the trigger, review the copy, and let LandinChat handle rate-limits, template compliance, and retry behaviour.
Final invoice
Final invoice is delivered as a native LandinChat module — no external plug-ins, no separate dashboard. It ships pre-wired to the growth teams data model, so the first working version is minutes of setup, not a sprint. You can override defaults per campaign, per agent, or per customer segment. In practice this means the growth teams operator running custom orders on whatsapp does not need to compose the logic themselves; they pick the trigger, review the copy, and let LandinChat handle rate-limits, template compliance, and retry behaviour.
How this actually rolls out
Step 1. Spec capture in chat
Spec capture in chat is the foundation of the custom orders on whatsapp workflow. On day one, an onboarding specialist walks a growth teams operator through this step live; on subsequent campaigns, the team runs it themselves from the LandinChat console. Expect this step to take between 15 minutes and an afternoon depending on how clean your existing data is.
Step 2. Drawing + fabric approval
Drawing + fabric approval is the next unlock of the custom orders on whatsapp workflow. On day one, an onboarding specialist walks a growth teams operator through this step live; on subsequent campaigns, the team runs it themselves from the LandinChat console. Expect this step to take between 15 minutes and an afternoon depending on how clean your existing data is.
Step 3. Milestone updates auto
Milestone updates auto is the next unlock of the custom orders on whatsapp workflow. On day one, an onboarding specialist walks a growth teams operator through this step live; on subsequent campaigns, the team runs it themselves from the LandinChat console. Expect this step to take between 15 minutes and an afternoon depending on how clean your existing data is.
Step 4. Dispatch + delivery confirm
Dispatch + delivery confirm is the final lock-in of the custom orders on whatsapp workflow. On day one, an onboarding specialist walks a growth teams operator through this step live; on subsequent campaigns, the team runs it themselves from the LandinChat console. Expect this step to take between 15 minutes and an afternoon depending on how clean your existing data is.
How different teams put this to work
Custom sofa
Custom sofa teams deploy custom orders on whatsapp to compress the gap between intent and action. The common failure mode we see is over-templating — sending the same broadcast to every segment. The teams that outperform run at least three variants keyed to recency, spend tier, and language, and they measure reply-rate not open-rate.
Built-in wardrobe
Built-in wardrobe teams deploy custom orders on whatsapp to compress the gap between intent and action. The common failure mode we see is over-templating — sending the same broadcast to every segment. The teams that outperform run at least three variants keyed to recency, spend tier, and language, and they measure reply-rate not open-rate.
Modular kitchen
Modular kitchen teams deploy custom orders on whatsapp to compress the gap between intent and action. The common failure mode we see is over-templating — sending the same broadcast to every segment. The teams that outperform run at least three variants keyed to recency, spend tier, and language, and they measure reply-rate not open-rate.
Office bulk
Office bulk teams deploy custom orders on whatsapp to compress the gap between intent and action. The common failure mode we see is over-templating — sending the same broadcast to every segment. The teams that outperform run at least three variants keyed to recency, spend tier, and language, and they measure reply-rate not open-rate.
Buyer’s checklist
- • Official Meta Tech Partner — templates approve faster and account is not at ban risk.
- • Native growth teams data model — no glue-code to import contacts, orders, or bookings.
- • Green-tick support with a clear submission checklist and Meta-side follow-up.
- • Conversation-based pricing that matches WhatsApp’s own billing model, not per-message surcharges.
- • Human handoff with unread routing, so qualified replies never sit in a bot loop.
- • Audit log & role-based access — required for regulated enterprise buyers.
Common pitfalls
- • Broadcasting cold lists — quickest way to a quality-rating downgrade and eventually a template ban.
- • Skipping opt-in capture — makes every future utility template harder to approve.
- • Treating WhatsApp as a one-way channel — the platform penalises accounts with low reply-rate.
- • Running only one template variant — you leave 20–40% of lift on the table.
- • Not routing hot conversations to a human within 5 minutes — kills conversion by up to half.
What to measure after launching custom orders on whatsapp
Week 1 signal
Track template approval time, first-reply latency, delivered-rate, and the first 100 customer replies. For growth teams, the fastest warning sign is not low opens; it is customers replying with confusion because the trigger, offer, or handoff promise was not specific enough.
Month 1 signal
Compare reply quality across Spec capture, Drawing approval, Fabric / wood select, Milestone updates. The best-performing growth teams teams keep the highest-intent replies visible to managers, then rewrite templates around real customer language instead of internal terminology.
Scale signal
Once Spec capture in chat → Drawing + fabric approval → Milestone updates auto → Dispatch + delivery confirm is stable, scale by segment rather than volume. Add new audiences only when opt-in source, template intent, agent ownership, and conversion tracking are all mapped.
Search-quality notes for this workflow
This page is intentionally built around custom orders on whatsapp rather than a generic WhatsApp marketing overview. The content references the actual workflow, the growth teams audience, implementation steps such as Spec capture in chat, Drawing + fabric approval, Milestone updates auto, Dispatch + delivery confirm, and use cases like Custom sofa, Built-in wardrobe, Modular kitchen, Office bulk. That specificity helps buyers, internal teams, and search engines understand why this page deserves to exist separately from broader WhatsApp CRM, broadcast, chatbot, and automation pages.
Related guides & pages
6 weeks of anxiety, one calm thread
Spec, approval, milestones, dispatch \u2014 all on WhatsApp.