Skip to content

PyAI Recap · Post-call intelligence

The call ends.
The next step starts.

Keep the useful part of every conversation. Recap turns call context into a clear summary, a disposition, the next action and the fields your team needs.

No bot to invite. No notes to copy by hand.

After the conversationExample output
Illustrative completed recap

The call ended. The work moves on.

Summary

Caller asked to move Friday’s delivery to Monday morning. The agent confirmed the new slot and updated the order.

Disposition
rescheduled
Next step

Send a confirmation for Monday at 10 AM.

Your field · delivery_window

Monday, 10 AM

Explore sample outputs. This does not process a call or send data to a CRM. Recap summarizes call context; Hear handles transcription.

Summary, disposition and next step
Structured fields you define
Webhook and Salesforce delivery

After the last word

A conversation becomes
something your team can use.

The caller should not have to repeat the story. Give the next person the context, the outcome and the action to take.

01

Capture what mattered.

Get a readable summary and a disposition from the call context. Recap works on Omni and Agents calls, or on a Hear transcript associated with a call ID.

02

Make the output fit your team.

Define structured fields for the information your workflow needs. Keep the next step beside the summary so the handoff has a clear purpose.

03

Send it where work continues.

Receive the recap on your webhook when the call ends. Map the fields to Salesforce once, or send the same object to another system through your integration.

One call. A useful handoff.

Good notes belong
where you work.

Recap runs with the call data you provide. There is no meeting participant to invite, and no need to copy a conversation into a second note-taking tool.

  • Summary and disposition on the call record
  • A next step that can move into your workflow
  • Salesforce field mapping or your own webhook
Read the integration guide
From the call to your workflowProduct workflow
Call context

Omni, Agents, or a Hear transcript with a call ID

Recap

Summary → disposition → next step → your fields

Destination

Your webhook, or mapped Salesforce fields

From exploring to building

Make a change.
Take the code.

Filter completed recaps and copy the matching request. The example reads existing records; it does not transcribe audio or start a call.

Find the recaps you need.

Filter existing post-call records and generate the matching read request. Recap must be enabled for your organization.

GET /v1/recap/calls

const response = await fetch("https://api.pyai.com/v1/recap/calls?status=complete&limit=10", {
  method: "GET",
  headers: {
    Authorization: `Bearer ${process.env.PYAI_API_KEY}`,
  },
});
if (!response.ok) throw new Error(await response.text());
console.log(await response.json());

// Use next_cursor as the cursor query parameter to read the next page.
// Read GET /v1/recap/calls/{call_id} for a complete call record.

Code updates here without sending a request. Run the copied example on your server with PYAI_API_KEY.

Copy the code to use these settings, or explore the full product workspace.

Recap does not transcribe audio itself. Use Hear for transcription, then associate the transcript with your call context.

A little more detail

Good questions.
Clear answers.

Recap: $0.02/min. See the current pricing page for applicable usage terms.

See current rates
Explore call review with Trace
What does a recap include?

A summary, a disposition, the next step, and the structured fields you define. Delivered to your webhook when the call ends and available from GET /v1/recap/calls.

Does Recap need Omni?

No. Recap runs on Omni and Agents calls, or on a Hear transcript you attach a call_id to. It does not transcribe audio itself.

Can it write to Salesforce?

Yes. Map Salesforce fields once via /v1/recap/crm-config (scope recap:configure). Other CRMs receive the same object on your webhook.

How is it billed?

Enable it once and it applies to the calls you choose. Check our pricing page for current rates.

Available on ClawHub

Use PyAI Recap in OpenClaw.

Install the skills you need, connect your PyAI account through the official CLI, and ask your assistant to put them to work.

Recap · v1.0.1

Keep the context. Find the next step.

Retrieve an existing recap or summarize a supplied customer/agent transcript with its original speaker roles and timing.

Get Recap on ClawHub

Recap enabled and recap:read access. New transcript processing needs suitable timed utterances; a plain transcript may need preparation.

Create an account for Recap

Build the part your team needs

Keep the conversation.
Move the work forward.