This is taking longer than expected.

Try againBrowse the library
AI Blocks

AI Blocks › Turn speech into text and back

Dialpad and Leexi call summarizer

Give a call ID or ask for recent calls through connected Dialpad or Leexi tools. It retrieves available call records and transcripts, then groups the main discussion, commitments and follow-up work. Get a short summary and actions with owners and dates where stated. Composio access is required; gaps and possible warning signs are not invented facts.

Choose a call. Get main points, decisions, promises and next steps from the available transcript, with missing owners or dates marked.

Free · No account · MIT licence · Made by Composio · Tested · Updated 28 Oct 2026

What you get

What goes in

  • A call ID, or "recent" for your latest calls
  • Or a pasted call transcript
  • The date, length and names of the people (optional)

Before you start

  • Composio command line with Dialpad or Leexi linked, for live lookups
  • Or a transcript you can paste, with no tools

What comes out

  • TL;DR: A two-sentence summary of the call.
  • Key Discussion Points: Each topic and what was decided about it.
  • Commitments Made: A table of who promised what and by when.
  • Action Items: Tasks with an owner and a due date, as a checklist.
  • Red Flags: Signs of churn or the need to escalate, with the words behind them.
  • Recent Calls Overview: When you ask for several calls, one table row for each, with mood and outcome.
See the full layout

Every run hands it back in this order. Your details fill each gap.

## Call Summary
Date, duration, participants, type of call
### TL;DR
### Key Discussion Points
### Customer Sentiment
### Commitments Made
Table of <who>, <committed to>, <deadline>
### Action Items
### Follow-Up Needed
### Red Flags
### Recent Calls Overview (several calls only)
Table of <date>, <contact>, <duration>, <type>, <sentiment>, <key outcome>

Is it for you?

Use it when

  • You manage a support team and want the promises from yesterday's calls in one list.
  • A rep finished a long customer call and needs the next steps written down.
  • You want a quick scan of your last ten calls to spot unhappy customers.

Skip it when

  • You want an email to the customer and CRM updates, not a summary: use the Call follow-up drafter.
  • You have an audio file, not a call record: use the Audio meeting notes writer to get the text first.
  • The call was not recorded, or the person did not agree to it: do not use it. Write your own notes.

Fill it in

Add what this task works from, then copy the request.

  • A call ID, or the word "recent" for your last 5 to 10 calls
  • Composio command line linked to your Dialpad or Leexi account (optional)
  • Or a pasted transcript, with date and names if you have them (optional)
  • Transcript (optional)
  • Tool connection (optional)

Run it

Download the complete instructions and supporting files. Add them to Claude, ChatGPT or Gemini once, then ask for it by name in any chat. Pasting the instructions into a chat works too.

Download all files

Before and after this skill

Choose the steps you need. Bring your own material when you have it.

Before

Bring the material listed under Fill it in.

This skill

Dialpad and Leexi call summarizer

Open builder

After

Details

From Composio. See the original on GitHub; shared under its licence, with a plain name for this library.

What it does

A call summary from Dialpad or Leexi saves you from replaying the recording. Support and sales calls hide small promises, such as "we will send that Friday", that are easy to lose. The skill finds the call, reads its transcript and writes a fixed brief. It has the date and length, a two-sentence summary, the topics and what was decided, the customer's mood, a table of who committed to what, action items with owners and anything that looks like a churn or escalation risk. It uses only what was said. When a date, name or deadline is missing from the transcript, it writes "not stated". Live lookups need the Composio command line and your own Dialpad or Leexi account. Without them, you can paste a transcript.

What goes in and out

You give it

  • A call ID, or the word "recent" for your last 5 to 10 calls
  • Composio command line linked to your Dialpad or Leexi account (optional)
  • Or a pasted transcript, with date and names if you have them (optional)
  • Transcript (optional)
  • Tool connection (optional)

You get

  • A two-sentence summary for each call
  • Key discussion points and what was decided
  • A table of commitments with who and by when
  • Action items with owners, and what to follow up
  • Customer mood and red flags, with the words they are based on

Use it when

  • You manage a support team and want the promises from yesterday's calls in one list.
  • A rep finished a long customer call and needs the next steps written down.
  • You want a quick scan of your last ten calls to spot unhappy customers.
  • A customer says "you promised us" and you need to see what was said.

More for Turn speech into text and back

Every turn speech into text and back skill

How the task works

  • Find the tools. It searches Composio for the right call tool for Dialpad or Leexi, and asks you to link the account if it is not linked.
  • Fetch the call. It gets the call you named, or the latest 5 to 10 calls, with their transcripts.
  • Pull out commitments. It separates topics, decisions, promises, owners and deadlines, using only what was said.
  • Write the call brief. It writes a fixed brief for each call, and an overview table when you asked for several.

Full instructions

  • Pick your route. For live lookups, use an AI that can run commands, such as Claude Code, with the Composio command line installed and your Dialpad or Leexi account linked. Check Composio's own plans first.
  • No Composio? Open Claude, ChatGPT or Gemini, paste in the skill text, then paste the call transcript.
  • Give a call ID, or say "recent". Add the date, length and names if you have them.
  • Read the commitments table first. Check two promises against the transcript. Each must be something someone really said.
  • Look at any "not stated" fields. Fill them from your own records before you share the brief.
  • Treat mood and red flags as a prompt to listen to that part of the call. Do not act on them alone.

Words used in this task

  • Transcript: A written copy of what was said on the call.
  • Composio: A service that connects your AI to tools like Dialpad and Leexi.
  • Red flag: A sign the customer may leave or need a manager.

Full instruction file

Call Summary

You are a call analysis specialist. Pull call recordings/transcripts and generate structured summaries with action items.

The user's input is: $ARGUMENTS

Before you start

Use the material below to do this job. If facts or tool access are missing, explain what you can finish and what must wait.

Makes it better (optional):

  • A transcript (yours): the words from a recording, written out, with who said what.
  • A tool connection (yours): an AI connected to an outside tool or service, such as an MCP server.

How to start:

  1. Look first. Use what they've already attached, pasted or put in their about-me note. In a coding assistant with file access, look in the project too for these by name.
  2. Check what's missing. Look for a transcript, a tool connection. They can attach files, paste the details, or share a file path your assistant can read. Ask only for missing facts that change the result. If they ask you to start with what they have, complete the parts you can and mark the gaps.
  3. Do the job. Follow the skill below with the facts and tools you have. Mark each gap with MISSING: where it belongs and never invent a fact to fill it.

Tools that do this best:

  • Dialpad or Leexi: Live lookups read call records and transcripts from these services.
  • Composio command line: It is the connector this skill uses to reach Dialpad or Leexi. It has its own account and plans.
  • Claude Code: It can run the Composio commands for you.
What you need
  • A call: a call ID, or the word "recent" for the latest 5 to 10 calls.
  • Live route: the Composio command line installed and signed in, with your Dialpad or Leexi account linked (composio link dialpad or composio link leexi). Composio, Dialpad and Leexi each have their own accounts and plans. Check their current terms before you start. The skill itself does not say what any of them cost.
  • No-tools route: if the user cannot use Composio, ask them to paste the call transcript, and the date, length and names if they have them. Then skip Steps 1 and 2 and go to Step 3. Say that you worked from pasted text.
  • A call transcript holds customer data. Use it only for this summary. Do not send or post it anywhere unless the user asks.

If no call ID is given and the user did not say "recent", ask once which call they mean.

Rules for Step 3
  • Use only what is in the transcript. If the date, length, names or deadline are not there, write "not stated". Do not guess.
  • List a commitment only if someone said it. Use the speaker's own words for the deadline.
  • Sentiment and red flags are your reading of the words. Say which words you based them on.
  • If the transcript is empty or cut off, say so and stop. Do not write a summary of a call you cannot read.
  • In Step 2, replace <CALL_TOOL_SLUG> with the tool name that Step 1's search returned for the service in use. If the search returns nothing, tell the user and stop.
Workflow
Step 1: Discover tools

Run composio search "get call recordings and transcripts from Dialpad" "get call analytics and transcripts from Leexi" in Bash.

Step 2: Fetch call data
  • If a call ID is given: run composio execute <CALL_TOOL_SLUG> -d '{"call_id":"<ID>"}' in Bash
  • If "recent" or no argument: run composio execute <CALL_TOOL_SLUG> -d '{...limit 5-10...}' in Bash

If the CLI reports a toolkit isn't connected, ask the user to run composio link dialpad (or composio link leexi) and retry.

Step 3: Analyze and summarize

For each call, produce:

## Call Summary

**Date:** [date/time] | **Duration:** [Xm Xs]
**Participants:** [names/numbers]
**Type:** [Support / Sales / Onboarding / Check-in]

### TL;DR
[2 sentence summary of the call]

### Key Discussion Points
1. [Topic] — [what was discussed and decided]
2. [Topic] — [what was discussed and decided]

### Customer Sentiment
- Overall: [Positive / Neutral / Negative]
- Key moments: [notable emotional shifts]

### Commitments Made
| Who | Committed To | Deadline |
|-----|-------------|----------|

### Action Items
- [ ] [Action] — Owner: [who] — Due: [when]
- [ ] [Action] — Owner: [who] — Due: [when]

### Follow-Up Needed
- [What should happen next and by when]

### Red Flags
- [Any concerning signals — churn risk, escalation needed, etc.]

If multiple calls, also provide a summary table:

### Recent Calls Overview
| Date | Contact | Duration | Type | Sentiment | Key Outcome |
|------|---------|----------|------|-----------|-------------|
After this

When you've handed it back, suggest what they could do next in one short question. It's a suggestion: if they're done, that's fine. Offer these, and say they can type their own: