Accelerate your roadmap.
Add voice and messaging without building telephony, AI operations and customer infrastructure yourself.
Build conversation AI into your product.
Embed our conversation engine in your product. Add partner-exclusive Trillet industry solutions where agreed. Your brand stays in front.
- Own the product experience
- Your brand
- Use the channels you need
- One engine
- Agree deployment and integration
- Your scope
Why OEM
Ship the capability.
Keep the product yours.
Connect to your systems.
Use APIs and webhooks to connect conversations to your product data and workflows.
Define the model together.
Agree branding, deployment, support and commercial terms with our product and engineering teams.
What you’re embedding
One engine behind your product.
Choose the channels, integrations and deployment your product needs. No fixed bundle.
Developer documentation
Channels on one engine.
Voice, SMS, chat and email on one platform. Use the channels your product needs.
Your brand in front.
Your domain and product stay primary. Any Trillet attribution is agreed with you.
Separate customer workspaces.
Give each customer a separate workspace without building the account structure yourself.
APIs & webhooks.
Read from and write to your product during a conversation, with platform APIs, in-call APIs and webhooks.
Carrier-level telephony.
Where voice is in scope, keep existing numbers with carrier-level forwarding.
Deployment that fits.
Managed cloud, private cloud or on-premises, scoped to your environment and requirements.
Security & deployment
Enterprise trust.
Your product in front.
A clear foundation for your product, security and procurement teams to evaluate.
Your organisation remains responsible for its own compliance obligations and configuration.
Independent assurance.
SOC 2 Type II attested and ISO 27001 certified.
Controls for regulated use cases.
Audit logs and role-based access. Controls and deployment options can support HIPAA, GDPR, ACMA and TCPA requirements, subject to use case and configuration.
Data where you need it.
Australian data residency available, with in-country LLM hosting on request.
Deployment agreed with you.
Private-cloud and on-premises options are available where agreed.
Starting the conversation
Define the product.
Then shape the partnership.
Your use case.
The product, users and launch goal. OEM suits a repeatable use case with a clear route to market.
Technical fit.
Channels, integrations, expected volume, security and deployment.
The partnership.
Product scope, responsibilities, commercial terms and launch planning.
Common questions
Frequently asked
questions.
Are Trillet industry solutions available to the public?
No. Official Trillet Health, Legal, Finance and Government solutions are exclusive to approved partners and are not available for direct public purchase. They are not included in self-serve white-label. Each partnership agreement specifies the solutions and whether the partner may resell, refer or embed them. Partner status does not automatically grant access to the full portfolio.
What can we embed?
Trillet’s conversation engine — AI agents across voice, SMS, chat and email, with platform API access plus in-call APIs and webhooks. Which channels and depth of integration you use is scoped to your product.
Can Trillet stay invisible to our end customers?
Trillet can remain invisible where agreed in the OEM scope. Your domain, interface and product name can stay primary. Your brand and customer relationship remain in front, while implementation, support, escalation and service responsibilities are defined in the agreement.
How is OEM different from agency white-label?
OEM embeds agreed Trillet capabilities into a product or managed service you own through a scoped partnership. White-label is a self-serve platform for agencies building and operating their own client solutions under the agency brand.
Does OEM include Trillet’s proprietary industry solutions?
Only when named in your agreement. The agreement lists any Trillet packages, markets and territories you can use. Health, Government, Finance and Legal require approval.
What deployment options are available?
Managed cloud, private cloud and on-premises deployment are available depending on environment and regulation. Australian data residency is available, with in-country LLM hosting on request. Deployment is scoped with the partnership.
How do commercial terms work?
OEM has no published self-serve plan. Terms are structured around channels, expected usage and volume, tenancy, deployment, integration depth, support model and any approved packaged-solution rights.
What does our product get on compliance?
Trillet is SOC 2 Type II attested and ISO 27001 certified. Available controls and deployment options can support requirements associated with HIPAA, GDPR, ACMA and TCPA. Your organisation remains responsible for its own compliance obligations and configuration; applicability is confirmed during scoping.
Your product. Our conversation engine.
Bring your use case, integrations and expected volume. We’ll shape the technical and commercial model together.
Building client solutions under your own brand? Explore self-serve white-label.