Payer calls from Claude

Connect Daybook's voice agent to Claude: start a payer call from a chat, read the answer and transcript, and record the outcome on the claim.

Daybook's voice agent calls the payer, works the phone tree, waits on hold and asks the rep your questions. Over MCP, Claude can start that call, read what the payer said, and record the outcome, from the same chat where you asked about the claim. It is the Payer calls workflow, with Claude as the one asking.

In a chat

Claim A-20817-1 with Bayline has been in process for 40 days. Call them, ask for the expected pay date, and record what they say.

Claude checks the claim
get_claim and claim_timeline: the last status answer and any earlier call, so it does not call about something the payer already answered this week.
Claude starts the call
start_call with the claim, call_type: claim_status and your extra question. Claude asks you before it dials unless you allowed the tool always. The call is gated as every call is: the firm's owner has confirmed Daybook as billing agent, a call script fits the claim's step, and the payer's line is linked.
Daybook works the call
Phone tree, hold, rep. Watch it in Switchboard → Live calls in the Daybook app, where anyone allowed to control the call can tell the agent something, take the call over or hang up.
Claude reads the answer
start_call waits for the structured answer: status, reference number, rep name, next step and the call type's details. Claude can read the call again at any time with get_call.
Claude records it
record_work on the work item, with a follow-up date from the rep's answer, or add_claim_note. A completed call with a reference number also moves the claim in Daybook to what the payer said.

Reading calls

Ask	Tool
What did Keystone say about A-20817-1?	`get_call`: the answer claim by claim, the reference number and the transcript turns, with the phone tree, the hold and any operator notes
Which calls this week ended in a denial?	`list_calls`, filtered by what the payer answered
How do you reach claims at Meridian?	`ivr_maps`: the payer's phone tree as the voice agent walks it
Which payers have no line set up?	`list_payers`: each payer's phone lines

Calls Claude starts are calls like any other

They are in Payer calls in the Daybook app with the transcript, they send the call.* webhook events to your endpoints, and they count toward your usage. Your ticketing integration hears about a call Claude started the same way it hears about one your queue started. In a sandbox they are real calls through the same voice agent, with events in mode: test.

What stays in the app or the API

Operation	Where
Tell the agent something mid-call	Live calls, or Tell the agent something
Cancel a call	Live calls, or Cancel a call
Take the line, press keys, listen in	Live calls, with a softphone in the browser
Hand a live rep to a biller	`mode: handoff` on Start a call
Repeat a call until the status moves	`schedule` on Start a call
Payer lines, phone trees, call scripts	Switchboard in the Daybook app