Enterprise

Tell us the volume. We’ll put a number on it.

Studio and Scale are self-serve. This page is for teams that need extra WhatsApp numbers, a Cloud API send path into a CRM, or Telegram extras (Business secretary, payments, inline catalogs) that aren’t on the public plans yet.

Already know you want Studio or Scale? Start there. Agents stay the same: inbound from knowledge, you send campaigns.

NameWork emailCompanyRolePhoneWhatsApp volumeWhatsApp numbersSend API into your CRM or storeMigrating from another BSP

Telegram extras to quote

Telegram Business secretaryConnect the bot to a business account so it can reply in the chats you allow — with Inbox claim still winning.Mini App checkout and catalogsIn-chat shop, booking, or lead form with Telegram Payments or Stars. You still approve what goes out.Inline catalogs from any chatType @yourbot in any conversation to share a product, slot, or FAQ card. High intent, low friction.Deep links and QR campaignst.me links that open a specific agent, offer, or language. Track which poster or ad started the chat.Topics, polls, and checklistsOne bot, many jobs: a topic per order, a quiz for onboarding, a checklist for a field visit.Channel DMs and streaming repliesPrivate replies under a public channel, with the agent drafting while the customer watches progress.

Anything else we should price

WhatsApp Cloud API

1. You onboard on our Meta app
Embedded Signup puts your WhatsApp Business Account on Actionpackd, the Tech Provider. Meta never hands you a raw Cloud API token to paste into Shopify.
2. Cloud API traffic runs through us
Inbound webhooks land here. Approved template sends leave here. Rate limits, quality, and the 15% channel margin stay on this pipe.
3. The agent answers. You still send.
One live agent per number handles inbound from knowledge and tools you grant. Campaigns and API sends are operator work — the model cannot launch them.
4. Enterprise send API (quoted)
Your CRM or store calls Actionpackd with a workspace key. We send the approved template on your WABA. Inbound still hits the same agent. Claim still silences it.

We never give you a Meta system user token to store. Your systems talk to Actionpackd. Meta talks to us. The live agent on that number still stops the moment someone claims Inbox.