Skip to content
Request rates
Menu
Request a test routeContact on Telegram

DraftThis page is a draft. Values set in grey monospace are placeholders and are not confirmed yet.

How it works

From your wanted list to live traffic at volume.

Eight stages, each with a target time. KYC runs both ways: you get our trust pack before we ask for your documents.

Request ratesRequest a test route
NAMED_ROUTING_LEADROUTING_LEAD_TITLEContact on Telegram

Onboarding

The eight stages.

  1. Stage 1: Contact

    You do
    Fill in a form, scan our QR code at an event, or message us
    We do
    A named person replies and asks for your wanted list
    Target
    FIRST_REPLY_TIME

  2. Stage 2: Company check

    You do
    Email, company, role, use case, volume band, top destinations
    We do
    A short check of your company and domain
    Target
    VERIFY_TIME

  3. Stage 3: Quote

    You do
    Share your wanted list (MCC/MNC); NDA if you need one
    We do
    A dated rate deck for those destinations: route class, sender-ID rule, validity, billing basis
    Target
    RATE_DECK_TURNAROUND after a passed company check

  4. Stage 4: Bind

    You do
    Send your source IPs; choose SMPP or HTTP
    We do
    Bind credentials, IP allow-list, TPS per bind, onboarding spec
    Target
    TEST_BIND_LEAD_TIME from receipt of your source IPs, after a passed company check

  5. Stage 5: Test

    You do
    Test the destinations that matter most on your own tester, against criteria agreed in advance
    We do
    FREE_TEST_ALLOWANCE free messages on up to TEST_DESTINATIONS_MAX destinations, handled exactly like production
    Target
    Verdict within TEST_VERDICT_DAYS

  6. Stage 6: KYC and contract

    You do
    Company documents, ownership, signatory; contract with AUP and AIT clause
    We do
    Our trust pack and company documents; sender-ID registrations where needed
    Target
    KYC_DAYS

  7. Stage 7: Go live

    You do
    Prepay, or use agreed terms
    We do
    Production opens on every destination on your rate deck
    Target
    HOURS_TO_LIVE after KYC and payment

  8. Stage 8: Review

    You do
    Add destinations and volume as your traffic grows
    We do
    Monthly per-destination report; postpaid review after POSTPAID_AFTER_CYCLES clean billing cycles
    Target
    Monthly

Every new buyer goes through these stages, in this order; you choose which destinations to test. CONFIRM_BEFORE_PUBLISH

Request a test route

KYC and sender-ID registration set the pace.

KYC depends on paperwork on both sides. Some destinations need sender-ID registration, which can take weeks. We flag those on the rate deck, before you plan a launch.

Onboarding spec

Connection parameters for your bind.

Onboarding spec: connection parameters and their values
ProtocolsSMPP SMPP_VERSIONS; HTTP API HTTP_API
Bind typesBIND_TYPES
SecurityCONNECTIVITY_OPTIONS; IP allow-list CONFIRM_BEFORE_PUBLISH
ThroughputCOMMITTED_TPS_PER_BIND TPS committed per bind; window size WINDOW_SIZE; throttling above the limit THROTTLE_BEHAVIOUR
Keep-aliveAn enquire_link every ENQUIRE_LINK_INTERVAL
AddressingAccepted TON/NPI TON_NPI
EncodingGSM-7 and UCS-2 CONFIRM_BEFORE_PUBLISH; concatenation CONCAT_METHOD
ReceiptsRECEIPT_FORMAT; message_state and receipted_message_id TLVs CONFIRM_BEFORE_PUBLISH
ValidityDefault VALIDITY_DEFAULT unless set per message

KYC checklist

What we need from you.

  • Company registration documents
  • Ultimate beneficial owners (UBOs)
  • Telecom licences or authorisations where they apply
  • Authorised signatory
  • Traffic declaration (use case, origin, monthly volumes, sender IDs, sample content)
  • Billing contact

Re-verification: KYC_REVIEW_CADENCE.

Talk to the team.

Ask for rates on the destinations and traffic you send, request a test route, or pick a time to meet.

Request ratesRequest a test route