Connect a Messaging Channel

What it is

This guide shows you how to connect a messaging channel to BotBat so you can send and receive messages through that channel. A connected channel is the foundation for chatbot deployment, campaign delivery, and inbox conversations. Without at least one connected channel, BotBat cannot communicate with your customers.

BotBat supports multiple channel types: WhatsApp Business API (via Meta Cloud API or a Business Solution Provider), Telegram, Facebook Messenger, and SMS (through providers such as Twilio, MessageBird, and Vonage). Each channel type requires specific API credentials and a webhook configuration so BotBat can both send outbound messages and receive inbound messages and delivery status updates. By the end of this guide, you will have a fully verified, bidirectional channel ready for use.

When to use

• Initial setup: You are setting up BotBat for the first time and need to connect your primary messaging channel before deploying chatbots or launching campaigns.
• Adding a channel: You want to expand to a new platform (for example, adding Telegram alongside your existing WhatsApp connection) to reach customers on their preferred channel.
• Switching providers: You are migrating to a new SMS or WhatsApp provider and need to reconfigure the connection with updated credentials and webhook URLs.

Step 1: Navigate to the Channels page

Open the BotBat Console sidebar and navigate to Settings > Channels (or Integrations > Channels, depending on your console version). This page lists all currently connected channels, showing the channel name, type, provider, status (connected, disconnected, or error), and last activity timestamp.

From this page you can add new channels, edit existing channel configurations, disconnect channels, and view connection health indicators. If no channels are connected yet, you will see an empty state with a prompt to add your first channel.

Step 2: Start the channel setup wizard

Click the Add Channel button in the top-right corner to open the channel setup wizard. The wizard walks you through provider selection, credential entry, verification, and webhook configuration in a step-by-step flow.

Select your channel type and provider from the list. The available options are displayed as cards with the provider logo, name, and a brief description. If you are unsure which WhatsApp option to choose, use WhatsApp Cloud API for direct Meta integration or select your BSP name if you use a Business Solution Provider.

Channel Type	Provider Options	Key Requirements
WhatsApp	Meta Cloud API, 360dialog, Gupshup, Infobip, other BSPs	Business-verified Meta account, approved phone number, permanent access token.
Telegram	Telegram Bot API	Bot created via BotFather, bot token.
Messenger	Facebook Messenger (Meta)	Facebook Page, Page Access Token, App Secret, webhook verification token.
SMS	Twilio, MessageBird, Vonage, other supported providers	Provider account, API credentials (SID/Auth Token or API key), sender number or sender ID.

Step 3: Enter API credentials

After selecting a provider, the wizard presents a credentials form with fields specific to that provider. Fill in each required field using values from your provider's dashboard. All credential fields are encrypted at rest and in transit.

The following table details the required credentials for each major provider:

Provider	Required Fields	Where to Find Them
WhatsApp Cloud API	Phone Number ID, WhatsApp Business Account ID, Permanent Access Token	Meta Business Suite > WhatsApp > API Setup. Generate a permanent token via a System User in Business Settings.
Telegram	Bot Token	Open Telegram, message @BotFather, use the /newbot command, and copy the token provided.
Facebook Messenger	Page Access Token, App Secret, Verify Token	Meta Developers Portal > Your App > Messenger Settings. The App Secret is in the App Dashboard under Settings > Basic.
Twilio (SMS)	Account SID, Auth Token, Sender Phone Number	Twilio Console > Account Dashboard. The sender number must be a Twilio number or a verified caller ID.
MessageBird (SMS)	API Key, Originator (sender name or number)	MessageBird Dashboard > Developers > API Access.
Vonage (SMS)	API Key, API Secret, Sender Number	Vonage API Dashboard > Settings.

Double-check each value carefully before proceeding. Common errors include trailing whitespace in tokens, using a temporary token instead of a permanent one, and entering the wrong Account ID.

Step 4: Verify the connection

Click the Verify button to test your credentials. BotBat sends a lightweight API request to the provider to confirm the credentials are valid and the account has the required permissions. The verification result is displayed immediately.

Verification Result	Meaning	Action
Success (green checkmark)	Credentials are valid, and BotBat can communicate with the provider.	Proceed to the next step.
Authentication Failed	The token, SID, or API key is incorrect or expired.	Re-check credentials in the provider dashboard and update the form.
Permission Denied	The credentials are valid but lack required scopes or permissions.	Grant the necessary permissions (messaging, webhook management) in the provider dashboard.
Network Error	BotBat could not reach the provider's API endpoint.	Check your network configuration, firewall rules, and provider service status.

If verification fails, fix the issue indicated in the error message and click Verify again. Do not proceed until verification succeeds, as the webhook step depends on a valid connection.

Step 5: Configure the webhook

After successful verification, BotBat generates a unique webhook URL for your channel. This URL is the endpoint that the messaging provider will call whenever an event occurs, such as an inbound message, a delivery receipt, or a read receipt.

Copy the webhook URL using the copy button and register it in your provider's dashboard. The registration process varies by provider:

• WhatsApp Cloud API: Go to Meta App Dashboard > Webhooks > Edit Subscription. Paste the URL, enter the verify token shown in BotBat, and subscribe to the messages, message_deliveries, and message_reads fields.
• Telegram: BotBat registers the webhook automatically via the Telegram Bot API. No manual configuration is needed.
• Messenger: Go to Meta App Dashboard > Webhooks. Add a callback URL, paste the BotBat URL, enter the verify token, and subscribe to messages, messaging_postbacks, and message_deliveries.
• SMS (Twilio): Go to the Twilio Console > Phone Numbers > your number > Messaging Configuration. Set the "A message comes in" webhook URL to the BotBat URL using HTTP POST.
• SMS (MessageBird/Vonage): Configure the inbound message webhook URL in the respective provider dashboard under your number or application settings.

Make sure you subscribe to all required event types. Missing subscriptions (for example, omitting delivery receipts) will cause BotBat to lose visibility into message delivery status.

Step 6: Send a test message

Click Send Test Message in the wizard. Enter a phone number or chat ID (your own personal number is recommended) and click Send. BotBat sends a test message through the newly connected channel to confirm outbound delivery works.

Confirm the message arrives on your device. Then reply to the message from your device to verify that inbound message handling works correctly. BotBat should display the inbound reply in the test results panel or in the Inbox. This round-trip test confirms that both outbound sending and inbound webhook reception are functioning properly.

If the outbound message does not arrive, check that the recipient number is correct and that your provider account has sufficient balance or quota. If the inbound reply is not received, verify that the webhook URL is registered correctly and that your infrastructure allows incoming connections from the provider's IP ranges.

Common pitfalls

• Expired or scoped tokens: WhatsApp and Messenger tokens can expire or lack required permissions. Always use permanent tokens generated via System Users, and grant all messaging-related scopes during token creation.
• Webhook URL not registered: If you skip the webhook registration step, BotBat can send messages but cannot receive replies or delivery status updates. Always complete webhook registration and verify it is active in the provider dashboard.
• Firewall blocking callbacks: If your infrastructure uses a firewall or WAF, ensure the provider's IP ranges are allowlisted. Meta, Twilio, and other providers publish their IP ranges in their documentation. Blocked callbacks result in missed inbound messages.
• Using test credentials in production: Some providers offer sandbox or test credentials with limited functionality. Make sure you use production credentials for your live channel configuration.
• Trailing whitespace in tokens: Copy-pasting tokens from emails or documents sometimes introduces invisible whitespace characters. Trim all credential values before pasting them into the form.

tip

After connecting a channel, send yourself a message and reply to it. This round-trip test confirms both outbound delivery and inbound webhook reception are working. Repeat this test any time you update credentials, change webhook URLs, or modify provider settings. It is also a good practice to set up monitoring or alerts for webhook failures so you are notified immediately if inbound message processing stops working.

• Channel List
• Add Channel Wizard
• Provider Selection
• Credentials Form
• Connection Verification
• Webhook Configuration
• Test Message