WhatsApp Webinar Automation Playbook
AiSensy + Rajiv Talreja Pattern

Email open rates have collapsed to 20–21% globally. WhatsApp sits at 90–98%. For webinars, where attendance is the single biggest determinant of conversion, that gap is decisive.

The cost moat is just as real. Cosco's reach went from 30–35% via email broadcasts to ~90% via WhatsApp. The 1% Club killed expensive Meta pixel retargeting in favor of WhatsApp first-party segmentation. PhysicsWallah was running 20% open / 2–5% CTR on email before WhatsApp drove their webinar attendance up 4× and course sales 5×.

Why this matters specifically for webinars

Webinar no-show rates run 50–70% across the industry. The single highest-leverage intervention is a reminder sequence that actually gets read. A 4× attendance lift (PhysicsWallah's documented result) compounds straight into:

• 4× more live attendees — more eyeballs on the offer
• 4× more high-intent conversations — better qualified leads downstream
• 4× more proof points — testimonials, case studies, social proof for next cohort

For Truffle Nation specifically: every 100 registrants you save from no-showing is roughly 5–10 incremental ₹25,000 program sales (at typical conversion rates from webinar → 6-week program). At ₹2,500 LTV per saved registrant, the entire WhatsApp infrastructure pays for itself within the first cohort.

This is the proven sequence used by Rajiv Talreja's Business Success Workshop — India's largest business-coaching webinar funnel. Captured live from a real registrant inbox in May 2026. Six touches over ~50 hours between registration and the webinar going live.

Always add these post-Rajiv touches

• T-10min: "Starting now — join immediately"
• T+15min (live): "We're LIVE! We don't see you in the room" — no-show recovery. Single most powerful template — recovers 15–25% of no-shows on its own.
• T+2h post: Recording delivery (when applicable) + offer
• T+24h post: Replay reminder (if recording offered)
• T+72h post: Feedback ask / next webinar invite

AiSensy is an Official WhatsApp Business Solution Provider (BSP) sitting on top of Meta's WhatsApp Cloud API. Founded in India, used by PhysicsWallah, The 1% Club, FlexiFunnels, NMIMS, Skullcandy, and most major Indian coaching/EdTech brands.

Why AiSensy specifically (vs WATI / Interakt)

The comparison only matters when you're picking. The headline split:

• AiSensy — best for click-to-WhatsApp Meta ads + high-volume broadcasting (30K+/month). Cheapest Indian pricing (₹1,500/mo starter). Free forever plan.
• WATI — best for CRM-heavy support workflows with Zoho/HubSpot sync.
• Interakt — best for Shopify D2C brands focused on abandoned cart.

For coaching/webinar businesses (Truffle Nation, Rajiv Talreja style), AiSensy wins on broadcast speed (18 min for 10K messages vs WATI's 90+ minutes) and Click-to-WhatsApp native integration.

Utility vs Marketing Template

WhatsApp Business API classifies every template into one of three categories. This affects pricing dramatically.

Broadcast UI vs API Campaign

For the TN webinar funnel: API Campaigns for everything triggered by form submission (registration confirm, T-X reminders calculated from each user's registration time). Broadcast UI for the next-webinar invite to the warm list.

Click any template to see the message body, category, and button config. All names follow AiSensy's snake_case_with_version_suffix convention. Approved templates are immutable — version with _v1 so future edits become _v2.

The one-time setup work to get a working AiSensy account capable of sending webinar templates.

One-time setup checklist

• Create AiSensy account at aisensy.com (Google or email signup, OTP verify)
• Run embedded signup flow — Continue with Facebook → Authorize Meta → Select Business Manager → Create WABA profile → Add phone number → SMS/voice OTP verify
• Display name approval (2–3 hours) — must relate to business, not violate Commerce Policy
• FB Business Manager verification — submit GST cert, business address, website footer with legal name, business email on own domain
• Create custom attributes in Manage → Custom Attributes: first_name, webinar_date, webinar_time, webinar_link, cohort_id, ticket_id
• Create tags: webinar_registrant, webinar_attended, webinar_no_show, cohort_<id>
• Submit 10 templates for Meta approval (Marketing/Utility/Authentication categories chosen correctly)
• Wrap each approved template in a Live API Campaign — note each campaignName
• Configure webhook URL → your backend endpoint /webhooks/aisensy/<random-token>
• Set opt-in/opt-out keywords: STOP (out), START (in). Enable API Campaign Opt-out.
• Store API Key in secrets manager — Manage → API Key → Copy

Top template rejection reasons (avoid these)

1. URL shorteners (bit.ly, TinyURL) — BANNED. Use your branded short link.
2. Variable syntax errors — must be exactly {{1}}, not {name}
3. Spelling / grammar errors
4. Language mismatch — selected English but body has Hindi
5. Extra spacing / double line breaks
6. Asking for personal financial data
7. Missing country codes on phone numbers in body

Only one endpoint matters for webinar funnels. Auth is in the JSON body (not a header — unusual pattern).

The send endpoint

POST https://backend.aisensy.com/campaign/t1/api/v2
Content-Type: application/json

Request body

{
  "apiKey": "YOUR_API_KEY_FROM_DASHBOARD",
  "campaignName": "tn_webinar_reg_confirm_v1",
  "destination": "+917428526285",
  "userName": "Karan Labra",
  "templateParams": ["Karan", "June 6", "4:00 PM IST"],
  "source": "webinar_landing_page",
  "tags": ["webinar_registrant", "cohort_june_2026"],
  "attributes": {
    "first_name": "Karan",
    "webinar_date": "2026-06-06",
    "cohort_id": "june_2026"
  }
}

Node.js production wrapper

async function sendAisensy(payload, attempt = 1) {
  const res = await fetch('https://backend.aisensy.com/campaign/t1/api/v2', {
    method: 'POST',
    headers: { 'Content-Type': 'application/json' },
    body: JSON.stringify(payload),
  });

  if (res.ok) return await res.json().catch(() => ({ ok: true }));

  const body = await res.text();
  const status = res.status;

  // Retry on transient errors
  if ([429, 500, 502, 503, 504].includes(status) && attempt < 5) {
    const wait = Math.min(60_000, 2 ** attempt * 1000 + Math.random() * 500);
    await new Promise(r => setTimeout(r, wait));
    return sendAisensy(payload, attempt + 1);
  }

  throw new Error(`AiSensy ${status}: ${body}`);
}

Field rules & gotchas

• destination — phone with full country code (+917428526285). Without + = rejected.
• campaignName — must EXACTLY match a Live API Campaign in dashboard. Case-sensitive.
• templateParams — array length MUST equal template variable count. Mismatch = 400 error.
• tags / attributes — must exist in project. Non-existent ones are silently ignored.
• media.url — must be publicly accessible HTTPS. AiSensy fetches server-side.
• No batch endpoint — loop with concurrency < 30 req/sec for broadcasts.

Webhooks (inbound)

AiSensy POSTs JSON to your endpoint with events: message_received, message_delivered, message_read, message_failed, opt_out, user_interaction (button clicks).

Configure: Dashboard → Manage → Webhook. Paste your HTTPS endpoint URL. No HMAC signing — treat the URL path as a secret. Implement idempotency by event.id.

The highest-leverage acquisition channel for webinar funnels. Sharan Hegde's The 1% Club uses this exact architecture and gets 5× leads / 3× conversions on the same ad budget.

The architecture

1. Lead capture: Meta ad → user taps → WhatsApp opens → name + number auto-captured. No landing page.
2. Qualification: AI chatbot asks budget / interest / readiness → tags lead in real time
3. Engagement: AI chatbot replies 24/7 instantly; broadcast nurture for re-engagement
4. Retargeting: Segmented broadcasts → 5× ROAS claim

Setup (in AiSensy)

1. AiSensy → Ads Manager → Continue with Facebook → choose Business Manager
2. Grant ad account permissions (new account auto-created)
3. Choose FB Ad account + Facebook page
4. "Send OTP" to connect WhatsApp API number to FB page
5. Click "Create Ad" → fill creative (1080×1080 square)
6. Target by geography / age / interests
7. Set budget + duration → Meta review ~15–20 min

Welcome message structure for CTWA EdTech: warm greeting acknowledging inquiry → immediate value prop ("I'll answer your questions in <2 min") → single-choice qualification buttons.

Billing changed Jan 1, 2026 from per-24-hour-conversation → per-template-message-delivered.

AiSensy platform plans

Cost per webinar (1,000 registrants)

// Monthly cost
Platform plan + (Agents × ₹750) + (Marketing × ₹1.09) + (Utility × ₹0.145)

// 1 webinar, 1,000 registrants:
- Platform: ₹3,200 (Pro)
- Utility: 1,000 × 7 reminders × ₹0.145 = ₹1,015
- Marketing: 1,000 × 1 upsell × ₹1.09     = ₹1,090
- TOTAL: ~₹5,300/month

// Filing reminders as Marketing instead would cost:
- 1,000 × 7 × ₹1.09 = ₹7,630 in reminders alone
- SAVINGS by filing as Utility: ₹6,615 per webinar

WhatsApp Business Policy (hard rules)

• Explicit opt-in required before any business-initiated message. No buying/scraping lists.
• Pre-approved templates required for all outbound (24–48 hr review for custom; minutes for library)
• 24-hour messaging window — once user messages you, free-form replies allowed for 24 hours
• Easy opt-out required in promotional messages (Reply STOP)
• Quality rating system (High / Medium / Low) determines messaging limits

Broadcast tier limits

Skip tiers via KYC: Complete WhatsApp KYC verification to bypass the tier ramp. Critical for big-bang launches.

Quality rating protection

• Send only to opted-in users
• Use Utility templates for transactional events (lower spam reports)
• Don't blast Marketing templates to cold lists
• Honor opt-outs immediately (AiSensy auto-honors if configured)
• Keep promotional broadcasts to max 2-3 per week
• Send only 9 AM - 8 PM in recipient's timezone

Numbers worth quoting when justifying investment or explaining the model internally.

The 5×-leads-3×-conversion pattern

Across info-product brands, the same architecture keeps repeating:

CTWA Meta ad
  ↓
WhatsApp opens (name + phone auto-captured)
  ↓
AI chatbot qualifies (budget / interest / readiness)
  ↓
Tag-based segmentation (real time)
  ↓
Broadcast nurture (Marketing templates)
  ↓
Live agent for close (Team Inbox)
  ↓
WhatsApp Payment (cart close inside WhatsApp)

Truffle Nation has documented rules about what can and cannot appear in marketing copy. These apply to every WhatsApp template — verified credentials only.

Banned claims

Approved positioning

• "Introductory pastry roadmap" — approved positioning
• Chef Kirty — real host
• Live demo + Q&A — true format
• "6-week Pastry Foundation Program" — real upsell, disclose it
• "Recipe sheets shared in class" — verifiable deliverable

The problem: Each webinar cohort needs a fresh WhatsApp group. Templates are immutable once Meta approves them. Hard-coding the group URL means submitting _v2, _v3 templates forever.

The solution: Use a variable URL pattern at template-approval time. AiSensy and WhatsApp Cloud API support dynamic URL buttons where the trailing segment is a variable.

At template submission

When creating the group invite template (tn_webinar_group_invite_v1), set the CTA button URL pattern to:

https://chat.whatsapp.com/{{1}}

Provide sample value CktDiWyaHOa0OZ7tEAipmt for Meta reviewer. Meta approves the pattern — the variable suffix is what changes per cohort.

At API send time

In each API Campaign call, pass just the suffix as a button parameter (not the full URL):

{
  "apiKey": "YOUR_API_KEY",
  "campaignName": "tn_webinar_group_invite_v1",
  "destination": "+919876543210",
  "userName": "Karan",
  "templateParams": ["Karan", "4:00 PM IST", "CktDiWyaHOa0OZ7tEAipmt"]
  // Last param is the group invite suffix
}

For each new webinar cohort

1. Create a new WhatsApp group for the cohort
2. Copy the invite link (e.g., https://chat.whatsapp.com/AbCdEfGhIjKlMnOpQrSt)
3. Extract just the suffix (AbCdEfGhIjKlMnOpQrSt)
4. Store it as the cohort_group_id attribute for that cohort
5. Use it as the last templateParams value when sending the group-invite template

Same pattern for the join URL

For templates that include the join link (registration confirm, 1h reminder, starting-now), use the same approach. If your branded short link follows a pattern like https://trufflenationonline.com/wb-{{1}}, you can submit one template approved with that pattern and pass 6-june, 13-june, 20-june as the suffix per cohort.

Or — simpler — hardcode the SHORT link domain at the redirect layer. Make trufflenationonline.com/webinar-current always redirect to the active webinar's Zoom URL. Templates ship as-is across cohorts; only the redirect target changes.