KYC Collection WhatsApp Template for Restaurants

How to personalise it

The four variables do the heavy lifting. Use {{1}} for the recipient's first name so it reads as a one-to-one message rather than a blast. Use {{2}} to name the specific account or role being activated — 'partner outlet account', 'rider profile' or 'catering account' — so the person immediately understands why they are being asked. Use {{3}} for your brand name to build trust, and {{4}} to spell out the exact documents you need. Listing the documents explicitly is what turns a vague request into a two-minute task: 'your PAN, FSSAI licence and a cancelled cheque' tells the partner precisely what to gather, which dramatically cuts the back-and-forth. Keep the document list tight — ask only for what that particular KYC stage genuinely requires.

• {{1}} — recipient first name (Rahul)
• {{2}} — account or role being activated (partner outlet account)
• {{3}} — your restaurant brand (Spice Route Kitchens)
• {{4}} — the exact documents needed (PAN, FSSAI licence, cancelled cheque)

Getting it approved as Utility

Submit this template under the Utility category because it is tied to a concrete action — completing verification to activate an account. To keep it there, stay strictly informational: no offers, no discounts, no 'join our partner network' pitch. The instant you add a promotional hook the template drifts into marketing, which raises both the review bar and the delivered-message rate. Provide realistic sample values for every variable when you submit — Meta reviewers check that {{4}} resolves to a plausible document list, not a marketing line — and make sure your 'Complete KYC' button points to a genuine, secure verification page. A clean utility submission like this is usually approved within a day, and you can then send it instantly from InfiQ.

• Keep the copy purely transactional — no promotions or incentives
• Supply sample values for all four variables at submission
• Point the button to a real, secure KYC page (HTTPS)
• Never collect sensitive documents in the chat itself — always via the linked page

Security and consent

KYC is sensitive by nature, so the template deliberately never asks anyone to type document numbers into WhatsApp. Everything is collected on a secure page behind the button, where you control encryption, storage and access. Because this is a utility message tied to an action the partner initiated by signing up, it does not need a marketing-style opt-out line — but consent still applies: you should only message people who have an existing relationship and have shared their number for this purpose. Under India's DPDP framework, keep collection limited to the documents you actually need, state clearly what each is used for on the linked page, and retain them no longer than necessary.

• Documents are submitted on a secure page, never inside the chat
• No opt-out line required for utility, but consent and a prior relationship still apply
• Collect only what the KYC stage needs (data minimisation)
• Explain purpose and retention on the linked verification page

What it costs to send

This template bills at the utility rate. Since Meta moved off per-conversation billing on 1 July 2025, WhatsApp charges per delivered message by category, so every KYC message you send is a single utility-rate charge — there is no 24-hour bundle to reason about, and the free service window only affects replies you send back to a customer-initiated conversation. Because most partners reply, tap the button and complete verification the same day, the effective cost per completed KYC is very low. InfiQ shows you transparent ₹ pricing (ex-GST) so you can forecast a month of onboarding volume before you commit.