Discuss Your Deployment
TextEnvoy SMS Switch
Discuss Your Deployment

PLATFORM · STAFF ADMINISTRATION PORTAL

Run your daily SMS operations in one portal.

Connect customers and suppliers, assign routes, set destination rates and manage prepaid credit. Follow each message from submission to the delivery status reported by your supplier.

Discuss Your Deployment

Built for application-to-person (A2P) SMS providers. Pre-launch inquiries are open; commercial service is not yet available.

STAFF PORTALFIVE WORKFLOWS
  1. 01
    CustomersInbound SMPP binds and HTTP API access
  2. 02
    SuppliersOutbound SMPP binds on your accounts
  3. 03
    RoutesConfigured customer-to-supplier assignments
  4. 04
    Rates & creditBalance and credit limit checked before forwarding
  5. 05
    Traffic logSwitch acceptance and supplier receipts
Workflow overview · Illustration

A staff portal for you. SMPP and HTTP for your customers.

Your operations team manages customers, suppliers, routing, rates, prepaid credit, and traffic records inside the TextEnvoy administration portal. Your messaging customers connect their software directly to your dedicated switch over SMPP or the HTTP sending API—TextEnvoy does not include a web self-service campaign portal for end SMS customers.

WORKFLOW 01 / CUSTOMER CONNECTIONS

Connect customer applications over SMPP or HTTP

Daily task: Create customer messaging accounts and issue inbound SMPP bind credentials or HTTP sending API access on your dedicated switch instance.

For your team: Manage SMPP and HTTP customer connections from the same staff portal.

Limit: Customer access is programmatic (SMPP / HTTP API). There is no end-customer web portal or campaign builder.

PRODUCT SCREENSHOT Staff portal · Synthetic test data

Staff portal, Inbound Clients: the customer Northstar Apps (system ID northstar_01), prepaid, balance $249.99, connected with 1 of 1 SMPP binds. Synthetic data.
Check each customer's SMPP access, prepaid balance and bind count in one list.

PRODUCT SCREENSHOT Staff portal · Synthetic test data

Staff portal, Outbound Clients: the supplier Gateway Alpha, connected (BOUND_TRX) over SMPP on the Gateway Alpha costs rate plan. Synthetic data.
See the live state of each outbound supplier bind, with its protocol and rate plan.

WORKFLOW 02 / SUPPLIER CONNECTIONS

Connect your SMPP suppliers

Daily task: Configure outbound SMPP connections to the upstream aggregators, messaging hubs, or carrier accounts your business contracts with directly.

For your team: Keep supplier connection settings and bind status together, so staff can check which connections are ready to carry traffic.

Limit: TextEnvoy supplies switching software, not SMS termination. A supplier bind does not imply direct mobile network operator (MNO) connectivity.

WORKFLOW 03 / ROUTE CONTROL

Choose the supplier route for customer traffic

Daily task: Assign inbound customer traffic to your connected outbound SMPP supplier binds using TextEnvoy’s supported routing rules in the staff portal.

For your team: See which supplier connection is assigned to customer traffic and review the configuration before making changes.

Limit: Routes follow your configuration: one supplier, failover or round-robin. No dynamic least-cost routing or MNP/HLR lookups.

PRODUCT SCREENSHOT Staff portal · Synthetic test data

Edit Route panel for Route BD 01: static route, order 10, active, single target connector Gateway Alpha (SMPP), with two attached filters: customer Northstar Apps and destination Bangladesh (880). Synthetic data.
Make each supplier assignment explicit: Route BD 01 sends Northstar Apps' +880 traffic to the Gateway Alpha connection, so staff can see exactly where it goes.

PRODUCT SCREENSHOT Staff portal · Synthetic test data

Billing & Balance for Northstar Apps: prepaid balance $249.99 USD, credit limit $0.00, delivery-based billing policy, and an audit ledger showing a $250 synthetic top-up and a $0.01 deduction for one delivered SMS. Synthetic data.
Control customer credit: top-ups and per-message charges post to an audit ledger, and you choose whether each customer is charged on submission, on attempt or on delivery.

WORKFLOW 04 / RATES & CREDIT

Set destination rates and manage customer credit

Daily task: Maintain customer rate sheets and update prepaid balances and credit limits that TextEnvoy checks before accepting customer traffic for outbound forwarding.

For your team: Check customer rates and available credit before forwarding traffic, and choose whether each customer is charged on submission, attempt or delivery.

Limit: Records support operations, not invoicing or accounting.

WORKFLOW 05 / TRAFFIC & DLR LOGS

Trace message status and billing records

Daily task: Search message logs to review customer submission timestamps, switch acceptance status, supplier-returned delivery receipts (DLRs), and per-message billing records.

For your team: Investigate delivery questions with the submission, supplier receipt and related billing records at hand.

Limit: Delivery status is what your supplier reports. Billing records are operational, not customer invoices.

PRODUCT SCREENSHOT Staff portal · Synthetic test data

Message details for one synthetic message: submitted at 20:33:51 UTC by Northstar Apps, sent via Gateway Alpha, source NORTHSTAR, placeholder destination 8801000000000, status Delivered, 1 segment, billing charged.
Follow one message from submission to supplier receipt: when it was accepted, which supplier connection carried it, what the delivery receipt reported, and whether it was charged.

OPERATIONAL CLARITY

Why TextEnvoy separates Submission Acceptance from Final Delivery

When your customer submits a message via SMPP or HTTP, submission acceptance means your TextEnvoy instance authenticated the request, verified available credit and route configuration, and accepted the message for outbound forwarding. Delivery information (DLR) arrives asynchronously from your upstream SMPP supplier as downstream networks process the message. Keeping these two states distinct in the staff portal helps your team pinpoint whether an issue occurred at customer submission or further downstream with a supplier.

Two sources of status

YOUR SWITCH
  • ACCEPTEDPassed authentication, credit and route checks
YOUR SUPPLIER · SMPP v3.4 RECEIPT STATES
  • DELIVRDDelivered
  • UNDELIVUndeliverable
  • EXPIREDValidity period expired
  • REJECTDRejected
  • UNKNOWNState unknown

Which receipt states appear depends on what each supplier returns.

Evaluate technical fit before we speak

TextEnvoy SMS Switch — Supported Scope & Current Exclusions
Capability Area Supported Scope in TextEnvoy SMS Switch Current Scope Boundaries & Exclusions
Downstream Customer Ingress Inbound SMPP binds and HTTP sending API on your dedicated switch instance No end-customer self-service web portal; no scheduled SMPP delivery
Upstream Supplier Egress Outbound SMPP client binds using your own supplier accounts TextEnvoy provides no SMS routes, carrier agreements, or message credits; a supplier bind does not imply direct MNO connectivity
Administration & Access Web administration portal for your internal operations staff No multi-tier sub-reseller portals or granular custom RBAC role matrices
Routing Control Single-supplier, failover and round-robin routes configured in the staff portal No dynamic LCR or MNP/HLR lookups
Commercial & Balance Control Destination rate management, prepaid balances and customer credit limits, a billing policy per customer, and operational billing records No tax calculation, automated invoicing, or payment processing
Traffic & Status Visibility Message traffic inspection, switch acceptance status, and supplier-returned DLR tracking DLR accuracy depends on upstream supplier reporting; no cross-server HA guarantees

Confirm whether TextEnvoy matches your switching workflow

Share your customer protocol mix, supplier setup, and operational requirements for a candid pre-launch fit review.

Discuss Your Deployment