Book a demo
Sales · Client calls · Apache 2.0

Sales Call
Transcription
API

Vexa sends a bot to each sales or client call on Google Meet, Microsoft Teams or Zoom and returns the transcript by speaker.

2.9k stars on GitHub
vexa · api
Zoom · Teams · MeetVexa botTranscriptsYour CRMREST · WebSocket
  • Zoom · Teams · Meet
  • Vexa bot
  • Transcripts
  • Your CRM
  • REST · WebSocket
Teams
Meet
Vexa
🦀
Meeting data for your agents

Your agents read the meeting while it runs.

The transcript streams to your agents as people speak, over WebSocket or MCP.

Built for sales and client calls

Vexa joins from the meeting link, records the call and transcribes it while it runs.

  • One API across Meet, Teams and Zoom
  • A signed webhook when each call ends
  • Summaries and next steps in your own pipeline
Send a bot to a booked sales call
# From your scheduler or CRM workflow, when a sales call is booked
curl -X POST "$API_BASE/bots" \
  -H "Content-Type: application/json" \
  -H "X-API-Key: $API_KEY" \
  -d '{
    "platform": "google_meet",
    "native_meeting_id": "abc-defg-hij",
    "bot_name": "Acme Notes"
  }'

# When the meeting.completed webhook arrives, read the transcript
curl "$API_BASE/transcripts/google_meet/abc-defg-hij" \
  -H "X-API-Key: $API_KEY"

# Then summarize it with your model and write it to the deal with your
# CRM's API. Keep your own map from the meeting to the deal.
Set $API_BASE to https://api.cloud.vexa.ai (hosted) or http://localhost:18056 (self-host). Get $API_KEY from /start.

Common patterns

What sales teams build on Vexa

Three examples, each with Vexa as the capture layer and your own pipeline after it.

Calls on the deal

Sales leadership wants each call's transcript and next steps on the deal in the CRM.

What you get
  • Your CRM workflow sends the bot.
  • On meeting.completed, your handler fetches the transcript.
  • It writes your model's next steps to the deal.

Call review

Managers review calls to see how deals move and what clients push back on.

What you get
  • Vexa keeps the recording and the transcript by speaker.
  • Your review tool or agent reads them through the API.

Prompts during a call

You are building a tool that shows a rep prompts while the call runs.

What you get
  • Stream segments to your model with the rep's playbook.
  • Test the delay on your own calls.

Capture your sales calls

One API across Meet, Teams and Zoom. Fire it from your CRM workflow or calendar.

Quickstart

  1. Get a Vexa API keySign in at vexa.ai. Self-hosted: make all prints a key.
  2. Pick the triggerAnything that fires when a sales call is booked.
  3. POST /botsSend the meeting's platform and ID.
  4. Take the webhookSet PUT /user/webhook; on meeting.completed, fetch the transcript.
  5. Add your extractionSummaries, next steps, scoring: your model and prompts.

sales calls architecture

Vexa sends the bot and produces the transcript; your CRM stays the system of record.

Pipeline
bot → audio capture → speech-to-text → transcript segments → REST / WebSocket

Documentation

Go deeper on sales-call workflows

Sending bots, webhooks, transcripts and streaming.

Full reference at docs.vexa.ai.

Related reading

Keep going on sales calls

Related pages, guides and comparisons.

Sales-call transcription FAQ

What sales teams ask before they build on Vexa.

Is this an alternative to Gong or Chorus?

Gong and Chorus are finished products: recording, analytics and coaching dashboards, ready to use. Vexa is the open-source capture and transcription layer you build on; the summaries, scoring and dashboards are yours to build or buy.

Does it work for outbound, inbound and customer-success calls?

Yes. The API doesn't know the difference: send a bot to any Meet, Teams or Zoom call it can be admitted to. The same transcript comes back, and your pipeline decides what each kind of call needs.

How do next steps get extracted?

Vexa returns the transcript; extraction is your step. One shape: on meeting.completed, fetch the transcript, ask your model for next steps and action items as JSON, and write them to CRM fields.

What about consent to record?

Vexa has no consent feature. The bot joins as a visible participant under the name you set. Telling participants, and getting consent where the law requires it, is your process; some US states, such as Maryland, require every party's consent.

A seat, an hour, or free

A seat for your agent. An hour for what you build. No licence fee when you run it yourself.

Capture your sales calls. Keep the transcripts where you want them.

Sign in, copy an API key, send a bot to your next call. Free credit, no card.

Apache 2.0 · Self-host or cloud · No credit card required