Zayloft
Zayloft
Zayloft provides communications, verification, developer and customer-engagement capabilities that can include SMS, supported rich messaging channels, email, voice, authentication workflows, APIs, webhooks and AI/NLP services according to the enabled account and use case.
Zayloft frequently asked questions
Clear answers about how Zayloft services, integrations, pricing, security and account operations work.
Use the categories or search below to find practical answers about communications, developer interfaces, enterprise operations, billing and responsible platform use.
Yes. Organizations can structure workloads across supported messaging, verification, email, voice and other enabled services. Availability, sender requirements and commercial terms can differ by channel and destination.
Service availability and sender rules vary by destination, channel, use case and account configuration. Zayloft does not represent every service or sender type as universally available.
Yes. Applications can combine channel APIs, inbound events, webhooks, verification, preferences and business logic to support broader customer journeys and operational workflows.
Application teams can use versioned REST APIs, signed webhooks and, for suitable SMS workloads, SMPP 3.4. The appropriate integration depends on the product, traffic pattern and account configuration.
REST is usually the simpler choice for application-driven messaging. SMPP can be appropriate for certain enterprise SMS workloads that benefit from persistent sessions, throughput controls and delivery receipts.
No. A synchronous success usually means the request was accepted for processing. Final delivery state should be determined from delivery events or receipts where the selected channel provides them.
Keep them in protected server-side secret storage or environment configuration. Do not expose them in browser JavaScript, public repositories, screenshots, public logs or client applications that cannot protect secrets.
Distributed systems can time out or retry. Idempotency and durable identifiers help applications recover safely, avoid unintended duplicate operations and reconcile asynchronous delivery or inbound events.
SMS pricing can vary by destination, network, sender type, route, message segmentation, local fees and account volume. One universal rate would not accurately represent many markets.
Eligible organizations can discuss pricing based on committed volume, destination mix, enabled products, routing requirements, payment structure and operational needs.
Not necessarily. Taxes, carrier fees, sender-registration charges, number fees and platform charges can vary by market and service. Applicable treatment should be disclosed in the account, quote, pricing schedule or invoice.
The billing architecture can support account-aware currencies and market-specific pricing. The currencies enabled for a customer depend on the approved billing setup and commercial arrangement.
Zayloft is designed around controlled access, scoped credentials, tenant boundaries, secure transport, signed events, auditability and operational safeguards. Security also depends on how customers protect their own users, credentials, endpoints and integrations.
No. Requirements vary by jurisdiction, industry, data type, destination and use case. Zayloft can provide technical and operational controls that support customer compliance programs without replacing the customer’s own legal and regulatory responsibilities.
Zayloft can support consent records, communication preferences, suppression and opt-out handling. Customers remain responsible for ensuring their communications are authorized and appropriate for the intended recipients and destinations.
Yes. Organization, project, environment and role boundaries are intended to separate access, credentials, usage and operational responsibilities.
Send the technical details to support@zayloft.com with “Security report” in the subject line. Avoid publicly disclosing sensitive exploit information before the concern can be reviewed.
Contact support@zayloft.com and use the email address associated with the account where possible. Sensitive account changes may require authenticated verification before they can be completed.
Provide the channels you need, destination mix, estimated volume, sender requirements, expected usage pattern and any enterprise billing needs. That information allows pricing to be structured around the actual workload.
No. Do not send passwords, API keys, access tokens, SMPP passwords, webhook secrets or other credentials through public support channels. Use request IDs, event IDs and redacted logs instead.
No general response-time guarantee is stated on the public website. Priority, escalation and support arrangements can depend on the account and commercial agreement.
No matching questions were found. Try a broader search or contact support.
Still need a specific answer?
Send the relevant service, destination, account context, request or event identifiers and the outcome you are trying to achieve. Do not include credentials.
Public support email: support@zayloft.com.