What we ship
Nexora Voice and Nexora Chat are two products that share one platform definition. Nexora Voice handles voice agents on inbound and outbound phone calls — tier-one customer service, appointment reminders, outbound renewals, payment-due notifications, lead qualification. Nexora Chat handles chat agents on web-chat, WhatsApp Business, and helpdesk surfaces. Both products run from the same agent definition, the same knowledge base, the same integrations, and produce the same audit trail. Customers who run both channels do not have to reconcile two different definitions of "what the agent knows".
Under the hood, the platform integrates with the systems most contact centres already run on day one: Salesforce, HubSpot, Twilio, WhatsApp Business, SIP and PSTN telephony, Confluence, PostgreSQL, Zendesk, Intercom, Slack, Zapier, and a full REST API plus webhook surface for everything else. Each integration ships with a dedicated landing page describing the wiring, a pre-built configuration pattern, and an FAQ for buyer questions. The integration story is part of the product, not a separate engagement.
The deployment shape: 14-day pilot, 30-day live
Every Nexora deployment runs the same shape. A 30-minute scoping call kicks off day one. We bring the integration patterns for your stack; you bring the system credentials and the first use case. By day 14 the agent is live on real customer conversations — not a sandbox simulation. Production cut-over follows by day 30. Pricing during pilot is fixed-scope; production pricing is contracted per deployment based on volume and service level.
The 14-day timeline is intentional. Long-cycle enterprise sales engagements have not been the right shape for the buyer's problem. Operators want evidence before commitment. The shortest reliable path from "we should look at voice AI" to "we have a working agent on real calls" is two weeks if the vendor brings the integration patterns and the buyer brings the use case. That is what we are committing to.
Five markets, one platform
We ship to New Zealand, Australia, the United States, the United Kingdom, and the European Union. Voice profiles are trained from a 50-call reference set per deployment, so the agent reads correctly to the actual caller distribution each customer serves — NZ English in Auckland, Australian English in Sydney, UK English in London, US English in New York, Irish English in Dublin, plus other language profiles as needed for multilingual contact centres. Multi-region data residency is configurable per deployment so customers can pin primary storage to their local region.
The five-market list reflects where we have committed engineering and support presence. Other markets may follow once we are confident we can serve them with the same deployment discipline. For now, the five markets are the ones where customers should expect the full Nexora deployment shape: 14-day pilot, 30-day live, local-time-zone support, voice profile tuned to the local caller base.
The engineering controls we ship — and the claims we do not make
We ship TLS 1.3 in transit, AES-256 at rest, zero-retention LLM routing (prompts and outputs are not retained by the model provider for training), multi-region residency configurable, and a per-conversation audit trail. A data-processing agreement and a security questionnaire are available on request. We document the engineering controls plainly so procurement teams can review them in advance of any contract.
What we do not do: we do not claim formal third-party attestations we have not earned. Buyers whose procurement teams require specific attestations should evaluate Nexora against those requirements before commitment. We are clear about what the platform does and what it does not. We expect that clarity to be a feature rather than a bug for the buyers we want to work with.
What we are building next
In the months ahead we will expand the integration footprint, the language coverage on voice profiles, and the per-region deployment options. We will publish more long-form material on this blog — technical explainers, deployment patterns, and field notes from real conversations. Customer stories will follow once the first deployments are mature enough to share publicly with their teams' consent.
If your team is evaluating voice or chat AI for an upcoming workflow — inbound triage, outbound campaign, appointment booking, lead qualification — we are happy to scope a pilot. The 30-minute scoping call is the right place to start. Contact us at sales@nexoralabs.co.nz or through the contact form on this site. We look forward to the conversation.
A note on positioning
We have made some deliberate choices in how Nexora is positioned that are worth calling out. The platform is sales-led rather than self-serve. The pricing is contracted rather than published per-minute. The certification posture is engineering-controls-with-DPA rather than badge-led. Each of those choices reflects what the buyers we want to work with — operators of real contact centres in real industries — have told us they need from a vendor. We have built the product they described rather than the product the SEO algorithm would prefer. The trade-off is that buyers wanting a self-serve developer platform should look elsewhere. The trade-off in our favour is that operators wanting a managed deployment with a named pilot-success owner have a vendor built for them.
Thank you for reading. The first wave of customers shipping on Nexora are doing the hardest work — taking a brand-new platform into production conversations with their real customers. We are grateful for the trust and we take the responsibility seriously. The platform will get better month by month because their teams will tell us where it falls short and what to fix. That feedback loop is the most important asset we have today.