Tawk.to
For teams running Tawk.to for website chat, Strkr threads conversations onto the matching contact and triggers flows on new-visitor and converted-chat events. Zero cost on the chat side, full CRM context on the Strkr side.
Everything Tawk.to does inside Strkr.
- Chat transcript logging on contact
- Visitor identification
- Flow triggers on chat-converted
- Agent assignment synced to Strkr owner
Native code, not a shim.
OAuth where available
Tawk.to 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 Tawk.to once; every teammate uses the shared connection without re-authenticating.
Disconnect at any time
Admins or users can disconnect Tawk.to from inside Strkr. Stored tokens are deleted and the provider's revocation endpoint is called within 24 hours.
Tawk.to is on the roadmap.
We ship integrations as first-class native code, which takes a little longer than a Zapier shim. If Tawk.to is a dealbreaker for your evaluation, reply to the welcome email after you start a trial and we'll flag it to the roadmap.