Skip to content
Optima docs
ConsoleChannels

Channels

The screens that connect Optima to the services that send your messages and to the systems your journeys call.

The channel screens are where Optima is told how to reach people and which outside systems it may call. A campaign or journey decides what to say and to whom; the screens here decide which service actually carries the message.

ScreenUse it to
Delivery channelsConfigure the providers that send email, SMS, RCS, WhatsApp, Viber, push and webhook messages, choose the default for each channel, and test the connection.
Custom channelsDeclare a channel of your own, such as a call centre or a print bureau, so consent, campaigns and suppression can treat it as a channel.
External systemsRegister the HTTP services that journey action steps call, with their credentials kept out of the journey.

Delivery channels and External systems are under Settings → Integrations. Custom channels are managed at the bottom of the Delivery channels screen.

Licence and roles

Delivery channels and external systems are part of the Campaign package (the delivery channels and external systems features). If your contract leaves one out, its entry does not appear in the navigation. Reading needs the integration_viewer role; creating, testing, changing and deleting needs integration_editor (or campaign_admin for providers and systems), or another role your administrator has given access to this area — see Licences and roles.

How the pieces fit

  • A channel is a way of reaching a person: email, SMS, push and so on.
  • A provider is a configured service that carries one channel, for example a Mailgun account for email. A channel can have any number of providers, and exactly one of them is the default.
  • A campaign or journey that does not name a provider uses the channel's default.
  • An external system is not a way to reach a person. It is a service a journey asks a question of, or tells something to, and it never appears in a channel picker.

Secrets you enter on these screens (API keys, passwords, tokens, signing secrets) are stored encrypted and are write-only: once saved they are never shown again, only replaced or cleared.

On this page