Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.digifist.com/llms.txt

Use this file to discover all available pages before exploring further.

Galantis supports connecting multiple WhatsApp Business phone numbers to a single workspace. Each number operates independently — it has its own sending identity, its own conversation threads, and its own quality rating in Meta. Using multiple numbers is appropriate for businesses that operate distinct brands, regions, or support functions under one Shopify store.

​
What this covers

  • When to use multiple phone numbers
  • How to add a number to an existing workspace
  • How numbers are used across campaigns, automations, and the Inbox
  • Quality and compliance considerations per number

​
When to use multiple phone numbers

Multiple brands — A Shopify store operating more than one brand may want each brand to have its own WhatsApp number so customers receive messages from a recognizable brand identity rather than a shared business number. Regional separation — Stores serving multiple markets may want country-specific numbers — a Mexican number for LATAM customers and a UAE number for MENA customers — so messages arrive from a local or familiar-looking number. Functional separation — Separating marketing sends from customer support conversations onto different numbers keeps the quality signals for each use case independent. A high-volume campaign number with some block rate does not drag down the quality rating of a support number used for high-satisfaction Inbox conversations. Dedicated high-volume sending — A number used exclusively for large campaign broadcasts will accumulate quality signals specific to broadcast behavior. Keeping it separate from a transactional number protects the transactional number’s quality.

​
Adding a phone number

1

Open WhatsApp Connection settings

Go to Settings → WhatsApp Connection in the Galantis dashboard.
2

Add a new number

Select the option to add a phone number. You will be prompted to go through the Meta OAuth flow again — or, if your current WABA access token has sufficient permissions, Galantis may be able to fetch additional numbers from the same WABA without a full re-authorization.
3

Select the number to add

Galantis fetches the phone numbers registered on your WABA. Select the additional number you want to connect.
4

Verify the number is active

After adding, confirm the number appears in your connected numbers list under Settings → WhatsApp Connection and is shown as active.
All phone numbers connected to a Galantis workspace must be registered on the same WhatsApp Business Account (WABA). Numbers from different WABAs cannot be connected to the same workspace. If you need numbers from multiple WABAs, contact Galantis support to discuss workspace configuration options.

​
How multiple numbers work in campaigns and automations

Campaigns — Each campaign is associated with a single phone number. Multiple numbers are supported per workspace, allowing different numbers to be used for different campaign sends. Automations — Each automation’s Action Nodes send from a specified phone number. If you have numbers segmented by region, you can build separate automation flows per region, each using the appropriate number, or use CUSTOMER_COUNTRY condition nodes to route customers to Action Nodes configured with different number assignments. Inbox — Conversations are associated with the phone number the customer messaged. Agents see conversations across all connected numbers in the unified Inbox.

​
Quality and compliance per number

Every connected phone number has its own independent quality rating in Meta. Actions taken on one number — block rates, template rejection patterns, message frequency — do not directly affect the quality rating of other numbers in the same workspace. This independence is one of the primary operational reasons to separate numbers by use case. A campaign number that absorbs the quality cost of high-volume promotional sends does not contaminate the quality rating of a support number used for Inbox conversations. Each number must maintain its own compliance posture:
  • Templates used on a number are reviewed against that number’s sending history and quality signals
  • Frequency caps on automations apply per number — a customer enrolled in an automation on Number A is not covered by frequency caps on Number B
  • Opt-outs (STOP replies) are processed per number — a customer who replies STOP to a message from Number A is opted out from Number A, but their consent state in Galantis is updated globally across the workspace
Consent opt-outs update the customer’s marketing_state globally in Galantis — not per phone number. A customer who replies STOP to any message from any connected number will be moved to UNSUBSCRIBED and excluded from all messaging across all numbers in the workspace. Managing separate opt-in lists per number is not supported at the consent state level.