INFRASTRUCTURE · CLOUDFONICA CLOUD PLATFORM

Cloud Deployment & Operations

The planned service lets your business create dedicated TextEnvoy instances on Cloudfonica, as many as you need, each in the cloud region you choose. Your team manages customers, suppliers, routes and pricing. We handle platform setup, maintenance and monitoring under agreed service terms; backups are available as a paid add-on.

Discuss Your Deployment

Pre-launch inquiries only. Cloudfonica instance creation, resizing and deletion are planned and still require verification.

INTENDED LAUNCH MODELCLOUDFONICA

Your customersSMPP / HTTP

YOUR DEDICATED INSTANCE

TextEnvoy switch
Staff portal
Traffic and billing records

EXPERT TECHNICAL SUPPORTInstallation · updates · monitoring · backup add-on

Your suppliersSMPP · outbound IP on their allowlists

Illustration · Cloudfonica lifecycle controls are planned for launch

DEPLOYMENT & OPERATIONS

Clear ownership at every layer.

Your team runs the SMS business, our experts support the platform, and your suppliers handle onward delivery.

01 / OUR TEAM

The platform

Dedicated TextEnvoy instance on Cloudfonica.

Switch installation and updates
Platform monitoring, with backups as a paid add-on
Platform security and incident support

Scope governed by service terms

02 / YOUR STAFF

The SMS business

Your customers, commercial rules and supplier relationships.

Customer onboarding and compliance
Routes, rates and prepaid credit
Supplier accounts and first-line customer support

Managed in the TextEnvoy staff portal

03 / YOUR SUPPLIERS

Onward delivery

The SMPP providers you contract with directly.

Outbound SMS termination
Onward routing to mobile networks
Supplier-reported delivery receipts

Subject to your supplier agreements

Prepare for the discussionSupplier readinessExpected traffic and peak burstsLicensing and sender approvals

Discuss your deployment readiness →

PLANNED LAUNCH DIRECTION — SUBJECT TO IMPLEMENTATION & VERIFICATION

Planned Cloudfonica service lifecycle controls

For launch, customers are intended to manage their instances through Cloudfonica, with our technical team handling platform setup and maintenance:

Create (Planned): Create dedicated TextEnvoy SMS Switch instances from your Cloudfonica account, as many as your business needs, each with its own plan and a cloud region in North America, Europe or Asia-Pacific. Each instance’s hourly rate is charged to your account balance. A region choice is not a data-residency or regulatory commitment.
Upgrade & Downgrade (Planned): Move any instance to a larger or smaller plan at any time as your A2P traffic changes; a smaller plan lowers that instance’s hourly rate.
Destroy (Planned): Retire an instance through Cloudfonica when a deployment is no longer needed.

Important pre-launch transparency: Self-service creation, resizing, and destruction remain under engineering implementation and verification. Activation times, resize interruption windows, outbound IP persistence across resizes, data export/retention windows, and final billing cutoff rules will be published only after technical verification and final service terms are approved.

Your business, backed by our technical expertise

Platform support and business responsibilities
Area	Our Technical Responsibilities (Subject to Agreed Service Terms)	Managed by Your Team
Cloud Infrastructure	Setting up and maintaining each dedicated Cloudfonica cloud instance hosting TextEnvoy	Create and manage instances, choosing each one’s plan and region, in your Cloudfonica account once those controls are available; no separate server is needed.
Switch Software Lifecycle	Initial TextEnvoy installation, configuration baseline, and software version upgrades	Testing internal customer/supplier integrations when notified of planned maintenance
Monitoring & Backups	Platform-level health monitoring; scheduled backups for clients who buy the backup add-on	Exporting or reconciling commercial rate/billing records for internal finance workflows
Security & Incidents	Underlying OS/platform security hygiene and platform-level incident investigation	Safeguarding staff portal credentials, customer API keys, and upstream supplier passwords
Telecom & Supplier Operations	Providing outbound instance IP details required for your supplier whitelisting requests	Negotiating supplier contracts, submitting IP whitelist requests, and managing supplier balances
Compliance & Daily Business	Maintaining the switching platform within agreed service terms	Telecom/messaging licences, customer KYC, sender ID / template approvals, routing, rates, prepaid credit, and customer support

What your team should prepare before deployment

Before moving from pre-launch discussion to instance onboarding, confirm these six prerequisites:

1. Upstream SMPP supplier account(s) At least one active or test-ready SMPP supplier connection (host, port, credentials, bind mode, and throughput allowance).
2. Supplier IP whitelisting process Point of contact or portal access with each upstream supplier to whitelist your dedicated TextEnvoy instance’s outbound IP address(es).
3. Regulatory & licensing compliance Required local or international telecom, aggregator, or A2P messaging registrations for the markets you serve.
4. Customer KYC & sender governance Internal procedures for verifying downstream customers and obtaining required sender ID or content template approvals.
5. Operations staff ownership Designated internal staff members to manage routes, destination rates, prepaid credit updates, and first-line customer inquiries.
6. Traffic & burst profile Realistic estimates of monthly volume, peak submission bursts, active SMPP bind counts, and character encoding mix (GSM-7 vs. Unicode).

From first discussion to a planned deployment

The proposed process includes a fit review, agreed terms and supplier testing. Service availability and supplier approvals determine when traffic can begin.

STEP 01
Technical Fit & Sizing Review: We review your inquiry, customer protocol mix (SMPP / HTTP), supplier bind count, and peak traffic profile to confirm fit and recommend a plan for each instance.
STEP 02
Commercial Quote & Service Terms: We share your deployment quote and applicable service terms covering operational responsibilities and billing rules.
STEP 03
Instance Creation on Cloudfonica: Once the service is available, you create your instances from your Cloudfonica account, choosing a plan and a cloud region for each. Our technical team handles switch setup and ongoing platform maintenance under agreed service terms.
STEP 04
Outbound IP Assignment & Supplier Whitelisting: We provide the instance connection details so your team can complete upstream supplier IP whitelisting and verify test SMPP binds. (External supplier approval turnaround is controlled by your suppliers.)
STEP 05
Staff Portal Handover & Controlled Traffic Start: Your operations staff configure supported routes, customer rates, and prepaid credit balances before transitioning live customer traffic.

How we evaluate instance sizing

Two SMS businesses sending the same monthly volume can place very different loads on a switch. During discovery, we look beyond monthly totals to evaluate peak submission bursts (such as morning notification spikes or OTP waves), concurrent downstream and upstream SMPP binds, multi-part concatenated message ratios, and upstream supplier DLR return behavior.

STEADY DAY

OTP AND CAMPAIGN BURSTS

Illustrative example: two days with roughly the same message volume. The dashed line marks each day’s peak, and sizing has to account for the peak, not only the total.

Evaluating a transition from an existing SMS switch

If you already operate another switching platform, pre-launch discovery focuses on verifying protocol compatibility, checking whether your current workflows rely on features outside TextEnvoy’s scope (such as end-customer web portals, least-cost routing or automated invoicing), and planning parallel supplier IP whitelisting for a controlled customer-by-customer cutover. We assess compatibility openly and do not promise automated historical data migration or zero-downtime cutovers.

Review your infrastructure and onboarding readiness with us

Share your current setup and supplier readiness to scope a dedicated Cloudfonica deployment.

Discuss Your Deployment