What is WhatsApp In-App Signup for business owners?
WhatsApp In-App Signup lets business and website owners collect official marketing opt-ins via a deep link (wa.me/…/signup/…). Customers consent inside WhatsApp, get a confirmation (with optional promo code), and join your messaging customer base — without messy “message us YES” hacks. Meta’s official deep-link opt-in so customers subscribe to your WhatsApp messages inside WhatsApp — with confirmation, optional promo code, and a webhook to your systems.
Last updated: 5 August 2026
WhatsApp In-App Signup is Meta’s official way for customers to subscribe to your business messages with one tap. You create a signup deep link, put it on your website (or QR / social bio), and when someone opts in inside WhatsApp you get a webhook event — and they get a confirmation message, optionally with a promo code. For business owners and website owners, that means cleaner consent, fewer “reply YES to subscribe” drop-offs, and a list you can market to with approved templates.
Source: Meta In-App Signup documentation (Graph API v22.0+). This guide explains the business value first; API builders can follow Meta’s endpoints directly or use a BSP like Ominiflow for inbox + campaigns on top.
Too long? Start here
- What it is: a
wa.me/<phone>/signup/<signup_id>deep link that opens WhatsApp with a pre-consent screen - Why owners care: official marketing opt-in, confirmation message, optional promo code, privacy policy URL required
- Where to use it: website “Chat / Subscribe” buttons, landing pages, Instagram bio, packaging QR, email footers
- What you get: webhook when someone subscribes + subscriber added to a messaging customer base
- Not the same as: Embedded Signup (onboarding a business to Cloud API) or Click-to-WhatsApp ads (ad traffic into chat)
What is WhatsApp In-App Signup?
In plain language: Meta lets you create a special WhatsApp link that asks the user to agree to receive messages before they join your list. The user sees your signup message and privacy policy context, taps to consent, then receives your confirmation message automatically.
Deep link format:
wa.me/<PHONE_NUMBER>/signup/<SIGNUP_ID>The signup ID is not locked to one number — you can reuse the same signup ID with any phone number on your WhatsApp Business Account (WABA). That helps brands with multiple numbers or regional lines.
Why it is useful for business owners
| Business problem | How In-App Signup helps |
|---|---|
| Marketing templates need proof of consent | Opt-in happens in WhatsApp with Meta’s flow — cleaner audit trail than vague “they messaged us once” |
| Customers ignore “reply YES” | One-tap consent + automatic confirmation reduces friction |
| Want to grow a broadcast list from the store / website | Put the deep link on CTAs and QR codes; every opt-in lands in your messaging customer base |
| Need a welcome offer | Use {{promo_code}} in the confirmation message (e.g. WELCOME10) |
| Campaign ended / link abused | Disable the signup (DISABLED) without deleting your WABA |
| Multiple offers / audiences | Create several signup links (Summer Sale, VIP, Newsletter) with different messages and promo codes |
After opt-in you still send marketing content with approved Marketing templates and respect quality rating — signup is the consent door, not a spam license. Related: template message guide · common API mistakes.
Why it is useful for website owners
Your website already captures intent (product page, blog, checkout). In-App Signup turns that intent into a WhatsApp subscriber without building a custom consent chatbot.
- Homepage / sticky CTA: “Get offers on WhatsApp” → deep link
- Product pages: “Notify me of restocks & deals on WhatsApp”
- Thank-you / order confirmation page: invite buyers to subscribe for shipping tips and VIP drops
- Blog / lead magnet: replace “enter email” with WhatsApp subscribe for higher open rates
- QR on packaging / storefront: same deep link offline → online
Meta requires a privacy policy URL on create (immutable after creation) and optionally your website URL (https:// only). That pushes website owners to keep a live privacy page — good for Meta policy and for India’s DPDP-style transparency expectations.
How the customer experience works
- Customer taps your deep link (button, QR, bio)
- WhatsApp opens a pre-consent screen with your
signup_message(1–300 characters) - Customer consents
- They receive your
confirmation_message(promo code filled in if you set one) - Your backend / BSP receives a webhook that they subscribed
- They are added to your WABA’s default messaging customer base
You never ask them to invent a keyword or hunt for your chat. The link is the funnel.
In-App Signup vs Embedded Signup vs CTWA
| Feature | Who uses it | Purpose |
|---|---|---|
| In-App Signup | Your customers | Opt in to receive your WhatsApp messages |
| Embedded Signup | You / your clients (businesses) | Connect a WABA / number to Cloud API via Meta’s onboarding UI |
| Click-to-WhatsApp ads | Paid media traffic | Open a chat from Meta ads; still need ongoing consent strategy for marketing blasts |
| Checkout checkbox | E-commerce buyers | Capture consent at purchase; complementary to In-App Signup |
Website owners often combine: checkout opt-in for buyers + In-App Signup for browsers who never purchase yet. Ad teams still use Click-to-WhatsApp ads for paid acquisition.
Where to place the link (practical checklist)
| Placement | Example CTA | Tip |
|---|---|---|
| Website header / floating button | “WhatsApp offers” | Use a dedicated signup link, not only a plain wa.me chat link |
| Landing page after Meta/Google ads | “Unlock WELCOME10 on WhatsApp” | Match promo_code to the ad creative |
| Instagram / YouTube bio | “Subscribe for drops” | Short display name in your CRM; users never see internal nickname |
| Email footer / SMS | “Prefer WhatsApp? Tap to subscribe” | Migrate high-open email list with consent, not purchased lists |
| QR at POS / packaging | “Scan for loyalty alerts” | Print durable QR; disable link when campaign ends |
Promo codes that actually convert
Meta lets you put {{promo_code}} in the confirmation message and pass an alphanumeric code (1–50 chars). Example confirmation:
Thank you for signing up! Here is your welcome code: {{promo_code}}.
Rules that matter for owners:
- If you use
{{promo_code}}, you must supply apromo_codevalue — otherwise Meta returns an error - Unknown placeholders also fail — keep copy simple
- Rotate codes per campaign via update API (or ask your BSP to update the link)
- Disable the signup when the offer expires so old QR posters don’t leak discounts
Messaging customer bases (why they matter)
When users opt in through a signup deep link, Meta adds them to a messaging customer base. Creating your first signup auto-creates a default base. You can create additional bases (e.g. “Summer 2026 Subscribers”), set which base is default for a WABA, and route new subscribers there.
For business owners this is the foundation of segmented WhatsApp audiences — separate VIP, sale, and newsletter pools instead of one messy contact dump. Your BSP or CRM should sync these contacts with opt-in source and timestamp for audits.
Compliance notes for owners (not legal advice)
- Accept Meta’s marketing messages Terms of Service on the first signup create (
policy.tos+accepted: true); omitpolicyon later creates - Publish a real privacy policy URL — it cannot be changed after the signup is created
- Website URL must use
https:// - Permission needed on the API side:
whatsapp_business_management - Marketing sends still need approved templates and healthy quality rating
- In India, align opt-in purpose with DPDP expectations — purpose-limited consent, easy opt-out in ongoing messages
DIY API vs platform (Ominiflow)
| Task | DIY on Graph API | With a BSP (e.g. Ominiflow) |
|---|---|---|
| Create / update / disable signup links | Call /<WABA_ID>/signups yourself | Dashboard or assisted setup; links for campaigns |
| Receive opt-in webhooks | Host and verify your own endpoint | Managed webhooks → inbox / CRM |
| Send post-opt-in journeys | Build template sends + sequencing | Campaigns, chatbots, Zoho/Shopify sync |
| Best for | Product teams with backend engineers | Business & website owners who need results this week |
API availability starts at Graph API v22.0+ (Meta examples use v25.0). Full create/list/update reference: In-App Signup docs. Cloud API basics: WhatsApp Cloud API get started.
30-minute owner playbook
- Confirm you have Cloud API access (BSP or direct) and a live privacy policy page
- Decide one offer (e.g. WELCOME10) and one signup message under 300 characters
- Create the signup (or ask Ominiflow to provision the link)
- Build
https://wa.me/<your_number>/signup/<id> - Add a clear website button + QR; test on a real phone
- Connect opt-in webhook to CRM / shared inbox
- Send a welcome Marketing template sequence only to opted-in contacts
- When the campaign ends, set signup status to DISABLED
FAQ
What is WhatsApp In-App Signup for business owners? expand_more
It is Meta’s official deep-link opt-in so customers can subscribe to your WhatsApp messages inside the WhatsApp app — with confirmation, optional promo code, and a webhook to your systems.
How do website owners use In-App Signup? expand_more
Place the wa.me/…/signup/… link on CTAs, landing pages, thank-you pages, and QR codes. Visitors consent in WhatsApp instead of filling a fragile form or typing YES.
Is In-App Signup the same as Embedded Signup? expand_more
No. Embedded Signup onboards a business onto Cloud API. In-App Signup lets end customers opt in to receive that business’s messages.
Do I still need message templates after someone signs up? expand_more
Yes for business-initiated marketing outside the 24-hour service window. Signup gives consent and a confirmation message; ongoing promos use approved Marketing templates.
Can I change the privacy policy URL later? expand_more
No. Meta marks privacy_policy_url immutable after creation. Get the correct HTTPS privacy page live before you create the signup.
Can I stop an old QR code from working? expand_more
Yes. Update the signup status to DISABLED. Users who tap a disabled link see an error. You can reactivate later with ACTIVE. There is no delete endpoint.
Do I need developers to use In-App Signup? expand_more
Direct Graph API calls need engineering. Most business and website owners use a BSP so the link, webhook, inbox, and campaigns are managed in one place. Updated August 2026. Based on Meta’s WhatsApp In-App Signup documentation for Business Messaging. Ominiflow is a Cloud API platform layer — not affiliated with Meta.
