A new tenant in a regulated vertical used to face the same blank-page problem on day one: the compliance profile, the campaign drafts, the opt-in flow, and the agent that answers on your behalf all ship as separate primitives, and wiring them together by hand takes weeks — most of it spent re-deriving defaults the industry already settled. The vertical compliance bundles close that gap. Under Settings → Compliance → Vertical Compliance Bundles, the catalog carries four pre-wired packs, and one activation call provisions the whole set as drafts. This post is the announcement of record: what the four packs are, what an activation actually creates, the go-live checklist it hands back, and the vendor question a buyer asks next.
The catalog: four shipped packs
Each pack is a named manifest — a fixed version, a summary, and the full list of what it provisions, previewable in the dashboard before you commit. The four shipped today:
- Healthcare (HIPAA-conscious patient messaging) — appointment reminders, prescription-refill, and post-visit follow-up drafts that keep PHI out of plain SMS, plus a patient-intake assistant. Its go-live checklist includes a Business Associate Agreement step before any patient message goes out.
- Fintech (KYC onboarding & account alerts) — five draft campaigns covering verification, onboarding, and transaction alerts, plus an onboarding-support assistant. Its vertical-specific checklist step makes you confirm the transactional-versus-marketing consent split before anything promotional sends.
- E-commerce (order lifecycle & re-engagement) — five draft campaigns for order, shipping, and re-engagement messaging, plus an order-support assistant. Its extra step separates marketing consent from order updates so promotional sends only target contacts who opted in to marketing.
- Payments & Collections (PCI-safe payment collection) — invoice, payment-link, and dunning drafts that never carry card data, plus a billing-support assistant. Its extra step asks you to confirm your payment links route to a PCI-compliant hosted payment page — a full card number, CVV, or expiry never travels over SMS or chat.
Every pack is SMS-channel drafts only, version-pinned, and the same activation endpoint serves them all.
What one activation actually provisions
Activation is a single POST from the bundle's page, and the response is the state of everything it created. Concretely:
- A draft compliance profile — named for the vertical and marked for review, not yet submitted. It sits in your compliance profile list in draft state until you attach documents and submit it.
- Draft campaigns — four or five per pack, carrying seed message copy with the mandatory opt-out footer already in place. They are drafts; none of them is scheduled, and none of them can send while the profile is unverified.
- A vertical-tuned AI agent — a first-line assistant (patient intake, onboarding support, order support, or billing support) with a system prompt tuned to the vertical's question shapes, ready to edit in the Agents surface.
- A double-opt-in flow configuration — pre-filled with your brand name and help contact, plus confirmation copy you can edit before it goes live.
What activation deliberately does not do: it wires no carrier, registers no sender ID, and places no send. Everything it creates is a draft behind the same verification gates a hand-built setup would face — the bundle compresses the setup, not the review. Buying a bundle is a starting position, not a shortcut past carrier approval.
The go-live checklist it hands back
The activation response carries a checklist, and the dashboard renders it as the go-live runbook for that pack. The shared tail — the same on every bundle — is the part that used to live in people's heads:
- Attach the required compliance documents to the draft profile.
- Submit the profile for verification — sending stays blocked until the carrier review approves it.
- Review the double-opt-in confirmation copy against your brand name and help contact.
- Confirm the quiet-hours window so sends land inside allowed local hours.
- Clear the vertical-specific step — sign the BAA (healthcare), confirm the transactional-versus-marketing split (fintech), separate marketing consent from order updates (e-commerce), or confirm the hosted payment page (payments).
- Review and approve the campaign copy before anything is scheduled.
Each step toggles pending or done and the activation keeps score, so a compliance lead and an operator can split the list and see the same progress. The provisioning steps themselves check in automatically — the manual steps above are the tenant-owned remainder no platform can honestly automate.
The question a buyer asks next
Once the packs exist, the evaluation question generalizes: does one vendor cover all four verticals, or do you assemble a specialist per vertical — one provider for healthcare messaging, another for fintech KYC alerts, a third for store notifications, a fourth for collections? The per-vertical assembly works until the consent record, the quiet-hours policy, and the opt-out list have to agree across four vendors — at which point the "specialist" stack is really four integrations and a spreadsheet. The bundle catalog answers the one-vendor side concretely: one activation surface, one consent ledger, one go-live checklist, four verticals. The packs also compose — a healthcare tenant running a payments arm activates both packs into separate draft profiles and runs two checklists against the same consent record.
Try it
Open Settings → Compliance → Vertical Compliance Bundles, expand a pack to read its full manifest before committing, and activate when the draft shape matches what you would have built by hand. Previously activated bundles appear in the resume list, so the checklist survives a reload. For the hand-rolled path the bundles replace, the manual loop is documented in the KYC sender-ID playbook, and the buyer-side questions a HIPAA evaluation raises first are in the HIPAA CPaaS buyer checklist.
Frequently asked questions
Does activating a bundle send anything or file anything with a carrier?
No. Activation creates drafts only: a draft compliance profile, draft campaigns, an AI agent, and an opt-in flow configuration. Nothing is scheduled, submitted, or transmitted. Sending stays blocked until you attach the required documents, submit the profile, and the carrier review approves it — the same gates a hand-built setup faces.
Can I edit what a bundle provisions?
Yes — everything it creates is a normal draft. Campaign copy, the agent's prompt and model settings, and the opt-in confirmation message are all editable before they go live, and the checklist makes you review the copy before anything can be scheduled.
What if my business spans more than one vertical?
Activate more than one pack. Each activation provisions its own draft compliance profile and checklist, so a healthcare tenant that also collects payments runs the healthcare and payments bundles side by side against the same consent record and quiet-hours policy.
Is this a shortcut past carrier or regulatory review?
No. The bundle compresses setup — the weeks of wiring primitives together — but it does not compress the review. Document attachment, profile submission, and carrier approval are still tenant-owned steps on the checklist the activation returns.