CHANNELS & PROVIDERS

Meet customers on the right channel.

Recognizable channels. Clear responsibilities. Check what is available and what needs separate qualification before planning your launch.

CHANNELS & PROVIDERS

Your service. The right channel.

The channel reaches your customer. Servinexa runs the workflow behind it.

One workflow. Qualified connections.
Illustrative channel map, not an activation status. Check each channel below.

Web Chat

Available for approved releases

Run approved web-chat workflows on our managed cloud, with Production setup and activation agreed with Servinexa.

Provider route
Servinexa-managed Runtime

USSD

Production qualification pending

The planned connection requires provider access, a shortcode and a qualified USSD adapter. It is not yet available in managed Production.

Provider route
Mobile operator or USSD gateway

WhatsApp

Production qualification pending

The planned connection requires a business account, an approved sender and a qualified messaging adapter. It is not yet available in managed Production.

Provider route
Meta or a WhatsApp Business provider

Messenger

Not available

A Messenger adapter is not available in this installation. A future connection needs separate provider access, implementation and qualification.

Provider route
Meta business messaging

SMS

Not available

SMS sending and delivery receipts are not enabled. Sender approval, provider contracts and a qualified SMS adapter are separate requirements.

Provider route
Mobile operator or SMS provider

Phone

Not available

Voice calls and IVR are not enabled. Phone numbers, call routing, provider access and a qualified voice adapter require a separate rollout.

Provider route
Voice or telephony provider

Provider accounts, approvals, numbers, shortcodes and third-party fees are separate unless your agreement says otherwise. Signup does not activate a telecom or messaging provider.

Plan a provider connectionSee the integration roadmap

LOOKING AHEAD

Future channel integrations

Our roadmap extends beyond the current rollout. Telegram is a planned adapter; the other channels below are integration candidates, not available services or guaranteed delivery commitments.

No launch dates are committed. Every connection depends on provider access, permissions, technical feasibility and separate qualification. Channel-specific consent, session windows, identity rules and features still apply.

Messaging & business inboxes

Telegram

Planned adapter

A planned bot adapter for customer conversations, with provider-specific consent, message handling and qualification.

Provider route
Telegram Bot API

Instagram Direct

Roadmap candidate

Explore professional-account messaging, subject to Meta permissions, conversation windows and a separately qualified adapter.

Provider route
Meta Instagram Messaging

Viber

Roadmap candidate

Explore approved business messaging with sender registration, provider access and separate commercial terms.

Provider route
Viber business messaging provider

LINE

Roadmap candidate

Explore official-account conversations with channel-specific consent, messaging limits and adapter qualification.

Provider route
LINE Messaging API

WeChat

Roadmap candidate

Explore official-account messaging where provider access, regional requirements and account approval permit it.

Provider route
WeChat Official Accounts

Apple Messages for Business

Roadmap candidate

Explore business conversations through an approved provider, with separate business registration and rollout qualification.

Provider route
Apple-approved messaging provider

RCS

Roadmap candidate

Explore rich business messaging with brand approval, supported device and carrier coverage, and a qualified provider route.

Provider route
RCS business messaging provider

Workplace & community

Slack

Roadmap candidate

Explore workspace conversations through an installed app with explicit workspace permissions and administrator approval.

Provider route
Slack apps and bot APIs

Microsoft Teams

Roadmap candidate

Explore approved Teams apps and bot conversations, subject to tenant policy, administrator consent and adapter qualification.

Provider route
Microsoft Teams app platform

Discord

Roadmap candidate

Explore approved community-server interactions with restricted bot permissions, provider policies and a qualified adapter.

Provider route
Discord bot and application APIs

Google Chat

Roadmap candidate

Explore Google Workspace chat apps with account permissions, administrator approval and separate connection qualification.

Provider route
Google Chat apps

Email, apps & agents

Email

Roadmap candidate

Explore asynchronous email journeys with verified senders, consent, delivery handling and safe reply correlation.

Provider route
Approved email provider

In-app messaging

Roadmap candidate

Explore embedded conversations with authenticated application sessions, explicit user permissions and a qualified client integration.

Provider route
Your approved web or mobile application

Push notifications

Roadmap candidate

Explore opt-in notifications with device-token protection and delivery controls. Notifications are not a two-way conversation adapter.

Provider route
Approved mobile or browser push provider

AI agents & MCP

Roadmap candidate

Explore opt-in access to selected capabilities through agents and MCP with explicit tenant authorization. This does not grant automatic access to all AI assistants.

Provider route
Approved agent interfaces

An idea is enough to get started.

Create your Developer account and make your first flow.

Create your free Sandbox