Skip to content
Akedly
Your own SMS provider

Enable on integrations & cloning

An active provider sends no traffic until BYO SMS is enabled for the integration. Complete Add a provider — not applicable to a managed Vodafone provider, which Akedly builds — and Test & activate first, then enable it for an integration — optionally cloning a provider for integration-specific coverage.


Where to set it

On a Gateway, Headless or Legacy integration: open it from Integrations, then its Channels tab, and find Your own SMS provider. Build and test the provider first — or, for a managed Vodafone provider, fill in the parts you own and get it past its readiness gates. Creating and cloning a managed provider are gated on pilot provisioning, not withheld from you: once Akedly has provisioned your account you do both yourself, and the fixed managed fields stay fixed in the copy.

If Your own SMS provider says Not on your plan yet, your account does not have BYO SMS yet — arrange entitlement with Akedly.

On a One-way messaging (Utilities) integration the dashboard has no Your own SMS provider selector. One-way SMS always goes through your own provider, and the integration follows the account default unless you override it. Its Channels tab has an SMS switch and Retry failed WhatsApp messages by SMS; both refuse to turn on, with UTILITY_SMS_REQUIRES_BYO, until the integration resolves to BYO SMS on and an active, tested provider can route for it. If the account default is off, turn BYO SMS on for that one integration with the CLI, then turn on SMS on its Channels tab:

Turn BYO SMS on for a one-way integration

akedly integrations update <integration-id> --byo-sms on --yes

akedly utilities doctor reports the same step when SMS cannot send. See One-way messaging from the CLI.


Turn BYO SMS on for an integration

On a Gateway, Headless or Legacy integration, under Your own SMS provider, Use your provider has three settings that control whether this integration routes through BYO SMS.

ControlEffect
Account defaultselect

Follow the account-wide default Akedly sets for you — the customer dashboard has no account-wide switch, so contact Akedly to change it. The card shows the resolved result, such as "Resolved: BYO-SMS on — Following your account default (on)."

Onselect

Force BYO SMS on for just this integration — the self-serve way to enable it without an account change.

Offselect

Force BYO SMS off for this integration. OTP SMS then uses Akedly's senders where available. (The CLI's --byo-sms off on a one-way integration stops it sending SMS at all, because one-way SMS has no Akedly SMS route.)

Savebutton

Select Save on the Your own SMS provider card. Each card on the integration page saves on its own; Cancel drops the change.


How Akedly picks the provider

The dashboard has no per-country route check. The Channels tab's How codes reach your users drawing shows this integration's channel order and fallback, not which SMS provider sends to a given country; these rules decide that.

  • Name
    Integration copy first
    Type
    precedence
    Description

    An active provider cloned onto this integration wins over an active provider in your account registry.

  • Name
    Specific country beats catch-all
    Type
    coverage
    Description

    An active provider that lists the destination country wins over an active all-countries (catch-all) provider in the same scope.

  • Name
    Otherwise Akedly
    Type
    fallback
    Description

    For OTP, a destination no active provider covers falls back to Akedly's own SMS senders. When a one-way send resolves to SMS, it has no Akedly SMS fallback and returns a BYO routing error when no provider covers it. See the Reference for request-chain failure behavior.

Within one scope, active providers cannot overlap: each destination country belongs to at most one active provider, plus at most one catch-all. Akedly blocks activating a second provider that would claim a country already covered in the same scope.


Cloning a provider onto an integration

Under Providers on this integration, use Add from your providers to create a copy scoped to this integration. Adding or removing applies at once.

ControlEffect
Add from your providersbutton

Create an integration-specific copy of the registry provider, including its coverage and stored credentials. Once active, the integration copy takes precedence over the registry when both cover the same destination country.

Independent copycopy-by-value

Edits and tests on the copy never touch the original. The reverse holds too: updating the registry does not change existing clones — re-clone to refresh from an updated source.

Draft → Livestatus

A fresh copy starts off. It must pass its own test in this integration (Send a test), then be turned on (Turn on), before it can route. Follow the Test & activate process.

Own SMSbilling

The clone copies the source's provider settings, including any provider fee override. Its resolved Own SMS fee is shown on the card, for example "0.05 EGP / successful auth" (the default; an Akedly-set account or provider override may apply when no provider override is set).

Registry routingrouting

Cloning is optional. An active registry provider already routes for any integration that resolves to BYO SMS on. Clone only when one integration needs a different provider, coverage, or credentials than your account-wide registry default.


What's next

See the Reference for routing, failure behavior, billing, and dashboard errors.