KYC Collection WhatsApp Template for D2C Brands
Chasing customers to complete their KYC over email or a static portal link is where activations quietly die — messages go unread, forms get abandoned, and your ops team ends up calling people one by one. This page gives Indian D2C brands a ready-to-use, Meta-compliant WhatsApp KYC collection template that lands in the one channel your customer actually opens. It ships as a Utility template with the variables, sample values, button and approval notes already worked out, so you can copy it, personalise it, and start collecting verified documents in a day. Because it's tied to a real account action, it qualifies for the cheaper utility category and reads as a genuine 1:1 request rather than a broadcast.
Variables
{{1}}= Rhea{{2}}= gold savings plan{{3}}= PAN and a selfie{{4}}= KYC-8842
Verified business
10:24
Preview · as customers see it
When to send this KYC collection template
Fire this message at the exact moment the customer hits a KYC gate — right after sign-up, at first order for a regulated product (jewellery gold plans, supplements sold under FSSAI, fintech-adjacent wallets or BNPL, or any category where you must verify identity before fulfilment), or when an existing account is flagged for re-verification. The template is designed as a proactive nudge, not a cold outreach, so it belongs inside a live customer journey where the person is already expecting a next step. Sending it promptly after the trigger event is what keeps it in the utility category and keeps completion rates high, because the request still feels connected to something the customer just did.
- Immediately after account creation, before you can activate or ship
- When a first order requires identity verification to fulfil
- On re-KYC prompts for dormant or flagged accounts
- As a follow-up when a document upload failed or was rejected
Personalise the variables so it reads 1:1
The difference between a KYC request that gets tapped and one that gets ignored is specificity. Merge the customer's first name into {{1}}, name the exact account or plan you're activating in {{2}}, and — critically — tell them precisely which documents you need in {{3}} rather than a vague 'your documents'. Add a short reference or ticket ID in {{4}} so support can trace the conversation and the customer trusts it's real. Keep the merged output honest and human: 'Hi Rhea, to activate your gold savings plan we still need to verify your KYC. Please share PAN and a selfie…' reads as a personal message from your brand, which is exactly what earns the tap. Never over-stuff variables or leave one blank, because empty or mismatched merge fields are a common cause of template rejection and undelivered sends.
- {{1}} — customer first name (e.g. Rhea)
- {{2}} — the specific account, plan or service being activated
- {{3}} — the exact documents required, spelled out
- {{4}} — an internal reference or ticket ID for traceability
Why Utility is the right category — and how it's billed
This message is transactional: it's tied to a concrete account action the customer initiated, and it carries no promotion, no offer and no cross-sell. That places it squarely in the Utility category, which since Meta moved to per-message billing on 1 July 2025 is charged per delivered message at the utility rate rather than by conversation. If a customer messages you first and you reply about their KYC within the free 24-hour customer service window, that reply can be free — the window is a service window, not a billing unit, so it never changes the category of a business-initiated template. On InfiQ you pay Meta's live utility rate plus InfiQ's own transparent ₹ platform pricing (ex-GST), with the exact per-message figure shown before you send so there are no surprises on the invoice.
- Utility = transactional, tied to a real action, no promotion
- Billed per delivered message at the utility rate (post-1 July 2025)
- The 24-hour service window is free but is not a billing model
- Adding any offer or incentive reclassifies it as marketing
Getting it approved on the first submission
Submit the template as Utility and keep the body strictly informational — the single fastest way to get a KYC template rejected is to sneak in a discount, a launch teaser or any marketing language, which forces it into the marketing category. Provide realistic sample values for every variable when you submit, because Meta's reviewers use them to judge intent; a placeholder like 'xxx' or an empty field invites rejection. Match the button to the action: a single 'Complete KYC' URL button that deep-links to a secure, HTTPS verification page performs best, and adding a lightweight 'Why we need this' button can pre-empt hesitation without changing the category. Approvals typically land within a day, after which you can send instantly through InfiQ.
- Keep the copy purely informational — zero promotional wording
- Fill in genuine sample values for every {{n}} variable
- Use a secure HTTPS link behind the Complete KYC button
- Re-submit for approval whenever you materially edit the wording
Variations you can adapt
Keep the core template and branch it for different needs. Trim to the customer name plus a single documents variable for a lean, high-urgency reminder when someone has already started but not finished. Build a Hindi or regional-language version so the request lands in the customer's own language — a strong driver of completion for D2C audiences outside metros. If you genuinely want to attach an incentive ('finish KYC by Sunday to unlock free delivery'), remember that turns it into a marketing template: it must be submitted as marketing, opt-in must be in place, and it must carry an opt-out line such as 'Reply STOP to opt out.' For pure verification, stick with the clean utility version above.
- Short reminder: name + documents variable only
- Regional-language variant in Hindi or the customer's language
- Incentivised nudge — submit as marketing, with an opt-out line
- Re-KYC variant with an updated reference and reason
Like this template? Send it live in 24 hours.