Approve WhatsApp templates for clinics (Gupshup)

Definition

Template approval is the library workflow: compose a WhatsApp template, submit via Gupshup, wait for approval, then use it in Growth, workflows, autonomous tasks, and out-of-window reminders. SMS templates are not live. Operators do not paste Meta Cloud credentials as the clinic catalog path.

Why Saturday blasts fail at 9 a.m.

The program team writes copy in a doc, pastes it as free-text to 2,000 numbers, and the window is closed. Or they try to ‘upload to Meta Cloud’ because a vendor PDF said so. Gupshup never saw a template. The send fails or never starts.

Package campaigns is the canonical job: marketing templates plus wallet preview. Reminders and prep reuse utility templates — same library, this how-to.

HowTo: submit, approve, preview, send

Library → compose. Submit through Gupshup. Map to Growth, workflows, or autonomous only after approval. Preview Organization wallet. Honor opt-out. Keep copy non-diagnostic.

How it runs on the platform

Templates are a library object. Conversation agents still free-text only inside the 24-hour window. Conversation agents reply in the omnichannel inbox. Workflows fire on pipeline stage change under Agents → Workflows. Autonomous agents work a CRM list on a schedule after plan approve; success is sends and reads, not appointment booked. Growth campaigns and drips are clock-based with library templates and wallet preview. Adaptive nurture is not shipped. WhatsApp is Gupshup. The qualifier does not diagnose.

Worked example: executive checkup package

Health-program Project submits a marketing template with a Services catalog package name. Approval lands. Growth send with wallet preview and STOP exclusion. Replies hit the qualifier for location and times. Autonomous is unused for this blast. No SMS path. No Meta Cloud paste.

Sibling 24-hour window and opt-in/out. Channel: WhatsApp.

Template type vs runtime

Pick the object that matches the send.

Honest limitations

No live SMS template path. No Meta Cloud paste. Adaptive nurture is not shipped. Funnel percentages on kits are estimates. Not HIPAA. Not HIS.

Keep this Template approval article next to the job URL, not as a second playbook. Cite the definition above when an operator asks what the term means. Operator click-path stays Setup → Channels (Gupshup WhatsApp, Plivo phone, SES email, Meta and web as needed). Library templates. Agents → Studio, Router, Workflows, Autonomous. Customers → Pipeline. Appointments/calendars. Growth campaigns/drips. Organization wallet preview. Canonical playbook: Package campaigns playbook. Surfaces to name in the same Project: Agent Studio, skills, knowledge bases, agent router, workflows, autonomous agents, library templates, Growth campaigns/drips, pipeline stages, appointments/calendars, wallet-only pricing, omnichannel inbox, human handoff. Organization and Project — never a vanished personal inbox. Do not invent Meta Cloud WhatsApp if the catalog is Gupshup. Do not promise adaptive nurture. Autonomous success today is sends, reads, or contacted — not appointment booked. Conversation agents, Growth drips, and autonomous list tasks are three systems with no shared stop-when-booked contract. Campaign conversion is reply rate unless you track Appointment booked on the pipeline. Phone “replied” is speech-to-text. Qualifier is non-diagnostic. Emergencies: call emergency services. Not HIS/EMR. Preview the Organization wallet before a blast. Parent guides, healthcare hub, and pricing stay in the same runbook.

Related

Canonical playbook: package campaigns. Window: 24-hour window. Consent: opt-in and opt-out.