Question 1

What is OZOO.ai and how is it different from a voice bot?

Accepted Answer

OZOO.ai is an AI conversation platform purpose-built for BFSI lenders. Unlike single-purpose voice bots, OZOO.ai unifies voice agents, conversation (chat) agents and post-call analytics in one platform — every interaction feeds the same intelligence layer.

Question 2

Which industries does OZOO.ai serve?

Accepted Answer

Banks, NBFCs and lenders — across collections, tele-sales, onboarding, customer service and renewals. The product is generalisable, but the workflows, vocabulary and guardrails are BFSI-first.

Question 3

Is OZOO.ai a production product?

Accepted Answer

Yes. The Post-Call Analytics product is in production at NBFC scale (1,500+ calls/day), with quantified outcomes: ₹28 Cr estimated annual ROI, 18 RBI/NHB compliance flags caught that sampling had missed and 300 long-pending cases actioned in the first pass.

Question 4

How is OZOO.ai secured?

Accepted Answer

PCI Compliant, HIPAA-eligible on AWS, with PII redaction by default, encryption at rest and in transit, configurable data residency and full audit trails. ISO 27001, SOC 2 and DPDP attestations are in progress.

Question 5

Who builds OZOO.ai?

Accepted Answer

OZOO.ai is built by Habilelabs — founded 2016, 200+ global clients, 95% retention, 250+ cloud and AI experts, AWS Service Delivery Partner.

Question 6

How many languages are supported?

Accepted Answer

12+ Indian languages including Hindi, Hinglish, English, Tamil, Telugu, Marathi, Gujarati, Bengali, Kannada and Punjabi — selectable per campaign or detected per caller.

Question 7

What is the typical latency?

Accepted Answer

Sub-second turn-taking with natural interruption handling — designed to feel like your best telecaller, not a slow IVR.

Question 8

Can the bot transfer to a human?

Accepted Answer

Yes — live handoff to a human or to a different AI agent (voice or chat) with the full conversation context preserved.

Question 9

Is consent captured?

Accepted Answer

Recording disclosure and explicit consent prompts are configurable per campaign, with timestamped logs maintained for audit.

Question 10

Which telephony stacks does OZOO.ai work with?

Accepted Answer

OZOO.ai is telephony-agnostic — works with SIP trunks, cloud PBX and contact-centre platforms. Pacing, retries and DND respect are controlled from OZOO.ai.

Question 11

Which channels are supported?

Accepted Answer

WhatsApp Business, web chat, in-app SDK and SMS — all from a single API and a single conversation history.

Question 12

How do you prevent hallucinated responses?

Accepted Answer

Responses are grounded on your knowledge base — product docs, FAQs and policy PDFs ingested into a retrieval layer. The model is constrained to answer from that corpus or escalate.

Question 13

Can chat hand off to voice?

Accepted Answer

Yes — handoff to voice (OZOO.ai Voice AI) and to a human agent, both with the full chat transcript and detected intent passed along.

Question 14

Is the chat data PII-safe?

Accepted Answer

PII is redacted before persistence; chat logs are encrypted at rest; consent and timestamps are captured for every interaction.

Question 15

Does OZOO.ai handle Hindi and Hinglish?

Accepted Answer

Yes — Hindi, Hinglish and English ASR are live in production with speaker separation (agent vs customer). Code-switched conversations are handled natively, not via translation.

Question 16

How does it integrate with my existing call recordings?

Accepted Answer

Recordings are ingested from Amazon S3 or via SFTP. The pipeline (Lambda → Transcribe → Comprehend → Bedrock → DynamoDB → Athena) runs serverlessly on AWS, with QuickSight dashboards on top.

Question 17

Can it run on-prem or in my VPC?

Accepted Answer

The reference architecture runs on AWS in your account or ours. VPC-isolated and on-prem-friendly variants are available for regulated deployments — talk to sales for specifics.

Question 18

What kind of compliance flags does it catch?

Accepted Answer

RBI/NHB-aligned rules cover tone, threat language, missing disclosures, recording-consent gaps and product mis-sell signals. Rules are configurable per portfolio.

Question 19

How quickly does it deploy?

Accepted Answer

Phase 1 — sentiment, buy signals and call quality — typically delivers the fastest ROI in 4–6 weeks. Phase 2 (collections intelligence + CRM push) and Phase 3 (agent coaching + business lens) build on the same pipeline.

Question 20

Where is data stored?

Accepted Answer

India region by default for Indian customers; US and EU regions configurable for global deployments. Recordings, transcripts and analytics each have per-tenant retention windows.

Question 21

How is PII handled?

Accepted Answer

Cards, Aadhaar, PAN, mobile numbers and account IDs are auto-masked before persistence and before they reach analytics. Customers can configure additional redaction rules.

Question 22

Is OZOO.ai DPDP-compliant?

Accepted Answer

OZOO.ai is DPDP-ready by design — consent capture, data minimisation and breach reporting align with the Act. Formal DPDP attestation is in progress.

Question 23

Do you offer a DPA?

Accepted Answer

Yes — a Data Processing Agreement is available on request and signed before production data is processed.

Common questions, answered.

The platform

Voice AI Agents

Conversation AI Agents

Post-Call Analytics

Security & compliance

See OZOO.ai on your own calls.