Zayloft
Zayloft
Sales
Discuss messaging, verification, voice, email, AI services, expected volume and destination requirements.
Contact salesContact Zayloft
Talk to the right team without having to guess where your question belongs.
Whether you are evaluating Zayloft, integrating APIs, managing an account, reviewing enterprise requirements or reporting a security concern, start here and route the enquiry to the appropriate team.
Choose the path that matches what you need.
Zayloft keeps public contact routes simple so commercial, technical and operational enquiries can be handled with the right context.
Enterprise
Discuss organizational structure, high-volume connectivity, invoicing, security controls and deployment requirements.
Contact enterpriseDeveloper support
Ask about REST APIs, SMPP 3.4, webhooks, authentication, events and integration behavior.
Developer enquiryBilling & account
Get help with account access, funding, invoices, usage questions and approved commercial arrangements.
Billing enquirySecurity
Report a suspected security issue or ask about platform security controls and responsible disclosure.
Security enquiryGeneral support
Use general support when the enquiry does not clearly fit one of the specialist paths.
Contact supportSend a structured enquiry.
Provide enough context for the team to understand the request without including passwords, API keys, private credentials or unnecessary sensitive data.
Help the team respond with useful context.
The fastest path to a useful response is to describe the actual service, destination, workload and issue rather than sending only a general request for information.
Commercial enquiries
Include channels, destination mix, estimated monthly volume and any sender or billing requirements.
Technical enquiries
Include the API or protocol involved, request or event identifiers and the observed behavior. Remove credentials before sending logs.
Account enquiries
Use the email address associated with the account where possible and describe the account action you need help with.
Security reports
Include reproduction details and affected service information without accessing unrelated data or disrupting production.
Share only what is needed to resolve the enquiry.
Contact messages may contain business and technical information. Avoid sending credentials or unrelated personal data, and use authenticated account support for sensitive account-specific matters.
Never send secrets
Do not send API keys, passwords, access tokens or private cryptographic material.
Remove sensitive payloads
Redact customer message content and personal data that is not necessary to explain the issue.
Use identifiers
Request IDs, event IDs and account references are usually safer and more useful than complete raw payloads.
Use the right channel
Sensitive account changes should be completed through authenticated account processes rather than ordinary public email.
Frequently asked questions
Use support@zayloft.com for public support, sales, technical, billing and security enquiries. Include a clear subject and enough context for routing.
No. Never submit API keys, passwords, access tokens, SMPP passwords, webhook secrets or other credentials through the public contact form.
Include the channels you need, destination mix, estimated volume, sender requirements and expected usage pattern so pricing can be based on the actual workload.
Include the interface involved, relevant request or event identifiers, expected behavior and observed behavior. Redact credentials and unnecessary personal data.
Choose Security in the form or email support@zayloft.com with “Security report” in the subject. Include enough technical detail for review and avoid public disclosure before the concern can be investigated.
Eligible organizations can discuss invoicing, credit terms, committed volume and other enterprise commercial arrangements with the enterprise team.
Use public contact to start the conversation, but sensitive account changes may require authenticated verification before they can be completed.
No response-time guarantee is stated on this public page. Priority and support arrangements can depend on the account and commercial agreement.
Start with the context. Zayloft will route the conversation from there.
For sales, enterprise, API, billing, account or security enquiries, provide the relevant details and avoid including credentials.
Public support email: support@zayloft.com.