Discuss Your Deployment
TextEnvoy SMS Switch
Discuss Your Deployment

PRICING MODEL · PRE-LAUNCH

Software and cloud. One planned hourly offer.

Hourly pricing is planned to cover TextEnvoy software and your dedicated Cloudfonica instance together. Each plan sets a monthly cap of SMS parts and a TPS limit; a larger plan has a higher hourly rate. You can upgrade or downgrade any instance at any time, so your platform cost follows your traffic. You pay your SMPP suppliers separately for SMS traffic. Rates are not yet published.

Discuss Your Deployment

Pre-launch inquiries only. Exact rates, service scope and billing policies remain subject to approval.

YOUR OPERATING COSTTWO PARTS
HOURLY · PLANNEDSoftware + cloud instancePriced by your plan’s SMS cap and TPS
PER YOUR SUPPLIER TERMSSMS terminationPaid directly to your suppliers per billable part
SMS termination is supplied and billed by your own SMPP providers.

PRICING MODEL · PLANNED FOR LAUNCH

One platform offer. Separate supplier costs.

Understand the two parts of your operating cost before discussing deployment sizing.

TEXTENVOY + CLOUDFONICA

Software + cloud instance

Planned hourly pricing

TextEnvoy switching software and dedicated cloud infrastructure in one offer.

  • Plans set by monthly SMS cap and TPS limit
  • Support and maintenance defined in service terms
  • Rates and billing rules subject to approval
Discuss Your Deployment
YOUR SUPPLIER AGREEMENTS

SMS termination

Paid to your suppliers

Your negotiated destination rates and billable message segments determine traffic costs.

  • You bring your own SMPP supplier accounts
  • Routes and message credits are separate
  • Supplier terms govern supplier charges
Discuss your traffic profile →

Before committing, confirm the hourly rate, billing increments, stopped-resource charges, resizing impact, and when charges end after deletion. Pricing and service availability will be confirmed before deployment.

What we need to scope your deployment

Start with your expected traffic, customer connections and supplier setup. These help us discuss an appropriate instance size and the operations your business needs.

Before a deployment commitment, the discussion should cover:

  • Plan match: Choosing the monthly SMS cap and TPS that fit your active SMPP/HTTP connections and peak submission patterns. At the cap, sending pauses until the next month or a plan upgrade.
  • Approved operational & infrastructure scope: Confirming exact commercial terms, currency, applicable taxes, minimum billing increments, and resource policies before any commitment is made.
  • Planned lifecycle alignment: Explaining how planned Cloudfonica instance resizing and lifecycle controls will interact with billing once verified for commercial release.

Four questions to ask about your platform costs

Use these questions to compare the scope of each offer, alongside its quoted price.

  1. 01

    What does the platform price include?

    Check software, cloud resources and operational responsibilities together. TextEnvoy plans a combined software and cloud offer, with support and maintenance scope set in the service terms and backups as a paid add-on.

  2. 02

    Can your customers use their required protocols?

    TextEnvoy supports customer connections over SMPP and the HTTP sending API. Each plan sets a monthly SMS cap and a TPS limit; plan rates are not yet published.

  3. 03

    Which daily operations does it support?

    Evaluate the workflows your staff need: customer and supplier connections, configured routes, destination rates, prepaid credit and message inspection.

  4. 04

    Who supplies and bills the SMS traffic?

    With TextEnvoy, you bring your own SMPP supplier accounts. Their destination rates and billing rules determine your termination costs, separately from the planned platform charge.

Peak traffic bursts and multi-part SMS segments

Two traffic details help us discuss capacity: the busiest sending periods and the number of SMS parts in each message.

Monthly volume does not equal peak throughput

Sending 3 million SMS spread evenly across thirty days places minimal sustained load on a switch, whereas sending the same 3 million SMS inside concentrated daily OTP spikes or promotional windows requires substantially higher concurrent session, queue, and DLR processing capacity. Sharing both your monthly range and expected peak submission behavior helps us size responsibly.

Logical messages vs. billable SMS parts (segments)

A single long API submission from a customer application is often split into multiple concatenated SMS parts over SMPP—up to 160 characters (153 per part when concatenated) using standard GSM-7 encoding, or 70 characters (67 per part when concatenated) when messages contain Unicode (UCS-2) scripts or symbols common across South Asia, the Middle East, and multilingual regions. Both upstream SMPP suppliers and switch traffic logs account for multi-part segments alongside logical requests.

SEGMENT CALCULATOR

How many billable parts is your message?

Paste a typical message. Its characters decide the encoding, and the encoding decides how many SMS parts your supplier carries.

Characters per SMS part
EncodingSingle SMSPer part when concatenated
GSM-7160153
UCS-2 (Unicode)7067

Uses the standard GSM 03.38 alphabet and concatenation with a 6-byte user data header. Characters such as € [ ] { } ~ ^ \ | use two GSM-7 positions. Suppliers can handle encoding differently; confirm how each one bills.

Talk through your traffic and operating costs.

Share your estimated volume range, business stage, and supplier readiness to start a pre-launch commercial discussion.

Discuss Your Deployment