WhatsApp

Use WhatsApp as the handoff, not the launch blocker.

Start with web chat plus QR/deep links, then upgrade to an official WhatsApp Cloud API automation when you are ready.

Start with QR and deep links

Show a desktop QR and mobile WhatsApp link while the web assistant handles instant answers.

Add official Cloud API later

Use a BSP or partner flow for real webhook automation once a company wants production WhatsApp.

Keep Meta work behind the scenes

Explain business verification, display names, phone numbers, and template rules only when needed.

Separate platform and Meta fees

Jiffy bills software usage; Meta/BSP message costs are pass-through or an explicit WhatsApp add-on.

Meta setup

Keep the first win independent of Meta review.

Official WhatsApp automation needs business assets, a number, display name review, webhooks, and template rules. The web assistant should prove value before that complexity.

Desktop widget shows a QR code that opens a prefilled WhatsApp thread.
Mobile widget opens a wa.me deep link with source attribution.
Production automation uses official Cloud API only.
Unofficial WhatsApp Web session automation is not part of the product.
Meta/BSP fees are shown separately from Jiffy software billing.