IbhanAi Labs · Unified Messaging

The AI Unified Messaging platform that speaks your organisation's language — and follows its rules.

Your staff know what to say — they just shouldn't have to paste sensitive information into a public AI. Kukku lets them dictate, search your own knowledge, and reach people by message or voice — every word following your policy, on your servers or in the cloud.

Private chatbot Policy-safe messaging AI voice, both ways On-premise or cloud

Four things Kukku does — in plain language

From a rough note to a policy-safe message — in seconds

It meets your people where they already work, uses only your organisation's approved knowledge, speaks and listens on voice calls, and gives everyone a private chatbot that never leaks a word.

It listens to how your people already work — dictation, writing, even paper

However your people capture information — talking, typing shorthand, or writing on paper — Kukku accepts it and turns it into a clear, professional record.

Examples

  • A doctor dictates the ward round on their phone. Kukku writes the family SMS and the EMR entry, in the right tone for each.
  • A nurse snaps a photo of the handwritten admission interview. Kukku reads it, structures it into chief complaint, medications, allergies, and family concerns, and adds it to the patient record.
  • A claims analyst jots two lines of internal shorthand. Kukku produces the policyholder update — with the sensitive numbers automatically kept out.
  • A care worker types a quick note at the end of a shift. Kukku prepares the family update and the shift-handover message in one go.

Guardrails first. Everything is checked against your policy before it goes anywhere. If it can't be said — bad news over SMS, a settlement figure in text, an identifier where it doesn't belong — Kukku flags it and asks for a human decision.

It searches your organisation's own knowledge — not the whole internet

Your protocols, playbooks, leaflets, and approved glossary already exist as documents on someone's drive. Kukku uses only those — so every message stays inside what your organisation actually approves.

Examples

  • A junior clinician writes to a family about a post-op recovery. Kukku pulls the approved paracetamol and NSAID guidance and phrases it the way your hospital says it should be phrased.
  • A claims agent explains the next step. Kukku uses your company's own claims process document — not something a generic AI made up.
  • A vet dictates aftercare for a pet owner. Kukku uses your clinic's own dental and pain-relief protocols.
  • A new team member sends their first family update. Kukku's suggestions match what your senior staff would write — because it's reading from the same house guide.

No IT project. You edit the glossary and upload new policy documents through a simple screen. No AI training. It's live for the next message.

It speaks and listens — voice calls, both ways

Not everyone reads SMS. Kukku uses your voice-agent platform to speak the message — and to answer when people call in.

Outbound — Kukku calls them

  • An elderly daughter is called by an AI voice that gently updates her, in Hindi, about her mother's day on the ward.
  • A pet owner receives a voice call in the evening with the day's recovery update — no app to install.
  • A policyholder is called back in their own language with a claim status they can understand.

Inbound — they call Kukku

  • A family member calls the hospital's status line at 2 a.m. and hears the latest approved update the doctor saved that afternoon — instead of interrupting the night shift.
  • A policyholder calls in and the voice agent answers with the most recent claim status — no menu tree, no wait.
  • A relative asks a follow-up question — the voice agent knows what was sent by SMS earlier that day and speaks consistently.

Same policy, every channel. If it can't be sent as text, it isn't spoken either. Nothing goes out and nothing is spoken without a human having approved it once.

It gives your staff a private chatbot — your knowledge, your servers, no data ever leaves

Your people already use public chatbots to draft and look things up — pasting patient details, claim numbers, and internal policies into someone else's cloud. Kukku gives them a private chatbot instead — on your infrastructure, reading only your approved knowledge, never sending a word outside your walls.

Examples

  • A nurse asks: "What's our policy for paracetamol dosing in over-65s?" — and gets your hospital's own protocol, cited, not a generic answer scraped from the internet.
  • A claims analyst pastes a rough internal note and asks: "How should I phrase this for the policyholder?" — the chatbot drafts it inside Kukku, ready for the same approval and audit flow.
  • A junior doctor asks: "Summarise everything we've told this patient's family in the last 48 hours" — the chatbot pulls from Kukku's own message record, not any external system.
  • A new team member asks: "What tone do we use with bereaved families?" — answered from your organisation's own communication playbook.
  • A care manager asks: "Which residents haven't had a family update this week?" — the chatbot queries Kukku directly, no data leaves the site.

The same AI that powers your outbound messages powers the chatbot — so tone, terminology, and compliance boundaries are identical whether staff are drafting a message, summarising a thread, or just asking a question. Staff stop pasting sensitive information into public chatbots, and every question and answer can be audited.

Compliance, built in

Every message follows your company policy — automatically

You write your communication rules once — Kukku enforces them on every message, every call, every summary, and every chatbot answer, and shows the person approving exactly which rule was applied. Nothing gets out unless the guardrails pass and a human clicks approve.

You also see a complete record of everything sent, everything spoken, every question asked, and every knowledge document the AI used — for audit, review, or dispute.

Deployment

Runs where you need it to — public, private, or both

Kukku is built for regulated environments where your data cannot leave the building. And the AI models can be tuned to your organisation — your terminology, your tone, your typical scenarios — so suggestions read like they came from your senior staff.

Private / on-premise

The AI models, voice agents, private chatbot, knowledge base, and every message live entirely on your servers. Nothing leaves.

Public / managed cloud

For less-sensitive work, use frontier models via API for the highest language quality.

Mix and match, per use case

Clinical conversations on-premise; internal team notifications in the cloud — all under the same compliance policy.

A private chatbot for staff

The same model that drafts your outbound messages answers your team's day-to-day questions, entirely inside your infrastructure.

Who Kukku is for

Any organisation where a badly-worded message costs trust, time, or money

…and any organisation whose staff are already using public chatbots to get their work done, but shouldn't be. If your compliance team has ever had to send a "please don't paste patient information into ChatGPT" email — Kukku is the fix. Same convenience for your staff, none of the risk.

🏥 Hospitals & clinics 🏡 Aged care & home care 🛡️ Insurance & claims teams 🐾 Veterinary practices 🏦 Banks & financial services 🏛️ Government & public services

Ready to see it with your own examples?

Bring us three real conversations

One you find hard to write, one you get too many phone calls about, and one a staff member would normally have asked a public chatbot about. We'll show you all three, handled through Kukku, in a 20-minute walkthrough.