Skip to main content

​
Phone Call Records

Every phone conversation your voice agent has is kept: the calls it places for you, and — once the agent has its own phone number — the calls people place to it. Each record holds who was on the line, when the call happened, how long it lasted, a short summary, and the full transcript.
Inbound calls used to be answered but not kept. If someone called your agent’s number, the conversation happened and then vanished. It is now recorded the same way an outbound call is, so a call that comes in at 9pm is still there in the morning.

​
What a record contains

​
Ask in chat

The simplest way in. Ask for the calls themselves, or for one call’s transcript:
“Has anyone called my Sofia number this week?”
“What did the caller say on that last call?”
Erdo lists the calls — newest first, with direction, both numbers, duration and a summary — and reads back the full transcript of whichever one you pick. You can narrow to one agent or to inbound calls only just by saying so.

​
Your agent asks callers who they are

On an inbound call the person on the line is a stranger — Erdo has no other way to reach them. So the agent asks, naturally and at most twice, for their name and the best email or phone to follow up on, spells an email back to confirm it, and accepts a “no thanks” gracefully. What they share lands in the transcript and the summary. On an outbound call it does the opposite: you already told Erdo who to call, so the agent never asks the recipient for their own contact details.
Erdo does not automatically create a lead from a call. Recording the conversation is not the same as deciding the caller is a lead — you decide what to do with the record.

​
Read them programmatically

The same list-and-read surface is available over the REST API, the CLI, and to MCP clients, so a scheduled automation or an external dashboard can pull calls without going through chat. All of them are scoped to your organization by your credentials.
  • List — GET /v1/voice/calls (or a POST with a JSON body) returns each call’s id, direction, both numbers, status, timing, duration, and summary, newest first and paginated. Narrow with agent (a voice agent’s slug) and direction (inbound or outbound). When a response includes next_cursor, pass it back as cursor to read the next stable page — this avoids skips when a call comes in during a multi-page scan. MCP tool: erdo_voice_call_list.
  • Read one — GET /v1/voice/calls/{call_id}, using a call_id from the list, returns the rendered transcript, the raw transcript, and a structured turns array with per-turn model latency and token usage. MCP tool: erdo_voice_call_get.
From the CLI:
Website chat widget conversations are a separate surface — they belong to a widget rather than to a phone number. See Website Concierge for those.

​
Good to know

  • Summaries fill in on their own. A call is summarized shortly after it ends, so a record read moments after hang-up may show a transcript before its summary.
  • Records follow the agent, not the person. An inbound caller is not an Erdo user, so the record belongs to your organization and the agent that answered.
  • Retention matches your other conversation data. Transcripts are visible to your workspace members through Erdo — treat them like any other customer communication.