Pricing
The economics of customer conversations
oHallo aligns the cost of your customer operations with the conversations your customers generate. Routine queries resolve autonomously, so your team focuses on the high-value work that requires human judgement.
Business
For teams scaling care across channels with predictable conversation volumes.
Includes
Enterprise
For organisations with compliance, integration, and scale requirements.
Includes
Frequently asked questions
What counts as a customer conversation? +
A customer conversation is one continuous exchange with a single customer, regardless of how many messages it contains. A customer who sends six messages over two days about the same query counts as one conversation. A customer who returns three weeks later with a separate query counts as a new one.
How is conversation volume estimated and priced? +
During the sales process we work with you to size expected conversation volume across the channels you operate. Pricing is sized to that forecast with bands that absorb normal monthly variation. Volume is reviewed annually.
What happens if our volume changes over time? +
The subscription includes flexibility bands for normal monthly variation. If sustained volume moves materially above or below the agreed band, we adjust the terms together at the next review point. The intent is alignment with your actual operation.
Is there a minimum commitment? +
Yes. The minimum scales with the size of your existing customer-facing team and is agreed during the sales conversation. oHallo is built for organisations already operating a customer-facing function at meaningful scale.
Do you offer multi-year terms? +
Yes. Multi-year subscriptions are available and typical for organisations integrating oHallo deeply into their customer operations. Specific terms are agreed during the sales conversation.
Can we run on our own AI infrastructure? +
The Enterprise tier includes private inference, where LLM execution runs on dedicated infrastructure isolated to your organisation. Conversation data stays within your inference environment. Specific configurations are agreed during onboarding.
How is data isolated between organisations? +
Every database row, storage path, and processing context carries an organisation identifier that scopes access at every layer. Cross-organisation queries are blocked at the application boundary in addition to access controls. The Enterprise tier can add custom data residency requirements.
What are the SLA terms? +
The Enterprise tier includes uptime guarantees, response time commitments for incidents, and credits for breaches. Specific levels are agreed during onboarding based on the criticality of your customer care operation.
How are voice and SMS charges handled? +
Phone numbers, voice minutes, SMS messages, and proactive WhatsApp messages are billed at carrier rates as a separate pass-through line. Email and chat channels are fully included in the subscription.
See it on your own data
Connect your systems, send a real query, and watch oHallo handle it.