Avoma logo

Avoma + Memtro

Ask Avoma what was agreed on a call, what a customer raised and how calls scored.

Connect Avoma with an API key and Memtro reads the organisation's recorded meetings and calls with attendees and outcome, Avoma's AI notes with action items, decisions and questions, full transcripts by speaker, users, and scorecard evaluations. A list covers at most 92 days. It reads on demand and there is no hourly sync. When asked, and once an administrator has granted each action by name, it adds a dialer call for Avoma to record, using that user's recording minutes and not removable afterwards, makes Avoma's bot leave a live meeting for good, and creates or edits organisation-wide smart categories.

In Memtro

What you can do with Avoma in Memtro

Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Avoma tool, reads what it needs, and answers with the source cited.

What it does

  1. 01Meetings and calls newest first with subject, time, length, organiser, attendees, purpose and outcome, filtered by attendee email, calls only or internal only
  2. 02Avoma's AI notes per meeting: action items, decisions and questions, with the keywords that came up
  3. 03The full transcript of a meeting, speaker by speaker, cut when very long
  4. 04Scorecard evaluations with overall score, who scored, who was scored, the company and deals, and the organisation's users and smart categories
  5. 05When asked and granted, adds a dialer call for Avoma to transcribe and note, using that user's licence and recording minutes, and makes Avoma's bot leave a meeting in progress, which everyone sees and which cannot be undone
  6. 06When asked and granted, creates a smart category or adds and removes its keywords and prompts, applied to every meeting across the organisation

Acts when asked

When you ask it to

These tools change something in Avoma. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.

  1. 01Add a dialer call for Avoma to record and process (uses the user's recording minutes)
  2. 02Make Avoma's bot leave a live meeting
  3. 03Create a smart category
  4. 04Add or remove a smart category's keywords and prompts

Events

When it happens

Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Avoma for you. Each event can start a job, with the event as its input. Avoma signs every delivery, and one whose signature does not check out is refused before it is read.

Events and webhooks
  • 01AI notes are ready for a meeting or call
  • 02A meeting was booked through an Avoma scheduling page
  • 03A scheduler-booked meeting was cancelled
  • 04A scheduler-booked meeting was rescheduled
In practice

Ask it like you would a colleague

Once Avoma is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.

Avoma logoAvoma + Memtro
  • What did we agree with Acme on Tuesday?

  • What did Brightwave Ltd raise across our calls this month?

  • How did Dan Fletcher score on discovery calls this month?

  • Which action items came out of yesterday's internal meetings?

  • Add 'competitor pricing' with the keywords Globex and BigCo as a smart category

01

After a renewal call

The account lead asks what was agreed with Northwind on Tuesday. Memtro finds the call by attendee email, reads Avoma's AI notes and answers with the decisions and action items, and the questions the customer left open.

02

Tracking a competitor

Rosa Diaz, the sales manager, wants every call that mentions Globex flagged. She asks Memtro to add a smart category, and Memtro creates it with the keywords and prompt she gave. From then on Avoma looks for them in every meeting across the organisation and adds what it finds to the notes.

Teams

Where it fits

The teams that lean on Avoma most, a question each of them asks, and what they connect beside it.

Better together

Works with

A record in Avoma is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.

Also in Email, calendar and chat

Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.

Setup

How to connect

Connect withAPI key
  1. 1

    Avoma includes the API only on some plans, and an Avoma admin has to generate the key. It reads the organisation's meetings, not only theirs

  2. 2

    In Avoma open Settings → Organization → Developer, generate an API key with read access to meetings, transcripts and notes, and write access to calls and smart categories for the actions, and copy it

  3. 3

    In Memtro open Connections → Avoma, paste the API key and connect

  4. 4

    Ask what was agreed on your last customer call. A request over a long date range can time out

Also works from

Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Avoma tools are the same everywhere.

FAQ

Questions

Can Memtro change anything in Avoma?+

Only when you ask, and only what it has been granted: add a dialer call for Avoma to record and process (uses the user's recording minutes); make Avoma's bot leave a live meeting; create a smart category; add or remove a smart category's keywords and prompts. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.

Who can use a Avoma connection?+

A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.

Does Memtro store my Avoma data?+

Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.

How do I connect Avoma?+

API key. Avoma includes the API only on some plans, and an Avoma admin has to generate the key. It reads the organisation's meetings, not only theirs.

Can Avoma start a job?+

Yes. Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Avoma for you. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.

Connect Avoma in a few minutes

Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.

Where agents remember your company

Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.

7-day free trial · card on file, nothing charged until it ends · cancel any time