> For the complete documentation index, see [llms.txt](https://help.smartico.ai/welcome/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.smartico.ai/welcome/technical-guides/communication-gateways.md).

# Communication gateways

Communication gateways connect Smartico to third-party messaging providers and client systems to deliver multi-channel marketing campaigns across Email, SMS, Instant Messaging (WhatsApp, Viber, RCS), Telegram, Push Notifications, and Voice (IVR).

Gateways are configured in the Smartico Back-Office under the **Label** tab in the respective gateway sections (**Mail Gateways**, **Instant Messages**, **Push**, etc.). Each configured gateway defines the authentication credentials, sender identifiers, and callback URLs required to send messages and track real-time delivery statuses (Sent, Delivered, Opened, Clicked, Bounced, Unsubscribed) within Smartico campaign journeys and analytics.

## Guides in this section

### Email Gateways

* [**Supported Mail gateways**](/welcome/technical-guides/communication-gateways/supported-mail-gateways.md): Complete setup guides, required credentials, DNS verification (SPF/DKIM), and webhook callback configurations for supported email service providers (including Mailgun, SendGrid, Infobip, Mailchimp Transactional (Mandrill), GetResponse, and others).
* [**Branded Links**](/welcome/technical-guides/communication-gateways/branded-links.md): Instructions for configuring custom tracking subdomains (CNAME) for email click and open tracking to protect sender reputation and improve inbox deliverability.

### SMS & Instant Messaging

* [**Instant Messages Gateway guide**](/welcome/technical-guides/communication-gateways/instant-messages-gateway-guide.md): Overview of configuring instant messaging channels in the Back-Office, including SMS, RCS, Viber, WhatsApp, Telegram bots, and Custom IM.
* [**Supported SMS gateways**](/welcome/technical-guides/communication-gateways/supported-sms-gateways.md): The SMS providers Smartico supports, with the Back-Office fields and the provider-side setup.
* [**Supported WhatsApp gateways**](/welcome/technical-guides/communication-gateways/supported-whatsapp-gateways.md): The WhatsApp Business API providers, their fields and setup.
* [**Supported Viber gateways**](/welcome/technical-guides/communication-gateways/supported-viber-gateways.md): The Viber providers, their fields and setup.
* [**Supported RCS gateways**](/welcome/technical-guides/communication-gateways/supported-rcs-gateways.md): The RCS providers, their fields and setup.

### Push Notifications

* [**Custom push gateways**](/welcome/technical-guides/communication-gateways/custom-push-gateways.md): How to integrate custom web and mobile push delivery providers using token-based or user-based payload models alongside standard Google Firebase Cloud Messaging (FCM).

### Secured & Custom Integrations

* [**Secured Messaging Gateways (Email/SMS/IM)**](/welcome/technical-guides/communication-gateways/secured-messaging-gateways-email-sms-im.md): Architecture and API contract for sending messages through client-hosted endpoints without exposing player email addresses or phone numbers (Zero-PII mode).
* [**Reverse integration: messaging**](/welcome/technical-guides/communication-gateways/reverse-integration-messaging.md): Setting up real-time outbound HTTP requests from Smartico to external client endpoints whenever a message asset is dispatched.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.smartico.ai/welcome/technical-guides/communication-gateways.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.