Whereby
Whereby meeting rooms attach to Strkr bookings with no download required for attendees. Great for inbound booking pages where friction kills conversion. Per-user OAuth so each rep uses their own room.
Everything Whereby does inside Strkr.
- Browser-first join, no download for attendees
- Per-user OAuth: own Whereby room
- Auto-attach link to booking confirmations
- Low-friction for inbound meetings
Native code, not a shim.
OAuth where available
Whereby will ship with a native OAuth flow when it lands. No pasted credentials for admins to rotate manually.
KMS-encrypted tokens
Access and refresh tokens are envelope-encrypted at rest using a dedicated customer-managed KMS key. Decryption only happens in Lambda memory during an active API call; plaintext tokens never land in a log.
Scoped to the connecting user
Each teammate connects their own Whereby account. The token is scoped to that user and never gets reused by another user in the workspace.
Disconnect at any time
Admins or users can disconnect Whereby from inside Strkr. Stored tokens are deleted and the provider's revocation endpoint is called within 24 hours.
Whereby is on the roadmap.
We ship integrations as first-class native code, which takes a little longer than a Zapier shim. If Whereby is a dealbreaker for your evaluation, reply to the welcome email after you start a trial and we'll flag it to the roadmap.