Sabra for Zoom
Sabra attends investor calls on behalf of a bank using BookRunner and files each one against the issuer. It joins as a visible participant, it listens, and it does not take part.
BookRunner serves banks and institutional investors under contract. This app is not intended for general installation.
Adding the app
Sabra is added once, to the Zoom account that hosts or attends the calls. It is not installed per person and there is no per-user sign-in.
- Sign in to Zoom as a user who is allowed to add apps to your account.
- Open the install link above and read the permissions Zoom lists on the consent screen.
- Choose Allow. Zoom returns you to BookRunner.
- In BookRunner, open Roadshows. The meeting-bot section is where a call is added and where its status is shown.
When it worked: the app appears under Manage → Added Apps in the Zoom App Marketplace, and adding a call in BookRunner produces a row whose status moves on its own from Requested through to In meeting at the call's start time.
If your administrator's app restrictions block it: Zoom shows a message saying the app is not approved for your account, and nothing is added. Only a Zoom account owner or admin can lift that, in the Zoom admin console under Advanced → App Marketplace → App Permissions. Ask them to allow this app by name, or to pre-approve it for the account. There is nothing to retry on our side until they do.
Using it
Sabra attends two kinds of call: investor calls that were publicly announced through the exchange, and calls a banker added deliberately by pasting the link. Nothing else is joined — there is no calendar scan and no automatic discovery beyond the exchange announcements.
It joins as a visible participant named Sabra · BookRunner, with camera and microphone off. It never connects to the meeting's audio. It does not speak, does not send chat messages, and does not ask questions. It never starts a recording and never requests recording permission, so the host is never prompted and no recording banner appears.
What is kept. One attendance record per call:
What is not kept. No audio, no video, no transcript, no captions and no chat. Sabra does not subscribe to the meeting's media at all — the part of the Zoom SDK that would deliver it is not built into this app — so there is no copy of the meeting anywhere, in memory or on disk, to keep or to lose.
The meeting passcode and the unmasked join link are held apart from the attendance record, readable only by the service that does the joining, and are never sent to a browser.
Webinars that require registration. Some investor calls are Zoom webinars behind a registration form. Sabra cannot complete every one of those on its own — a number of them refuse automated submission, which we do not work around. In that case a person at BookRunner registers Sabra once, by hand, using BookRunner's own address, and Zoom sends back a personal join link. That link is stored the way the passcode is: apart from the record and readable only by the joining service. From then on the call runs like any other.
When a registration is refused, the page Zoom showed at the moment of failure is saved to private storage so the failure can be diagnosed. Those captures contain the issuer's own public registration page and what Sabra typed into it — the bot's name and BookRunner's address. They are not shared.
Removing the app
- Sign in to the Zoom App Marketplace.
- Open Manage → Added Apps, or search for the app by name.
- Find Sabra for Zoom and choose Remove.
- Confirm the removal.
What stops immediately. Sabra joins nothing further. A call already scheduled in BookRunner will fail to join rather than join silently. If Sabra is in a meeting at the moment you remove the app, a host can also remove it from the participant list, or a BookRunner administrator can stop it from the Roadshows page — it leaves within seconds either way.
What happens to records already created. The attendance records described above are the bank's own record of calls it attended, and removing the app does not delete them. To have them deleted, write to support@bookrunner.app. Retention and deletion requests are covered by the privacy policy.
Troubleshooting
The row on the Roadshows page carries the reason as a sentence, not a code — read that first. The three common ones: the host never admitted it from the waiting room, in which case it waits and then gives up; the meeting had not started; or the call was a webinar whose registration was refused, which the row says in those words. Sabra joins at the scheduled start and never earlier, so a row still reading Requested before the start time is behaving correctly.
That is expected to work and nothing needs to be done. Sabra leaves and the record shows it was removed by the host, along with how long it was in the meeting. It does not attempt to rejoin. A host who would rather it did not attend at all should say so to the banker who added the call.
Almost always an account restriction rather than a fault: the Zoom account has app installation limited to approved apps, and an owner or admin has to allow this one. See Adding the app above. If the error mentions something else, send us the exact wording and the Zoom account it happened on.
That is by design. Sabra attends one meeting at a time; a second call scheduled for the same slot waits rather than overlapping.
Common questions
It is BookRunner's meeting participant, and no — being visible is the point. It appears in the participant list under that name from the moment it joins, so anyone in the room can see it is there.
No. Sabra does not record, transcribe or caption, and it never requests recording permission from the host.
No.
The display name you were using in that meeting, Zoom's numeric id for you in it, and the times you joined and left. Nothing else. Write to support@bookrunner.app to ask what is held or to request deletion.
Write to support@bookrunner.app — put “Security” in the subject for the second. Guides for the rest of BookRunner are on the support hub.