Zayloft
Zayloft
Usage-based
Pay according to measurable service consumption such as messages, verification attempts, minutes, email volume or other billable units.
Zayloft pricing
Pricing that follows the service, destination and workload instead of forcing every customer into one flat global rate.
Communication costs vary by channel, destination, sender type, carrier path, message category and local requirements. Zayloft structures pricing so organizations can understand what drives usage and choose the commercial model that fits their operations.
Commercial models for different operating needs.
Exact rates can differ by market and product. This page explains the pricing framework without publishing fabricated rates.
Volume-based
Eligible higher-volume workloads can use negotiated tiers or route-specific commercial terms.
Enterprise agreement
Organizations with committed volume, multiple teams, credit requirements or tailored support can use negotiated arrangements.
Prepaid & account-funded
Where supported, usage can be funded in advance and deducted as billable activity occurs.
What determines pricing by service.
Each communications product has its own cost drivers, so pricing should reflect the actual service and route being consumed.
SMS
Destination, network, sender type, route, message segments, local fees and volume can affect price.
WhatsApp & rich messaging
Pricing can depend on channel rules, message category, destination and applicable platform charges.
Usually based on sending volume, service type, dedicated infrastructure options and account requirements.
Voice
Can depend on destination, origination, call duration, number resources, routing and enabled features.
Verification
May be priced by verification attempt, completed workflow, delivery channel, destination or agreed model.
AI & NLP services
Commercial terms depend on scope, model usage, data processing, integrations, evaluation and operational support.
SMS pricing follows the real delivery path.
A single flat SMS price cannot accurately represent every destination and route. Pricing can reflect the actual market, sender requirements, segmentation and connectivity used for the account.
Destination
Country, network and local termination economics can change the underlying cost.
Message length
SMS content may be billed in multiple segments depending on encoding and character count.
Sender type
Alphanumeric senders, long codes, toll-free resources and short codes can have different fees and requirements.
Route & quality
Commercial terms can vary according to the approved route, connectivity and service characteristics.
Currency should match the account, not a hard-coded website default.
Zayloft is structured for account-aware currencies and market-specific billing. The currency used for funding, invoices or commercial agreements should follow the approved account configuration.
Account currency
A customer account can be associated with the currency used for its approved billing arrangement.
Market-aware rates
Destination and channel rates can remain independent of the customer’s billing currency.
Conversion
Where conversion is required, the applicable method and timing should be disclosed in the billing flow.
Invoices
Enterprise invoices can reflect agreed currency, billing period, usage and approved adjustments.
Taxes, regulatory fees and third-party charges need clear treatment.
Communication services can attract taxes, carrier fees, sender-registration charges, number fees or other destination-specific costs.
Taxes
Applicable sales, consumption, value-added or similar taxes can depend on customer and billing jurisdiction.
Sender registration
Some sender types and destinations may require registration or recurring resource charges.
Numbers & resources
Virtual numbers, short codes, toll-free resources or other assets can carry setup or recurring fees.
Pass-through costs
Certain carrier, network or platform charges may be passed through where applicable and disclosed.
Enterprise pricing for complex workloads.
Organizations with sustained volume, multiple products, special routing requirements, credit terms, reseller models or dedicated operational needs can use a commercial structure aligned to the real workload.
Committed volume
Negotiate terms around measurable volume and destination mix.
Multiple products
Structure messaging, verification, voice, email and other services under one account relationship.
Credit & invoicing
Eligible organizations can use agreed invoicing, payment terms and credit controls.
Operational support
Commercial agreements can include suitable implementation and support arrangements.
Frequently asked questions
SMS costs vary materially by destination, network, sender type, route, segmentation and local fees. One global number would be misleading for many destinations.
Yes. Network economics, sender requirements and local charges can differ by destination and channel.
It can. SMS may be split into multiple billable segments depending on character count and encoding.
Yes. Eligible organizations can negotiate terms based on volume, destination mix, products, payment structure and operational requirements.
That depends on the market, customer profile and billing presentation. Applicable taxes and fees should be disclosed in the account, quote or invoice.
The billing architecture can support market-aware pricing and account-level currency configuration. Enabled currencies depend on the approved billing setup.
AI projects are typically scoped according to data volume, integration complexity, model usage, evaluation requirements, workflow design and ongoing support.
Provide the service, destination mix, estimated volume, sender requirements and usage pattern so pricing can be structured around the actual workload.
Get pricing based on the traffic you actually need to run.
Share your channels, destination mix, estimated volume and operational requirements so Zayloft can structure pricing around the real workload rather than a generic headline rate.
For pricing, billing or account enquiries, contact support@zayloft.com.