Skip to main content
A Conversation is a Galantis platform usage unit consumed when a WhatsApp template message is delivered. Understanding exactly what counts — and what does not — helps you predict usage and avoid surprises on your Shopify invoice.
Conversations are not WhatsApp credits and they do not pay Meta charges. Meta bills WhatsApp messaging directly in Meta Business Manager. Galantis bills the platform Conversation separately.

​
What counts as a Conversation

A Conversation is consumed when all of the following are true:
  • The message is a WhatsApp template message (campaign or automation flow)
  • The message status becomes DELIVERED
  • The message is billable under WhatsApp messaging rules
A Conversation is not consumed for:
  • Drafts or previews
  • Failed sends
  • Undelivered messages
  • Inbound replies in the Inbox (those are tracked as Inbox Threads — see Inbox add-on)

​
The credit model

Galantis uses a flat rate: 1 delivered Conversation = 1 credit, regardless of destination country or template category. Meta’s per-country and per-category charges still apply on the Meta side, but they don’t change how many Galantis credits a delivered message consumes. Credits come from three places — in this deduction order:
1

Plan allowance

Each plan includes a fixed monthly Conversation allowance (Free 20, Starter 50, Growth 250, Scale 1,000, Enterprise 2,000). These are spent first.
2

Monthly Conversation tier

If you added a tier ($1 = 100 credits, 68 tiers from $5 to $5,000), those credits are spent after the plan allowance.
3

Send-time upgrade

If both are depleted mid-campaign, Galantis blocks new sends and prompts an instant tier upgrade. Existing in-flight sends complete on the current balance.
Want to add or change a tier? See Tiers & upgrades for the full list and how upgrades work.

​
Counting happens on delivery

Usage is recorded at the point of delivery, not when you click Send.

​
Estimation vs. final usage

Before sending a campaign, Galantis shows an estimate of required Conversations. Final usage is reconciled based on actual delivered messages. Estimates can differ from final usage for the following reasons:
  • Delivery rate differs from expected
  • Segment size changes between estimate and send
  • Recipient country distribution shifts (affects Meta’s charges, not your Galantis credit count — but estimates may show both)

​
Examples

You launch a campaign with a template message. The message is delivered successfully.Result: 1 Conversation credit consumed per delivered recipient.

​
Conversations vs. Inbox Threads

The Inbox module also uses the word “conversation” to describe support threads. To avoid confusion, this documentation uses two consistent terms:
  • Conversations (or credits) — the billing unit for delivered campaign and automation messages
  • Inbox Threads — support threads handled in the Inbox module, billed separately per agent seat

Inbox add-on

How Inbox Threads are priced and counted separately from platform Conversations.

​
Developer notes

This section is intended for engineers and QA. Customers can skip it.
Delivery webhooks can be retried. Deduction must be idempotent on message_id to avoid double-charging.
  1. Plan included Conversations
  2. Monthly tier Conversations
If both are insufficient:
  • Block new campaign sends
  • Prompt immediate tier upgrade
  • Pause automation sends (policy choice)

Tiers & upgrades

The 68 Conversation tiers, the $1 = 100 credits rate, and how upgrades work.

Usage & blocking

Where to track usage and what happens when you run out of Conversations.