Drift
Drift conversations and booked meetings attach to the matching Strkr account. Lead-routing rules fire on chat-booked and chat-converted so pipeline reflects conversational revenue motion.
Everything Drift does inside Strkr.
- Chat session logging on the account
- Booked meetings routed to the owner
- Flow triggers on chat-converted
- ABM playbook sync
Native code, not a shim.
OAuth where available
Drift 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.
Shared by the workspace
A workspace admin connects Drift once; every teammate uses the shared connection without re-authenticating.
Disconnect at any time
Admins or users can disconnect Drift from inside Strkr. Stored tokens are deleted and the provider's revocation endpoint is called within 24 hours.
Drift is on the roadmap.
We ship integrations as first-class native code, which takes a little longer than a Zapier shim. If Drift is a dealbreaker for your evaluation, reply to the welcome email after you start a trial and we'll flag it to the roadmap.