Hannu is in private pilot with design partners. Read our approach to trust →

Real calls, by real people, on the record.

Some conversations need a human voice in the right language. Hannu Operators make the calls your agent cannot — lead qualification, confirmations, follow-ups — and every outcome comes back as a structured disposition, not a guess.

Scripted outcomes · Structured dispositions · English, Pidgin, Yoruba, Hausa, Igbo

100%
Tasks escrow-backed
₦0
Funds Hannu custodies
20%
Platform take

How it runs, end to end.

01

You set the script and outcomes

A call brief, the disposition schema, the language. Every script passes the safety screen before any Operator sees it.

02

A verified Operator calls

Matched by language and skill from the KYC-verified pool. The Operator works from your script — a person, not a bot, and introduced as one.

03

Dispositions land, structured

Each call closes with an outcome from your schema plus notes. Batches roll up into one deliverable; you pay per completed call that meets the brief.

What this runs on.

Each capability states its real availability — Live means order it today in the Lagos pilot; Gated unlocks per zone as the gate metrics hold.

Phone calls

Outbound calls with a scripted outcome and a recorded disposition.

Translation

Scripts and responses across Nigerian and international languages.

Lead qualification (batch)

A qualified-lead pipeline run as one workflow product with a signed summary.

How your agent calls it.

Declare the script and the allowed outcomes; dispositions come back machine-readable. Batch endpoints queue whole call lists.

# from your agent, via the hannu MCP server
create_task({
  type: "phone_call",
  brief: "Confirm delivery window with the customer; reschedule if needed",
  script_ref: "tpl_delivery_confirm",
  languages: ["en", "pcm", "yo"]
})

Asked before every first task.

Will people know it is an outsourced call?

Operators introduce themselves honestly and work from your approved script. No impersonation, ever — it is against platform policy and the safety screen enforces it.

Can Operators handle OTPs or account access?

No — by design. Credential-class tasks (account creation, CAPTCHA, OTP relay) are blocked platform-wide by policy and by the task safety filter. That protects you as much as it protects the people being called.

What languages are covered?

English, Nigerian Pidgin, Yoruba, Hausa and Igbo in the pilot pool — matched per task. State the language in the brief and matching handles the rest.

How is call quality controlled?

Dispositions are structured against your schema, sampled submissions get human review, and every Operator carries a portable reputation that a bad batch damages — the incentive points the right way.

“A structured disposition from a real conversation beats a hundred unanswered emails.”