Releases

Per-team delivery of status and chat webhooks

Teams that run several white-label platforms from one account can now have bot.statuschange and bot.chatmessage delivered straight to each bot's own callback URL, so each platform…

Sign-in fix for invited users, and reliable Microsoft calendar sync

A user invited to a team could not sign in until they belonged to one, which failed with a server error. Large Microsoft calendars also sync reliably instead of failing partway…

Zoom failures say what went wrong

Two Zoom failure reasons that had been arriving as an unknown error now report themselves, so you can tell a transient Zoom problem apart from a wrong passcode. The API reference…

Maintenance release

Dependency and security maintenance only. There is no change to the API, to webhooks, or to how bots behave in a meeting.

Teams links from sovereign clouds, and GIF bot avatars

Microsoft Teams meeting links served from sovereign and national clouds are now recognised instead of being rejected as an unknown platform, including when they arrive wrapped in…

Better speaker naming and an explicit Zoom passcode error

Speaker names survive collisions instead of everyone involved being anonymised, calls where two people share one microphone name both, and a Zoom bot given the wrong passcode says…

Bring your own transcription key on any plan

Using your own transcription provider key is no longer tied to a plan entitlement. A bot that asks for a provider nobody holds a key for is also rejected when it is created,…

Fewer unknown speakers, and proper status codes on Teams invitation errors

Transcripts that lost a real speaker to the bot's own timeline now fall back to the transcription provider's view, and a meeting's opening utterances are attributed rather than…

Bot avatars appear on Google Meet again

A bot's avatar image had stopped rendering on Google Meet — the camera failed silently as the bot started, so it joined with no image at all. This release also makes bots…

Bots honour the 12-hour recording cap

The bot side of the twelve-hour recording cap introduced in v2.6.2. A bot given a maxrecordingduration above six hours now records for the full requested duration instead of…

The last unknown speakers on Google Meet

This closes the remaining cases where a Google Meet speaker came back as "Unknown" — roughly one percent of them after the previous release, where the meeting's audio identified a…

Recording cap raised to 12 hours

The per-bot recording cap can now be set up to twelve hours, raised from six, for all-day sessions and long-running events.

Google Meet speakers named instead of unknown

Around three in ten speakers detected in Google Meet meetings were being delivered as "Unknown" — real speech, attributed to nobody. Those speakers are now resolved to the right…

Sub-accounts for resellers

Resellers can now open one account per end customer, each with its own API key, bots, recordings, webhooks and calendar connections, while everything those customers spend is…

Zoom bots stay for the whole meeting

Zoom bots could leave a meeting early when an entry message or a participant's chat message contained wording that looked like a removal notice. Removal detection is now scoped to…

Per-participant speaker attribution on Google Meet

Roughly half of Google Meet bots were falling back to on-screen observation, which attributes every speaker to one identity. Bots now hold the audio path that exposes each…

Teams transcripts name speakers on every kind of meeting

Some Microsoft Teams meetings deliver a single mixed audio stream, which left the bot with no way to tell speakers apart — those transcripts came back as "Speaker 1", "Speaker 2"…

Teams audio quality fix

Microsoft Teams recordings could come back with distorted audio. This release also corrects speaker attribution in Teams and Google Meet meetings where a participant was…

Newly added Google Meet logins can sign in

A Google Meet login added to an existing workspace failed to sign in on every run and silently joined anonymously, while older logins on the same workspace kept working. Setup…

Cap a bot's recording length, and clearer Zoom failures

A per-bot recording cap can now be set, which is useful for meetings that are left open long after everyone has stopped talking. Three Zoom and networking failure reasons are also…

Bring your own storage

Recordings, audio, transcripts and logs can now be written to your own S3-compatible bucket instead of ours, configured per team. Transcription also retries a provider that fails…

Transcripts no longer open with a run of unknown speakers

A transcript could begin with a stretch of "Unknown" before the first named participant, because the recording started before the speaker signal was live. Across thirty days of…

Real participant names in Meet and Teams transcripts

Transcripts that came back as "Speaker 1" and "Speaker 2" for Google Meet and Microsoft Teams meetings now carry real participant names, including the first sentence of a meeting…

Participant data removed from bot diagnostic logs

Everything a bot writes to its diagnostic log is now stripped of personal data at the point it is written — participant names, meeting URLs, email addresses, phone numbers, chat…

Corrected re-release of v2.4.1

This re-issues v2.4.1 with the correct bot version. The customer-facing changes are the same as v2.4.1, and nothing was added or removed — if you are on v2.4.1, this is the build…

Failed bots report a real duration, and two failure reasons are named

Bots that failed before producing a recording reported a duration of zero, which made per-bot cost impossible to compute from the webhook. They now report their real duration, and…

Authenticated Microsoft Teams bots

Bots can now join Microsoft Teams meetings signed in as a real Microsoft account rather than as an anonymous guest, which gets them into meetings that refuse guests and names…

Google Meet bots are flagged far less often

Google Meet bots now join from networks in regions you allow, and automatically avoid networks that have started getting bots flagged. In pre-production testing at ten concurrent…

Zoom browser bots get their own capacity

Zoom browser recording is heavier than Google Meet and Microsoft Teams recording, and was competing with them for the same capacity. It now runs on capacity of its own, which…

Smoother Zoom recordings

Zoom recordings could stutter and the audio lag behind, worst in busy meetings. The recorder now draws only the active speaker's tile rather than every participant's at full size.

Zoom chat sends exactly what you wrote

Chat messages sent to a Zoom meeting arrived with characters missing or reordered. They are now inserted as a single edit, so the message is exact. Zoom speaker-view recordings…

Retry visibility and Zoom audio and consent fixes

A bot that fails an attempt and is about to try again now reports a retrying status rather than going quiet, so you can tell a retry apart from a failure. Zoom recordings also no…

Zoom bots without credentials record on every creation path

Zoom bots created through batch, scheduled and calendar routes now fall back to the browser recorder when no Zoom credentials are supplied, as bots created one at a time already…

Zoom browser bots join more reliably and record correctly

Zoom bots that record through the browser now run on a hardened browser build with human-like input, which improves how often Zoom admits them. The mute and screen-share problems…

Zoom without credentials, and transcription that fails before the meeting rather than after

Zoom bots sent without Zoom credentials now fall back to a browser-based recorder instead of failing, and a bot that asks for transcription we have no usable key for is rejected…

Recording audio and A/V sync fixes

This release fixes Google Meet and Microsoft Teams recordings that captured silence, and corrects audio-video drift on recordings from both platforms.

Recover older recordings that failed to upload

Recordings that appeared blank in the dashboard because their upload had failed at the time can now be restored on request. Transcripts also separate speakers more accurately and…

Teams bots join reliably and record clean video

Microsoft Teams had begun treating recording bots as automated clients, which cost joins and degraded recordings. Teams bots now join on the same hardened stack Google Meet uses,…

Maintenance release

Internal database maintenance. There is no change to the API, to webhooks, or to how bots behave in a meeting.

Real speaker names in Teams transcripts

Microsoft Teams transcripts now identify who is speaking from the meeting's own participant data, matching what Google Meet already did. This release also adds a way to keep…

Bots start faster under load

Capacity is now kept ahead of demand, so a bot created during a busy period starts on machine capacity that is already running rather than waiting for new capacity to come up.…

No more duplicate status webhooks for delayed bots

A bot waiting to be picked up was re-sending the same bot.statuschange webhook every minute for as long as it waited. It now sends the status once.

Zoom privacy prompts no longer block the join

Zoom's recording-disclaimer and privacy-reminder dialogs are now handled during the join, so a bot is not left sitting behind a prompt it never answered.

Bots removed from a meeting now exit cleanly

A bot that a host removed from a Google Meet could get caught retrying the join, or sit on the removal screen until its grace period ran out. Both now end the bot promptly.

Longer silence timeout and a fix for Zoom bots crashing at startup

The silence timeout can now be set up to an hour, and a class of Zoom bot that crashed immediately on startup — depending on which machine it landed on — is fixed.

Repeated chat messages are delivered again

A participant who sent the same chat text twice had the second message silently dropped, because identical text from the same sender was suppressed permanently. Suppression is now…

Maintenance release

Internal build maintenance. There is no change to the API, to webhooks, or to how bots behave in a meeting.

Transcription no longer fails on a deprecated language option

Bots that passed a deprecated language-detection option in their transcription parameters had the whole transcription submission rejected. The option is now dropped before the…

Large recordings are no longer lost in post-processing

A slow inspection step on multi-gigabyte recordings could discard a fully captured recording and report it as a streaming failure. That step is now best-effort, and the recording…

Authenticated Google Meet bots and multi-provider transcription

Bots can now join Google Meet as a real Google Workspace user instead of an anonymous guest, and transcription runs on the provider of your choice — optionally with your own API…

Recordings recovered when an upload fails

When a bot's recording cannot be written to storage on the first attempt, its files are now recovered in the background and the bot completes normally once they land. Previously…

Participant video is visible again in Teams recordings

Microsoft Teams recordings show participant video again, after a regression in the previous release left the video stage blank. Google Meet is unaffected.

Google Meet bots are harder to flag

Google Meet bots now run on a browser build designed to avoid automated-client detection, which improves how often Meet admits them. No API or configuration change is required.

Longer Zoom join window and larger chat messages

Zoom bots are given considerably longer to complete the join handshake before giving up, which recovers joins that were failing on slow starts. Chat messages sent through the API…

Maintenance release

Internal networking maintenance for Google Meet and Microsoft Teams bots. There is no change to the API, to webhooks, or to how bots behave in a meeting.

Google Meet join retries use a fresh network each time

When a Google Meet join times out, the retry now comes from a different network instead of the one that just failed, and the final attempt connects directly. Bots that used to…

Bots no longer stick in the Google Meet waiting room

A bot could sit in the waiting room indefinitely when the meeting's chat icon showed unread messages, because the unread badge was misread as part of the waiting-room screen.…

More reliable Google Meet admission

Google Meet bots now join from residential networking during the phase where Meet decides whether to admit them, which materially improves admission rates. There is no API change…

Teams meetings that require sign-in now fail in seconds

Bots sent to Microsoft Teams meetings that refuse anonymous guests now report the reason within seconds instead of waiting out the full waiting-room timeout. Sign-up email…

Startup grace period for bots

Bots can now be given a startup grace window during which none of the automatic exit timeouts apply. It is aimed at meetings where participants routinely join late and a bot would…

The v2 API

The first tagged release of the v2 API. It covers sending bots to Zoom, Google Meet and Microsoft Teams meetings, scheduling them ahead of time, connecting a calendar so bots…