Clinical documentation · Production

Verbal uses Recall.ai to streamline video meeting integration for AI-driven clinical documentation

The problem

Verbal's AI clinical documentation platform required seamless access to patient-provider video conversations across multiple meeting apps, but building custom integrations in-house required a dedicated engineer, two to three months of development per platform, and ongoing maintenance for scalability and stability issues.

First attempt

Verbal's homegrown meeting-platform integrations required a dedicated engineer who spent two to three months per platform and still needed ongoing attention for scalability and stability problems discovered after launch.

Workflow diagram · grounded in source
1
Patient meeting on video call
Trigger
A patient meeting takes place on a video call platform such as Zoom.
▾ source quote
“patient meetings on video calls”
2
Recall.ai captures meeting data
Integration
Recall.ai's API integrates with the video meeting platform to deliver conversation data to Verbal's AI platform.
▾ source quote
“Recall.ai's API could simplify how the Verbal platform integrated across video meeting apps”
3
AI analyzes conversation data
Ai action
Verbal's AI captures and analyzes conversation data from patient meetings on video calls.
▾ source quote
“using AI to capture and analyze conversation data from patient meetings on video calls”
4
Clinical documentation generated
Output
The Verbal AI app automatically generates clinical documentation like SOAP, SBAR, and therapy progress notes in electronic medical records.
▾ source quote
“the Verbal AI app automatically generates clinical documentation like SOAP, SBAR, therapy progress notes, and other key information in electronic medical records”
Reported outcome

By switching to Recall.ai, Verbal completed the Zoom integration in one and a half to two weeks and freed their entire engineering team to build new features rather than maintaining meeting-platform integrations.

Reported metrics
Homegrown integration build timetwo to three months
Recall.ai integration switch timeone and a half to two weeks
Engineering team capacity for new featuresable to allocate the entire team in building new features
Reported stack
Recall.aiZoom
◆ Does this fit your context?

Compare to your context

Tell us your scale, team, and constraints. We'll show what changes at your size, what fails at your scale, and whether this case is a fit, needs adaptation, or won't scale to you. Free demo, no signup.

Compare to your context →
~30 seconds · free
Source
https://www.recall.ai/customers/verbal
Read source ↗

Frequently asked questions

What did this team achieve with this AI workflow?

By switching to Recall.ai, Verbal completed the Zoom integration in one and a half to two weeks and freed their entire engineering team to build new features rather than maintaining meeting-platform integrations.

What tools did this team use?

Recall.ai, Zoom.

What results were reported?

Homegrown integration build time: two to three months; Recall.ai integration switch time: one and a half to two weeks; Engineering team capacity for new features: able to allocate the entire team in building new features (source-reported, not independently verified).

What failed first in this deployment?

Verbal's homegrown meeting-platform integrations required a dedicated engineer who spent two to three months per platform and still needed ongoing attention for scalability and stability problems discovered after launch.

How is this clinical documentation AI workflow structured?

Patient meeting on video call → Recall.ai captures meeting data → AI analyzes conversation data → Clinical documentation generated.

Related clinical documentation cases

WHAT TO DO WITH THIS

Now compare it to your context

This case is one data point. Whether its pattern fits you depends on your volumes, your stack, and your exception load — that comparison is the step no case study can do for you.

Browse the Clinical documentation cases →