01 / Kai

Kai runs Kupe. Or any harness you already love.

Kai is the operator inside the hub. You talk to Kai. Customers talk to the agents you deploy.

Ask Kai to create a collections agent

What Kai is

The in-product operator. Not the voice on the line.

Kai lives in the hub the same way Cursor or Claude lives in your editor. Create agents, launch campaigns, read analytics, ask what broke on last night’s shift. Callers never hear Kai unless you put Kai on a number.

01 / Operator

You talk to Kai.

One thread for the team. “Draft a clinic night-line.” “Which EMI script recovered?” “Pause the numbers that failed KYC.” Kai runs Kupe — or harnesses Claude, Cursor, or Codex on the same knowledge graph.

  • Create and edit voice agents
  • Launch and pause campaigns
  • Read the night shift without a dashboard tour
Kai · operatorhub thread

You

Create a collections agent for EMI reminders.

Kai

Drafted Priya. Hindi/English, warm, takes a promise, transfers messy accounts.

Who speaks

Customers talk to Priya. You talk to Kai.

Deploy a collections agent, a clinic bot on WhatsApp, a night line that books Thursday. Those voices are yours. Kai is how you run them — the operator, not the caller-facing persona.

Callers hear

Priya, Meera, the clinic bot

On the phone and on WhatsApp. One memory. Your scripts.

You talk to

Kai

Inside the hub. Create, launch, debug, pause.

GPT
Claude
Cursor
Codex
Antigravity
OpenCode

Harness

One operator. The tools you already live in.

Teach something in Cursor or Claude and it can land in the same graph the voice agent retrieves from. Kai does not lock you into a playground — it runs Kupe, or rides the harness you already pay for.

GPTGPTClaudeClaudeCursorCursorCodexCodexAntigravityAntigravityOpenCodeOpenCode

01 / Create the agent

Create the agent

Describe the job. Kai drafts the voice, the greeting, the tools, and the knowledge — then you hear it on a real number.

02 / Launch the campaign

Launch the campaign

CSV of leads, a night batch, a retry after KYC. Kai wires the list to the agent and watches the first minutes land.

03 / Read the shift

Read the shift

Ask which script recovered, which number failed, which campaign should pause. Analytics as a conversation, not a maze.

The night shift

Create agents. Launch campaigns. Read what broke.

Kai is how a collections lead, a clinic ops manager, or a founder runs voice without a six-week IVR project. You do not learn a dashboard. You ask. The same knowledge graph the caller-facing agent retrieves from is the one Kai reads when you ask which script recovered at 9pm.

A campaign is a list, an agent, and a window. Kai wires them. When KYC fails on three numbers, you do not export a CSV — you ask why, and Kai queues the retry. When the night line is quiet, you ask what booked. Analytics as a conversation, because the people who run the line are not analysts.

Agents

Priya is the voice. Kai is the operator.

Draft a collections agent, a clinic bot, a night line. Voice, greeting, tools, knowledge — Kai puts them on a number. Callers never hear Kai unless you put Kai on that number.

Campaigns

Launch tonight. Pause what failed.

EMI reminders, appointment confirms, lead lists. Kai watches the first minutes land. Pause the batch that failed KYC. Retry after 10am. The night shift is a thread, not a war room.

Open Kai

Ask Kai what to build. Ship the agent tonight.

Same path you try in the hub is the path that answers a real number. Kai is already there.

Open the hub