Sanaf AI
Start free
AI Meeting Assistants

Avoma, worked by an AI employee

Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your Avoma account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.

  • AI Meeting Assistants
  • Connects with a key
  • 16 ready-made tools
  • Asked in Slack or Teams
At work

An illustration of how the conversation reads, not a transcript from a client account.

What Avoma is

Avoma is an AI meeting assistant for recording, transcribing, analyzing, and managing meetings, calls, notes, scorecards, and conversation intelligence.

You paste in a key from your own Avoma account. It is kept encrypted, and you can withdraw it from inside Avoma whenever you like.

How a run works

One message in, the work done in Avoma.

  1. 01

    You ask

    You message your AI employee in the chat your team already has open, in one sentence, in your own words.

  2. 02

    It works out the step

    It decides what the job needs in Avoma. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own Avoma account, inside the access you granted it, doing the thing you asked for.

  4. 04

    It reports back

    It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.

16 tools it already has

What it can do in Avoma

These are the ready-made tools your AI employee already has in Avoma. It is not limited to them, but it never has to be taught these.

  • Create CallSubmit an externally hosted call recording to Avoma for asynchronous processing. This persistently creates external call state, and Avoma will download the recording from the suppl
  • Get CallRetrieve one externally ingested Avoma call by the dialer system's external ID.
  • Get Engagement SummaryAggregate Avoma engagement metrics across visible users for a required UTC date range and optional meeting and user filters.
  • Get MeetingRetrieve one meeting by UUID, including processing/readiness state and optionally CRM associations.
  • Get Meeting AnalysisReturn Avoma's AI insights, topical and speaker segments, and sentiment records for one processed meeting in a single read-only invocation.
  • Get RecordingGet time-limited audio and video URLs for a meeting recording.
  • List CallsList externally ingested calls in a required UTC date range, optionally filtered by inbound or outbound direction. Returns one page and a cursor.
  • List Configuration ResourcesList one Avoma configuration catalog: custom categories, smart categories, scorecards, templates, meeting types, or meeting outcomes.
  • List Engagement MetricsList per-user Avoma engagement metrics over a required UTC date range with meeting and user filters. Returns one page and an opaque cursor.
  • List MeetingsFind meetings visible to the connected Avoma user within a required UTC date range, with optional attendee, CRM, call-type, privacy-context, duration, and ordering filters. Returns
  • List NotesRetrieve Avoma notes for meetings in a required UTC date range, optionally narrowed to a meeting or custom category and rendered as JSON, HTML, or Markdown.
  • List Scorecard EvaluationsList Avoma scorecard evaluations, optionally filtered by UTC date range, scorecard templates, meeting, or evaluated users. Returns one page at a time.
  • List SnippetsFind user-created or AI-generated meeting snippets by meeting UUID or by a UTC date range of at most 180 days. Returns one page at a time.
  • List TranscriptionsFind full meeting transcriptions by meeting UUID or by a UTC date range, with attendee and CRM filters. Returns one page because transcript payloads can be large.
  • List UsersReturn users visible in the Avoma organization, including their UUID, email, role, teams, and active status.
  • List WebhooksAudit the connected organization's active Avoma webhook subscriptions without reading signing secrets.
Access, and who is in charge of it

You stay the boss of your Avoma account.

Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.

How we handle your data
  • It signs in to your own Avoma account. You are not moving anything into ours.
  • You grant access one app at a time, and you can take it back the same way.
  • Everything it does in Avoma is written down, with what it did and when.
  • Anything you tell it to check with you first, it checks with you first.
Other apps in the same corner of the business

It works in Avoma and the rest of your software in the same job

A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.

See every app

Questions people ask about Avoma

Can an AI employee really work inside Avoma?
Yes. It signs in to your own Avoma account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
Do I have to move anything out of Avoma?
No. Nothing moves and nothing is replaced. Your records stay in Avoma, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
How does it get into my Avoma account?
You paste in a key from your own Avoma account. It is kept encrypted, and you can withdraw it from inside Avoma whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
What can it actually do in Avoma?
It has 16 ready-made tools in Avoma today, among them Create Call, Get Call and Get Engagement Summary. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use Avoma and the rest of my software in the same job?
Yes, and that is usually the point. Reading a message in one app, checking a record in Avoma and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
Who decides what it is allowed to do in Avoma?
You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in Avoma is written down with what it did and when.