Platform Coverage & Integrations | Skribby | |
|---|---|---|
Supports multiple data capture form factors Captures meetings via bot API, desktop SDK, or other capture modes. | Captures meetings via bot API, desktop SDK, or other capture modes. | Meeting bot only |
Integrates with multiple video conferencing platforms Works across Zoom, Google Meet, Teams, Webex, Slack, GoTo, and more. | Only Zoom, Google Meet, Microsoft Teams | |
Handles signed-in bot workflows Allows bots to authenticate and join meetings as signed-in users. | Bots able to sign in on Zoom, Microsoft Teams, Google Meet, and Slack Huddles | |
Supports breakout rooms Enables bots to record breakout rooms. | Supported for Microsoft Teams and Zoom | |
Provides free calendar integration Connects to user calendars for read-only scheduling data. | No calendar integration | |
Provides robust documentation Provides clear, accurate, thorough and consistent developer documentation. | Easy-to-follow, consistent documentation with sample repos and demo videos | Documentation inconsistent with actual API behavior. |
Allows for customizable bot name and avatar Lets teams define the bot’s name, avatar, logo, or video identity. | Full control over name, logo, avatar, or video | Can only customize the bot's name |
Supports sending custom consent message Delivers configurable consent prompts via chat, bot speaking, etc. | Full control over name, logo, avatar, or video | Can only send an initial chat message |
| Recording & Transcription | Skribby | |
|---|---|---|
Produces a video recording Produces a video recording (single merged track). | Need to upgrade to record video | |
Produces an audio recording Produces an audio recording (single merged track). | ||
Provides speaker-separated audio streams Produces individual audio recordings for each meeting participant. | ||
Provides speaker-separated video streams Produces individual video recordings for each meeting participant. | ||
Supports 100% perfect diarization Captures each speaker on their own track with no loss during overlap. | Overlapping speech is merged so diarization isn’t accurate | |
Identifies speakers accurately Associates speech with the correct participant names and emails | Can confuse one speaker as multiple speakers. No speaker names for Zoom | |
Produces clean video output Generates video without UI of the meeting platform. | Video shows meeting platform UI, modals and popups. | |
Generates post-meeting transcription Creates transcripts after meetings. | Only available at extra cost, with no free transcription option | |
Provides speaker-diarized transcripts Provides detailed transcripts labeled with participant names | Transcripts don’t have speaker names, speaker diarization provided separately | |
Streams real-time transcription Provides live transcription during the meeting. | ||
Handles multiple languages Transcribes meetings in a variety of languages. | ||
Transcribe pre-recorded audio Allows you to upload and transcribe existing audio files |
| Real-Time Capabilities & Interactivity | Skribby | |
|---|---|---|
Streams real-time audio Delivers audio in real time via WebSockets or webhooks. | WebSocket, webhook, and RTMP | Only available at extra cost |
Streams real-time video Delivers video in real time via WebSockets, webhooks, or RTMP. | WebSocket, webhook, and RTMP | |
Delivers real-time participant events Streams event signals such as join, leave, mute, unmute, and other events. | WebSocket or webhook | Limited to participants joining, starting, and stopping speaking |
Delivers real-time chat messages Streams chat messages as they occur in the meeting. | WebSocket or webhook | WebSocket only |
Enables interactive agents Allows bots to speak, display media, send chat messages, and respond dynamically in meetings. | Meeting bot form factor supports AI Agents |
| Reliability & Bot Behavior | Skribby | |
|---|---|---|
Allows for pausing and resuming recording Enables temporary stopping and restarting of recording. | ||
Ensures platform reliability Joins meetings consistently across supported platforms. | Frequent connection failures on certain platforms. | |
Dedupes bots Prevents accidental bot duplication from rapid or repeated requests. | ||
Detects other bots Recognizes bot participants through behavioral and event cues. | Detects other bots based on user names, events, and silence | Detects other bots based on participant silence |
Joins meetings immediately Connects bots to meetings in under ten seconds. | Depends on the platform, can take up to a minute to join Google Meet calls |
Data Delivery & Observability | Skribby | |
|---|---|---|
Delivers logs Exposes logs and debug information for troubleshooting | ||
Supports flexible data delivery Provides data through REST API, webhooks, or WebSockets. | Also supports WebSockets and RTMP | |
Offers configurable data retention Gives teams control over data-retention duration. | Infinite, custom, or zero data retention | Yes, but only gives the option to store recordings for one week or one year |



While Recall.ai and Skribby both offer meeting bot APIs, they have some important differences. Recall.ai offers a smoother developer experience and over 99.9% reliability compared to 42% reliability for Skribby. We’ve extensively tested Skribby’s performance – below, we’ll dive into what sets Recall.ai apart.
To inform our findings, we extensively tested Skribby and Recall.ai in 300 calls across Google Meet, Microsoft Teams, and Zoom.
During our testing, Skribby experienced extensive reliability issues. For example, on Google Meet, Skribby’s bots either never made it into the meeting or got kicked out immediately 66.7% of the time. With Skribby, we also encountered long wait times for bots to join meetings – on average, over a minute for Google Meet. In our tests, Recall.ai bots successfully joined calls 100% of the time and took an average of just 15 seconds to join a Google Meet meeting.
We also evaluated the ease of setting up meeting bots with Skribby’s API, and found that Skribby does not provide all the resources developers may need during implementation. Their documentation is difficult to search, and they don’t offer sample apps or an “Ask AI” feature to help developers navigate their API docs. When sending bots to meetings, Skribby doesn’t provide logs to help you troubleshoot when bots don’t successfully join or record meetings. In comparison, Recall.ai provides detailed logs and documentation, many sample apps, and an “Ask AI” feature in API docs to help developers quickly find what they need.
When we tested Attendee, we ran into edge cases that their platform did not account for. For example, we found that Attendee bots would not join if the host was in another meeting. This is a fundamental limitation of their API, and they don’t offer a workaround for this situation. In contrast, Recall.ai allows bots to join and remain in a call even if the host is not present or in another meeting.
Recall.ai offers multiple ways to capture meeting data, with a Meeting Bot API and a Desktop Recording SDK, plus a Mobile Recording SDK launching soon. This allows users to record chats that happen on video conferencing platforms, in person, and on the phone, with or without a bot. Skribby only supports recording through sending bots to meetings on video conferencing platforms, which restricts flexibility for users.
The other main difference between Recall.ai and Skribby is platform coverage. Recall.ai’s unified API works across all major video conferencing platforms, supporting Zoom, Microsoft Teams, Google Meet, Slack Huddles, Webex, GoTo Meeting, and more. Meanwhile, Skribby only supports Zoom, Microsoft Teams, and Google Meet.
Recall.ai includes both real-time audio and video streaming capabilities in every pricing plan. However, Skribby users must purchase an add-on to get real-time audio from meetings, and Skribby does not support real-time video streaming at all.
Many companies are looking to build interactive AI agents that can have real-time conversations directly in meetings. Recall.ai’s Output Media feature enables two-way AI agent interactions by sending data back into meetings, streaming audio output and displaying images or video. In contrast, Skribby bots are receive-only – they can capture and transcribe content, but can't stream anything into the meeting.
Recall.ai offers perfect diarization, meaning that speech remains accurately attributed and labeled with speaker names even when multiple people are talking at once. While Recall.ai allows you to get separate audio streams per speaker, Skribby only offers mixed audio that merges overlapping speakers and makes attribution more difficult. Skribby also does not accurately label transcripts with participant names, so it’s harder to understand who said what during a conversation.
Though Recall.ai charges $0.50 per hour for a Pay As You Go plan and Skribby charges $0.35 per hour, Skribby has several hidden costs. For example, Skribby charges an extra $0.05 per hour for real-time audio and metadata, plus an additional $0.05/h for recording video, adding up to a total of $0.45/h. Recall.ai offers real-time and asynchronous audio and video recording at no extra charge.
Skribby also does not offer a free transcription option, meaning that users will always incur additional costs for transcribing meetings. Given the price of Skribby’s third-party transcription providers, the hourly costs for using Skribby can exceed $1.16/hour. Meanwhile, Recall.ai offers the option of using perfectly diarized, free transcripts generated by native meeting captions.
Recall.ai’s pricing also includes a free Calendar API, which connects Recall.ai with your users’ Google Calendar or Microsoft Outlook accounts. This lets you automatically send meeting bots to select events on your users’ calendars, while enriching meeting recordings with calendar information like participant emails and meeting titles. Skribby doesn’t have a calendar integration at all, with no built-in way to dispatch bots to meetings on a calendar.
Given that Recall.ai includes all of the above features in its hourly pricing model, Recall.ai’s pricing is very similar to Skribby’s, while offering a much richer feature set. Moreover, Recall.ai offers volume discounts that allow customers to get an hourly recording rate below $0.50, while Skribby does not lower prices for high-usage customers. This makes Recall.ai’s pricing much more scalable than Skribby’s, supporting both enterprises and startups who want to build a core part of their product with Recall.ai’s API.
Recall.ai consistently comes out on top in terms of reliability, flexible meeting recording, diarized transcription, and developer experience. If you’re a startup or enterprise looking for a way to record and transcribe meetings across different video conferencing platforms, Recall.ai is the clear choice.
Content in a cell |