Databus Logo
Blog Login →
Meta Business Solution Partner · TRAI DLT · DPDP 2023 · 500+ schools 🇮🇳

WhatsApp Business API for Indian K-12 Schools

There is exactly one screen where parents actually read school messages. It's their WhatsApp.

This module owns the WhatsApp Business API tenant setup — registering your school as a Meta-verified business, getting message templates approved, and applying for the Green Tick where eligible. The broader bulk-comms orchestration (when WhatsApp vs when SMS fallback vs when in-app push) lives at /features/communication-tool/. The "reduce office calls 70%" buyer story is at /solutions/parent-communication/.

Setup is 10-14 days end-to-end: Meta business verification (3-5 days), template approvals (2 days each, batched), Green Tick application where eligible (case-by-case). Tap Pay Now in a fee reminder → lands at the school's UPI checkout in /features/fees/.

Book a demo to see the WhatsApp integration See how setup works

WhatsApp Business API for Indian K-12 schools is Meta's enterprise messaging interface that lets a verified school send transactional messages — fee reminders, attendance alerts, exam results, circulars — from a verified business phone number with pre-approved templates. SchoolDeck is the Meta Business Solution Partner that registers the school's WhatsApp Business Account, gets templates approved, supports Green Tick verification where eligible, and feeds the API into the school's bulk parent communications orchestrator at /features/communication-tool/.

10-14 days
Setup end-to-end
verification + templates
3 categories
Utility · Auth · Marketing
different pricing each
SMS fallback
For parents without
active WhatsApp accounts
Pay Now
Button taps to
school's own UPI checkout

The 14-day setup, day by day

Day 1: documents submitted. Day 14: first Pay Now button live.

No magic — Meta's review process has fixed wait times. What we control is the discipline of submitting clean documents and clean template copy the first time.

1

Day 1 · Documents collected

PAN, GSTIN (or 12A/80G for Trusts), address proof, phone number

The school provides four pieces of paper. SchoolDeck submits them to Meta Business Platform. The phone number must not currently be active on any WhatsApp account — if it is, we walk the school through the de-registration first.

2

Day 3-5 · Meta business verification approved

School's WhatsApp Business Account is live

Meta reviews and approves. The school is now a Verified Business sender. The Display Name configured at this step — "Greenwood International School" or whatever the school chooses — is what every parent will see in the message header from this day onward.

3

Day 6-10 · Templates submitted in batch

10-15 core templates registered with Meta for approval

Fee Reminder, Fee Receipt, Attendance Absent, Late Arrival, Exam Result, Holiday Circular, Admission Follow-Up, PTM Invite, Bus Delay, Result Published — each as a Utility template with that fill at send time. Marketing templates (Open House, Admissions Open) submitted under the Marketing category. Each gets approval in 24-48 hours; rejections (usually wording) we fix and resubmit.

4

Day 11-13 · Green Tick application (where eligible)

Submitted with public-presence evidence; Meta reviews

For schools with strong public footprint — news coverage, third-party listings, sometimes Wikipedia — Green Tick is achievable. We submit the application with curated evidence; Meta decides case-by-case. Outcome is not guaranteed; the API works equally well with or without Green Tick. Schools without it show as Verified Business (no green badge); functionally identical.

5

Day 14 · Go-live with a test parent

First real Fee Reminder fires; Pay Now button works end-to-end

The Accounts Head picks one real parent (with informed test consent), fires a Fee Reminder template, the parent receives it on WhatsApp with the school's Display Name, taps Pay Now, lands at the school's own UPI checkout in /features/fees/, completes payment, gets the Receipt template back in the same WhatsApp thread within 30 seconds. End-to-end works. The integration is operational.

Every API call, every template send, every Meta-side rejection and every parent reply logs in /features/audit-logs/ — DPDP Act 2023 audit trail starts on Day 14, not Day 100.

Four problems with the personal-WhatsApp reality

Why your teacher's phone is not a parent comms channel.

Not the broader orchestration question (that lives at /features/communication-tool/). These are about the WhatsApp Business API layer specifically.

📱

Pain 1 · The teacher's personal number is the school's brand

Class 5-B parents have Mrs. Kapoor's personal number saved.

She quit in March. The new teacher has different contact details. Half the parents still WhatsApp the old number for fee questions, attendance disputes and circular confirmations. The old teacher quietly forwards messages for six months out of guilt. A verified school WhatsApp Business sender means there's exactly one official channel — independent of which teacher is in which classroom this term.

🚫

Pain 2 · The bulk-sender tool that got the school banned

"Our WhatsApp account was suspended without warning."

Unofficial bulk-sender tools route through hijacked consumer WhatsApp accounts. Meta detects and bans them — at scale, not one by one. The school's main number, the one printed on all parent letterheads, goes dead at 9 AM on a Monday. The Business API is the legitimate paid interface designed for high-volume school messaging; using it ends the ban risk by structure.

💸

Pain 3 · The fee reminder that doesn't convert

"Your fee of ₹42,500 is due on the 5th" — and then what?

A plain text reminder works as information but not as a call to action. The parent has to remember the message, switch apps, find the payment portal URL, log in, enter details — five steps where attention falls off. An approved template with a Pay Now button collapses that to one tap — the button routes directly to the school's own UPI checkout in /features/fees/ with the invoice ID prefilled. Same parent, same intent, one tap instead of five.

📋

Pain 4 · The DPDP compliance gap nobody's tracking

"Did we ever get consent to message this parent on WhatsApp?"

Until 2023, schools messaged parents freely. Then DPDP Act 2023 became law (assented August 11, 2023; Phase III deadline May 13, 2027) and the compliance posture changed — verifiable parental consent is now required for processing personal data including messaging. Without a structured consent record at admission and an opt-out trail logged in audit logs, the school is exposed. The API layer's consent-record-and-opt-out machinery sits inside the integration, not bolted on.

Built on verified frameworks

The six frameworks Indian school messaging sits under.

Sending a fee reminder to a parent in 2026 isn't unregulated — six different rule frameworks touch the channel.

DPDP Act 2023

Verifiable parental consent

Digital Personal Data Protection Act 2023 (assented August 11, 2023; Phase III deadline May 13, 2027). Verifiable parental consent for processing minor's data is the lawful basis for school messaging. Captured at admission via structured checkboxes — fee + attendance + circulars separately from marketing/event. Opt-out via /optout reply switches the parent to SMS-only. Every consent + opt-out logs in /features/audit-logs/.

TRAI DLT Framework

SMS fallback registration

Telecom Regulatory Authority of India Distributed Ledger Technology framework. When WhatsApp send fails (parent without active WhatsApp), the SMS fallback fires from the school's TRAI-DLT-registered sender ID with a registered transactional template. SchoolDeck handles the DLT registration alongside the WhatsApp Business onboarding so both channels are live.

Meta Business Policy

WhatsApp Business Solution Terms

Meta's WhatsApp Business Solution Terms + Commerce Policy. All outgoing broadcasts must use pre-approved Utility / Authentication / Marketing templates. Promotional language in Utility templates causes rejection. Excessive parent opt-outs degrade messaging quality rating. The platform surfaces messaging quality continuously; we coach schools on template hygiene.

RBI PA-O Framework

Pay Now button destination

RBI Payment Aggregator-Online framework. Pay Now buttons in fee templates land at the school's own UPI checkout via /features/fees/ — backed by RBI-licensed PA-O (Razorpay CoA 28.12.2023, Cashfree CoA 20.05.2024 or similar). The button payload carries the invoice ID; checkout is pre-filled; parent confirms with UPI PIN. Settlement flows back to the school's escrow account.

CBSE Bye-Laws Ch. 9

Parent communication records

CBSE Affiliation Bye-Laws Chapter 9 covers school-record requirements including parent communications. The WhatsApp message log + delivery status + read receipts form part of the school's record set for periodic CBSE affiliation inspection. The integration's audit log produces searchable inspection-ready exports.

Consumer Protection Act 2019

Communication evidence trail

Consumer Protection Act 2019 + e-Commerce Rules 2020. Parents in dispute often raise "we were never informed" complaints. Timestamped delivery + read receipts from the WhatsApp API provide an objective evidence trail — when was the message sent, when was it delivered to the parent's device, when was it read. This evidence is admissible and frequently resolves disputes without escalation.

References: DPDP Act 2023 (Phase III 13.05.2027) · TRAI DLT framework · Meta WhatsApp Business Solution Terms · RBI Payment Aggregator-Online framework (March 2020 + September 2022 amendment) · CBSE Affiliation Bye-Laws Chapter 9 · Consumer Protection Act 2019

"
For three years our school's main parent comms channel was a third-party bulk WhatsApp tool. It worked until it didn't. One Tuesday morning in May the account just stopped. No warning, no email — the messages we tried to send returned errors. By the afternoon we understood: Meta had banned the entire fleet of numbers the tool used. We had to call 1,200 families individually to tell them the next day's PTM was still on. I lost two days. After that incident the Principal said find a real solution. We came to SchoolDeck in August. The onboarding took 13 days because two of our templates needed wording changes — "URGENT" in all-caps gets rejected, who knew. By the third week parents were getting Fee Reminders with a Pay Now button. The first week the September fees collected, 31% of payments came through that button — parents who would have otherwise paid on the 28th paid on the 6th. No drama, no banned numbers, no Goa-monsoon-day chaos. Just messages that arrive and buttons that work.
D
Mr. Daniel Pereira
Communications Manager · CBSE + ICSE School, Margao, Goa · 1,200 students · Migrated August 2024

What is the WhatsApp Business API for Indian K-12 schools?

It is Meta's official enterprise messaging interface. A verified business — in this case, your school — gets a dedicated phone number registered as a WhatsApp Business sender. Outgoing messages use Meta-approved templates (fee reminder, attendance alert, exam result, circular). Parents see the school's verified Display Name in the message header. Conversations are priced per category — Utility, Authentication, Marketing — and the school pays Meta directly through its tenant.

SchoolDeck is the Meta Business Solution Partner that handles the operational setup — registering the school's tenant on Meta Business Platform, submitting business verification documents, batching templates for approval, supporting Green Tick where eligible, and feeding the API into the school's broader bulk parent communications orchestrator. The school's WhatsApp Business Account is in the school's name, not Databus's. The school owns the templates, the conversation history, the parent-consent records.

This page owns the API tenant layer specifically. The broader question — when WhatsApp to use vs SMS fallback vs in-app push, how multilingual variants get selected, how sender masking works — lives at /features/communication-tool/. The buyer-outcome "reduce office calls 70%" story is at /solutions/parent-communication/.

Business verification with Meta — what documents are needed

Meta requires every WhatsApp Business sender to be verified as a real business entity. For Indian K-12 schools, the documents are:

  • PAN of the school's registered legal entity — the Trust, Society, Section 8 Company, or proprietorship that operates the school.
  • GSTIN if registered — schools above the GST threshold are registered. For schools below the threshold operating under Section 12A/80G charitable registration, the 12A registration certificate works as alternative proof.
  • Registered office address proof — utility bill (electricity, water, gas) in the entity's name, or municipal property tax receipt, or registered lease deed.
  • Phone number — a working mobile or landline that is not currently active on any WhatsApp account. If it is currently active, we walk the school through de-registration first (a one-time WhatsApp account delete on the consumer app).

SchoolDeck submits these to Meta Business Platform during onboarding. Meta's standard review window is 3-5 business days; sometimes faster, occasionally longer for documents needing clarification. On approval, the school's WhatsApp Business Account is created and the Display Name configured at this step ("Greenwood International School" or whatever the school chooses) is what every parent will see in the message header from day one.

Template approval — what Meta wants to see

Meta requires that every outgoing broadcast use a pre-approved template. This is a deliberate constraint — it prevents schools (and businesses generally) from using the API as a free-form messaging tool that turns into spam. Each template defines:

  • The text body with . Fee Reminder template: "Dear , the school fee of ₹ for is due on . Tap Pay Now to settle via UPI." The variables fill at send time from the school's data.
  • The header type. Text header, image header (school logo), document header (PDF receipt), video header (rare for schools).
  • The footer line. Typically the school's verified Display Name.
  • The button row. Quick-reply buttons ("Yes / No / Maybe" for RSVP), URL buttons (Pay Now → UPI checkout), phone buttons (Call School Office).
  • The category. Utility, Authentication or Marketing — determines per-conversation pricing.

SchoolDeck pre-loads the common school templates and submits them during onboarding. Each one Meta approves typically in 24-48 hours. Rejections — usually for promotional language in Utility templates, or all-caps urgency words ("URGENT") that Meta flags — get a wording change and a resubmission. The school's accumulating template library is the operational asset; over time most schools have 15-25 active templates covering routine and exceptional communications.

Three template categories — what each one costs

Meta categorises every template under one of three classes, each priced differently per conversation (a 24-hour window starting from the school's first message that day to that parent):

  • Utility — Transactional messages tied to a specific transaction or account update. Fee Reminder, Fee Receipt, Attendance Absent, Exam Result Published, Bus Delay, Holiday Circular, PTM Reminder. Lowest cost tier. Most school messaging sits here. Strict on policy — no promotional language, no general school marketing in this category.
  • Authentication — One-time-passwords and identity codes only. Login OTP for parent app, account-reset OTP. Mid-cost tier. Used sparingly in school context — only when SchoolDeck dispatches an OTP for parent app login (and even there, SMS is often the lower-cost fallback).
  • Marketing — Promotional or non-transactional messages. Open House invitations, Admission Season Outreach, Annual Day Save-the-Date, donor campaign. Highest cost tier. Requires explicit marketing-category consent from the parent (separate checkbox from utility consent).

For a typical 1,500-student K-12 school running attendance + fee + circular templates, monthly WhatsApp conversation spend usually lands in the ₹3,000-8,000 range depending on circular volume. SchoolDeck reports this monthly per category — the Communications Manager can see "₹4,200 Utility + ₹0 Authentication + ₹1,800 Marketing this month" and budget accordingly. Refer to Meta's official India price list for current rates; pricing has revised periodically since 2024.

Green Tick — what it is, why most schools want it, why some won't get it

The Green Tick is Meta's Official Business Account verification badge. It appears as a green checkmark next to the school's name in WhatsApp — visible to every parent who messages the school or receives a message from it. The Green Tick signals: Meta has reviewed this entity beyond standard business verification and considers it notable enough to mark as official.

What's true:

  • The Green Tick is NOT a prerequisite to use the WhatsApp Business API. The API works without it; the school appears as a Verified Business (no green badge). Functionally identical for sending and receiving messages.
  • Meta grants Green Tick case-by-case based on third-party online presence. News coverage, third-party listings, sometimes Wikipedia. Schools with strong public profile (big-city established schools with media presence) typically get approved. Smaller schools and Tier-3 city schools often don't, which is fine.
  • SchoolDeck supports the application but cannot guarantee approval. We submit the application with curated evidence — what news articles mention the school, what third-party listings exist, what alumni achievements have public attention. Meta decides.
  • Re-applications are allowed after improvement. A school that doesn't get Green Tick in Year 1 can re-apply later after building more public footprint.

Pay Now button — how the fee reminder converts to a settled payment

A Fee Reminder template carries a URL button. When the parent taps the button, the URL routes them — through a SchoolDeck redirect — to the school's own UPI checkout in /features/fees/. The button payload carries the specific invoice ID; the checkout opens pre-filled with the right student name, the right amount, the right due date.

The flow end-to-end:

  • Parent receives Fee Reminder on WhatsApp — sees school's verified Display Name in the header, the fee amount, the due date, the Pay Now button.
  • Taps Pay Now. WhatsApp opens the school's UPI checkout page.
  • The page is pre-filled — student name, fee head breakdown, applicable concessions, late fine if any.
  • Parent selects their UPI app, completes the payment via UPI PIN — typical settlement T+0 for UPI.
  • SchoolDeck receives the payment confirmation, marks the invoice paid in /features/students/, fires a Fee Receipt template back to the same parent's WhatsApp thread within 30 seconds — PDF receipt attached.
  • The Accounts Head's /features/fees/ dashboard shows the payment in real time; reconciliation is automatic.

The payment infrastructure is RBI Payment Aggregator-Online compliant — the school's UPI checkout is backed by an RBI-licensed PA-O (Razorpay holds RBI Certificate of Authorisation dated 28.12.2023; Cashfree holds CoA dated 20.05.2024; schools choose). Funds settle to the school's escrow account; T+1 to the school's operating account by typical workflow.

SMS fallback — how parents without WhatsApp still get the message

About 4-7% of parents in an average Indian K-12 school don't have an active WhatsApp account on their registered mobile — older parents who haven't migrated, basic feature-phone users, rural areas with intermittent data, parents who have actively de-registered. The school can't decide who they message; the message has to reach everyone.

The fallback mechanism — handled by the orchestrator at /features/communication-tool/ — is structurally simple:

  • The school's TRAI DLT registration is set up alongside the WhatsApp Business onboarding. The school has a registered SMS sender ID and registered SMS templates that mirror the WhatsApp templates.
  • For every outgoing message, SchoolDeck first attempts WhatsApp delivery via the Business API.
  • If Meta returns a "not registered" status (parent's number has no WhatsApp), SchoolDeck within seconds fires the equivalent DLT SMS template from the registered sender.
  • The Communications Manager sees both attempts in the per-parent message log — "WhatsApp: not delivered (no account) · SMS: delivered 09:42:11."
  • Pay Now button doesn't work in SMS (no rich media); the SMS template carries a short payment URL instead. Parent taps, lands at the same UPI checkout, same flow from there.

API ≠ Orchestration ≠ Buyer Story ≠ Solution Bundle

The SchoolDeck parent-communication cluster spans four ownership layers. Knowing the boundaries keeps schools from buying the wrong page's promises.

  • This page · /features/whatsapp-integration/ — Owns the WhatsApp Business API tenant layer specifically. Meta business verification, template approval workflow, Green Tick application, conversation pricing model, webhook reception. The IT or Communications Manager-facing technical setup page.
  • /features/communication-tool/ — Owns the bulk parent communications orchestrator. Decides which channel fires for which event — WhatsApp first, SMS fallback, in-app push parallel. Multilingual template variant selection. Sender masking. The day-to-day "how does an attendance alert actually get to every parent" page.
  • /solutions/parent-communication/ — Owns the buyer-outcome story. Reduce office calls 70%. Replace 28 class WhatsApp groups with one DLT channel. The Principal-facing "what does this do for me" page.
  • /solutions/attendance-biometric/ — Owns the biometric attendance + auto WhatsApp alert solution. A specific solution bundle where biometric capture triggers parent alerts; uses this page's API and that orchestrator.

Four pages, four owned layers. This page targets the buyer asking "what's involved in actually setting up the WhatsApp Business API for our school?" The orchestrator answers "how do we use it day to day?" The buyer-outcome page answers "what does this fix?" Different intents, different content.

Unofficial bulk-sender tool vs SchoolDeck WhatsApp Business API

Practical differences for a Communications Manager choosing between the cheap, unofficial tool and the official Meta Business Solution Partner path.

Capability Unofficial bulk-sender tool SchoolDeck WhatsApp Business API
Meta policy compliance Hijacks consumer accounts — TOS violation Official Business API — within policy
Account ban risk High — Meta detects, bans whole fleets Negligible — official paid interface
Verified Display Name Shows as unknown number "Greenwood International School" header
Green Tick eligible Not available — non-official Yes — application supported
Pay Now button + UPI checkout Plain text URLs only Native interactive button
Delivery + read receipts Inconsistent or absent Per-message status from Meta API
Inbound parent replies Routed to random teacher phone Webhook → admin inbox
DPDP 2023 consent record No structured trail Audit-logged consent + opt-out
SMS fallback for non-WA parents Manual workaround Auto via DLT-registered channel
CBSE inspection evidence trail No exportable log Searchable, exportable per Ch.9

FAQ

Questions Communications Managers ask before adopting WhatsApp Business API.

Honest answers about what this layer owns, what it costs, and what's a separate concern.

What is the WhatsApp Business API for Indian K-12 schools?

+

The WhatsApp Business API is Meta's enterprise messaging interface that lets verified businesses (including schools) send transactional and utility messages to customers (parents) from a verified business phone number. For Indian K-12 schools it means: a Meta-verified WhatsApp Business Account in the school's own tenant; pre-approved message templates for fee reminders, attendance alerts, exam results, circulars; interactive buttons that route to the school's UPI fee gateway; and a conversation-priced model under Meta's India price list. SchoolDeck is the Meta Business Solution Partner that handles the tenant setup, template registration and ongoing template versioning for the school. Used by 500+ Indian K-12 schools.

How is /features/whatsapp-integration/ different from /features/communication-tool/?

+

This page owns the WhatsApp Business API integration layer specifically — the Meta tenant setup, business verification, template approval workflow, Green Tick application, conversation pricing model. It targets the IT or Communications Manager evaluating the WhatsApp infrastructure. /features/communication-tool/ owns the broader bulk parent communications orchestration — deciding when WhatsApp to use vs SMS fallback vs in-app push, multilingual template variant selection, sender masking across all channels. Two pages, two layers. The school sets up the WhatsApp Business tenant on this page; the day-to-day choice of which channel to fire on a given attendance alert lives there.

What is the Green Tick and does our school need it?

+

The Green Tick is Meta's Official Business Account verification badge — a green checkmark next to the school's name in WhatsApp. It signals that Meta has reviewed the school as a notable business entity. The Green Tick is helpful for parent trust but it is NOT a prerequisite for using the WhatsApp Business API. The API works without it; the school just shows as a regular Verified Business. Meta grants Green Tick case-by-case based on third-party online presence — news coverage, third-party listings, sometimes Wikipedia. Schools with strong public profile usually get it; smaller schools may not, which is fine. SchoolDeck supports the application but cannot guarantee approval.

How does message template approval work?

+

Every outgoing broadcast message from a WhatsApp Business sender must use a Meta-approved template. SchoolDeck pre-loads the common school templates — Fee Reminder, Attendance Alert, Exam Result, Holiday Circular, Admission Follow-Up — and submits them to Meta during onboarding. Each template carries placeholder variables (, , ) that fill at send time from the school's data. Meta categorises each template — Utility (most school messages — fee, attendance), Authentication (OTP), or Marketing (admission outreach, event broadcasts) — with different per-conversation pricing. Approval typically takes 24-48 hours per template. Rejected templates need a wording change (Utility templates cannot have promotional language) and a resubmit.

What does WhatsApp Business API actually cost?

+

Meta charges schools per conversation (a 24-hour window starting from the school's first message that day), with different pricing for Utility, Authentication and Marketing categories. India pricing (subject to Meta's official rate card; check Meta's published price list before budgeting): Utility conversations are the lowest tier — fee reminders, attendance alerts, exam results fall here. Authentication (OTP) is mid-tier. Marketing (admission outreach, event broadcasts) is the highest. For a typical 1,500-student K-12 school running attendance + fee + circular templates, monthly conversation spend usually lands in the ₹3,000-8,000 range depending on circular volume. SchoolDeck reports this monthly per category. The platform integration itself is included in the SchoolDeck pricing.

What about parents who do not use WhatsApp?

+

About 4-7% of parents in an average Indian K-12 school don't have an active WhatsApp account on their registered mobile (older parents, basic feature-phone users, rural areas with intermittent data). The orchestration page /features/communication-tool/ handles this — when a WhatsApp template send returns a 'not registered' status from Meta, the same message falls back to a TRAI DLT-registered SMS template within seconds. The parent gets the message; the school doesn't have to track who-has-WhatsApp at the data-entry level. This page owns the WhatsApp send mechanism; the fallback decision lives in /features/communication-tool/.

Will our school's WhatsApp number get banned?

+

Not when used through the official Business API. The ban risk applies to unofficial 'bulk sender' tools that hijack regular WhatsApp accounts (the consumer app) for high-volume sending — Meta detects and bans those numbers. The Business API is the legitimate, paid interface designed exactly for high-volume school-style messaging. Schools sending only through pre-approved templates with documented parental consent records under DPDP Act 2023 sit cleanly inside Meta's policy. If template rejection patterns appear (too much promotional language in Utility templates, excessive opt-out reports from parents), Meta may downgrade the messaging quality rating; the SchoolDeck panel surfaces this rating and we coach the school on template hygiene.

Can parents reply to messages — does the school see those replies?

+

Yes. Inbound parent replies to school WhatsApp messages are received via the API webhook and routed to the admin inbox in /features/communication-tool/. They do not go to a random teacher's personal phone. Authorised front-office staff see the inbound queries, can assign them as support tickets (fee query → Accounts; attendance dispute → Class Teacher; admission enquiry → Admissions desk), reply through approved templates within the 24-hour conversation window. After 24 hours, any new outbound message reopens the conversation under Meta's pricing model. The two-way history is searchable and accessible only to authorised admins per /features/role-based-access/.

How does parental consent work under DPDP Act 2023?

+

Under the Digital Personal Data Protection Act 2023 (assented August 11, 2023; Phase III deadline May 13, 2027), processing a parent's personal data for communications requires a documented lawful basis — typically verifiable parental consent or a contractual necessity (school enrolment contract). SchoolDeck captures consent during admission with explicit checkboxes for fee + attendance + circular communications, separate from marketing/event communications. Parents can opt out at any time via a /optout reply on WhatsApp; the system records the opt-out, switches that parent to SMS-only for transactional messages, and stops marketing-category messages entirely. Every consent and opt-out event logs in /features/audit-logs/.

Can we use the WhatsApp API for an admissions chatbot?

+

Yes, with honest framing — what we offer is a rule-based template-response flow, not a generative AI chatbot. A prospective parent sends an enquiry over WhatsApp (clicked from a website ad or a Click-to-WhatsApp link); the system replies with a pre-approved Marketing template offering options: View Fee Structure, Download Brochure, Book a School Visit, Talk to Counsellor. Each option triggers another approved template — fee structure as a PDF, brochure as a PDF, visit booking via the admissions CRM, or hands off to a live counsellor's WhatsApp queue during office hours. It is structured and reliable; it is not free-text natural language understanding.

The four modules connected to the WhatsApp API

Where the API plugs in.

Each owns its own layer. Together they form the complete parent-communications operation.

📱

Communication Orchestrator

Owns the bulk parent comms orchestration — when WhatsApp vs SMS fallback vs in-app push, multilingual templates, sender masking.
📞

Parent Communication Solution

The buyer-outcome story — reduce office calls 70%. Replace 28 class WhatsApp groups with one DLT-registered channel.
💰

UPI Fee Collection

Owns the UPI checkout — Pay Now button in fee templates lands here. RBI Payment Aggregator-Online compliant.
🆔

Biometric Attendance + WhatsApp

The bundled solution — biometric capture triggers Attendance Absent template auto-fires via this API layer to parent's WhatsApp.
For Indian K-12 Communications Managers + IT Heads

Your bulk-sender tool gets banned next Tuesday. Or you set up the real one this fortnight.

In the demo we'll walk through Meta business verification documents, submit a real Fee Reminder template for approval together, fire a test message with a Pay Now button to a sandbox parent number, and show the per-category conversation pricing meter.

From ₹30/student/month · 500+ Indian schools · Setup live in 10-14 days · Meta Business Solution Partner

Book a demo to see the WhatsApp integration See pricing