Skip to main content
OneXtel plugins let your team send messages through OneXtel from the tools they already work in — your CRM, your marketing automation platform, your storefront. Campaigns are built and triggered where they always were; OneXtel handles template delivery, carrier routing, delivery reports, and inbound replies underneath.

​
Available plugins

​
What each plugin covers

Every plugin covers the same four areas. What differs is how much of each the host platform itself can express — a limitation of the platform, not of OneXtel.

Outbound messaging

Send approved templates and, where the channel allows, free-form messages. Supported message types vary by plugin — see each page.

Template handling

Templates approved in OneXtel are made available inside the host platform, so campaign builders select from the same approved list.

Delivery reports

Sent, delivered, read, and failed events flow back into the host platform’s own reporting, so campaign performance stays in one place.

Inbound messages

Customer replies are routed back to the host platform where supported. Some platforms cannot receive inbound at all — this is called out per plugin.

​
Channel coverage

​
Common requirements

Whichever plugin you use:
  • An active OneXtel account with an API key for the channels you intend to send on. Every setup starts by copying your API key from API → Show API Key in the OneXtel portal.
  • Approved templates. WhatsApp and RCS templates must be approved in OneXtel before a campaign can use them, and SMS templates must be DLT-registered where applicable. See WhatsApp templates and RCS templates.
  • A registered sender. A WhatsApp Business number, an RCS agent, or an SMS sender ID, depending on channel. Every plugin also accepts a pool in place of a single sender — see below.
  • Matching templates. The template name and ID must match between the host platform and OneXtel exactly. A change to either on either side breaks the send.
  • A callback configured in OneXtel. Delivery reports and inbound messages only reach the host platform once the corresponding callback is registered against your API key, under Configuration → Add New Callback in the portal.

​
Pools instead of a single sender

Anywhere a plugin asks for a sender, you can give it a pool instead — a group of sender profiles that OneXtel distributes traffic across.
A pool narrows what you can send. Only templates assigned to that pool are available to it, so a template belonging to a different profile will not resolve. Confirm which templates the pool carries before building campaigns against it.

​
Message categories

Templates are approved by category, and plugins send on these: Because templates are fetched per category, most platforms need a separate sender or channel configuration for each category you send on. The per-plugin pages show how each one expresses this.
Plugins are enabled per account. Contact your OneXtel account manager to have one provisioned, and to confirm which channels are available on your plan.

​
Coming soon

These connectors are in development. Contact your account manager if you need one of them on your roadmap.

​
Choosing between a plugin and the API

Use a plugin when campaigns are already built and triggered in the host platform, and you want messaging to live alongside the rest of that platform’s reporting. Use the API directly when you need message types or controls the host platform cannot express — every plugin is limited by what its platform’s campaign builder supports, and those limits are listed on each page.