Managed vs Branded WhatsApp Delivery: Which Should You Use?

Managed vs Branded WhatsApp Delivery: Which Should You Use?

We just rebuilt WhatsApp delivery from the ground up. The TL;DR: there's now a one-click way to start ("Managed"), and a do-it-properly path for when the message header has to say your company's name instead of ours ("Branded").

This post explains why the split exists, how each tier works under the hood, and how to pick.

The problem with WhatsApp setup

WhatsApp is the highest-signal place to push a chart. People read their phones. They reply. They react. Slack has notification fatigue; WhatsApp doesn't (yet).

But the path to actually sending a WhatsApp message from a business is famously painful. The default story looks like this:

1. Create a Meta Developer account
2. Create a Meta App with the WhatsApp product
3. Spin up a WhatsApp Business Account (WABA)
4. Buy a phone number that Meta will verify (usually through Twilio)
5. Get your business verified in Meta Business Manager (1–10 business days)
6. Generate a System User access token with the right scopes
7. Set up webhooks for inbound replies
8. Add 5 test recipients in API Setup or apply for a higher rate tier

The first time I did this for Chartcastr it took about a week. For most teams that's a complete blocker — they'd never even try it just to text themselves a daily revenue chart.

So we asked: what if the setup just... wasn't there?

Managed: zero setup, our number sends

The Managed tier removes every step above. The flow is:

1. Open Chartcastr → Destinations → WhatsApp → Enable
2. Enter the recipient's phone number
3. Reply to the WhatsApp message we send you with the 6-digit code

That's the entire onboarding. Chartcastr's shared business number does the sending. Your recipient sees a message header that reads "Chartcastr" with our verified green check, then the chart, then the AI summary as a threaded reply.

This works for the use case most teams actually want: a founder, a small team, an internal exec — people who want charts on their phones and don't care which number it came from.

It's bundled with any paid Chartcastr plan, no separate fee. Group chats are supported too: invite our number to a WhatsApp group, send the message chartcastr link from inside, and the group shows up as a destination.

Why this works (technically)

Verification is the trick. Meta's WhatsApp Cloud API has a strict "24-hour window" rule — businesses can only send free-form messages to a recipient who has messaged them in the last 24 hours. (Outside that, you need pre-approved templates.)

When you verify a new phone number with us, you reply to that verification message with the code. That reply opens the 24-hour window. Your first chart delivery happens immediately and lands cleanly. From there, every reply or reaction you send on a delivered chart keeps the window open indefinitely.

We hash and store the verification code (HMAC-SHA256 with a server-side salt). The inbound webhook detects 6-digit numbers in any message from an unverified phone and auto-confirms — so most people never even see the dialog's manual code field.

For groups: when our number is in a group and someone sends chartcastr link, we check whether the sender's phone is a verified destination on any Chartcastr org. If it is — and only if it is — we attach that group to that org. This is the no-data-leak guarantee: another customer can't claim your group by guessing IDs, because they don't have a verified member of your team sending the link command from inside.

Branded: your company's number, your brand

Managed is the right default for most use cases. There's exactly one situation where it isn't: when the recipient is your customer.

If you're an agency sending KPI digests to clients, or a SaaS sending account dashboards to enterprise buyers, the message header saying "Chartcastr" instead of "Acme Reporting" is a problem. It looks like you outsourced your delivery (you did) and it dilutes your brand.

Branded fixes that. Charts ship from your company's verified WhatsApp Business number. The recipient sees your brand, your green check, your name in their chat list.

The trade-off is setup time. We handle the Meta-side work with you — including business verification, phone provisioning, WABA setup, token generation, and (when needed) drafting approved message templates for sending outside the 24-hour window. Expect about 1–2 weeks end-to-end, depending on how much of the Meta Business setup you already have.

Pricing starts at $85/mo per account and scales with volume + how many Meta-side assets we maintain for you. Meta's per-message fees are passed through at cost (these are usually fractions of a cent, but stack up for large lists).

It's lead-gen onboarding — you tell us what you want to send, to whom, and at what volume; we scope, price, and book a call. There's a button inside the Connect dialog (and an email at branded@chartcastr.com) when you're ready.

A decision matrix

A clean way to think about it: Managed is the dev environment of WhatsApp delivery; Branded is the production environment. Most teams start on Managed and never move. The ones that do move are usually doing it because their customers are now the recipients.

What's the same between the two

The actual sending pipeline is identical. Both tiers:

• Use Meta's WhatsApp Cloud API directly (no third-party message bots)
• Send the chart as a native WhatsApp image (not a link to a PNG)
• Include the AI short summary in the caption (1024 chars, with auto-trim)
• Send the long-form analysis as a threaded reply (4096 chars max)
• Support inbound replies + emoji reactions, which trigger an AI follow-up in the same conversation
• Track sent / delivered / read / failed status for every message
• Work with every Chartcastr source (Google Sheets, HubSpot, Shopify, BigQuery, Linear, etc.)

The only differences are whose token signs the API call and what name shows up in the message header. Everything else — including the long-running feature roadmap (group send, templates, multi-region) — applies to both tiers automatically.

Coming next

A few things on the immediate WhatsApp roadmap that ship to both tiers when they land:

• Group send GA — schema and UX support WHATSAPP_GROUP destinations today; we light up actual delivery the moment Meta promotes group send out of limited beta.
• Message templates — for sending pulses to recipients who haven't messaged you in >24 hours. Branded customers get template authoring as part of onboarding; Managed will get a shared "Chartcastr weekly chart" template.
• Multi-region Managed numbers — local-presence numbers in AU, UK, EU, etc. so your weekly digest doesn't always come from a US number.

If you want to be early on any of these, enable Managed in app and we'll surface them automatically as they ship. If you want Branded set up properly with your own number and brand, tell us about your use case and we'll get back the same day.

Either way, your charts are about to start landing where people actually read them.