Integrations

Where Rotwatch canask your chatbot.

Through the chat widget on your public website or your chatbot's own HTTPS endpoint. API connections to Intercom, Zendesk and LiveChat are opening soon.

Available now

No vendor account needed.

Website audit

Available

Rotwatch opens the chat widget on your public website in a browser, as a customer would, and asks each question there. It needs no key: a widget without vendor-specific steps goes through Rotwatch's general widget driver.

Before an audit you prove that you own the domain and approve the questions. If the widget asks visitors to sign in, Rotwatch records that and does not send the question.

What you need
  • A public website with a chat widget
  • A DNS record or a file that proves you own the domain
Start a website audit

Your own chatbot API

Available

Rotwatch sends questions straight to your chatbot's endpoint, in staging, production or sandbox, using a bearer token you save. Approving the connection check sends 1 test question.

What you need
  • Your chatbot's HTTPS endpoint
  • A bearer token
Connect your chatbot API
API connections

Through your vendor's own API.

Rotwatch asks your chatbot through your vendor's API, with access you give it on the Chatbots page of your dashboard.

Each vendor bills its AI answers in its own terms. The dashboard shows the vendor's fee note before you connect, and again before every audit with the line on each card below, where N is the number of questions you approved. No audit starts until you tick that you read it.

Intercom

Opening soon
What you need
  • Where your workspace is hosted: US, Europe or Australia
  • Your workspace's Fin Agent API key, once Intercom has granted access
  • A webhook: you save Rotwatch's address in Intercom, then paste the signing secret Intercom shows
Intercom's fee note

Intercom bills Fin Agent API conversations on outcomes, and its page says pricing is "being finalised and is subject to change". A question Fin answers through the API counts as a resolution, which Intercom bills to your workspace.

Before each audit: This audit sends N questions to Intercom.

Zendesk

Opening soon
What you need
  • Suite Professional or above
  • A Conversations API key, created in Admin Center
  • Your Zendesk subdomain and app ID
Zendesk's fee note

Zendesk bills AI agent resolutions at USD 1.50 committed or USD 2.00 pay as you go, and monthly active users above 1,000 at USD 50 per 2,500. Whether test conversations count toward either is not stated.

Before each audit: This audit sends N questions to Zendesk.

LiveChat

Opening soon
What you need
  • Sign in with LiveChat
  • Your LiveChat owner or administrator approves Rotwatch's app
LiveChat's fee note

LiveChat bills AI resolutions: 10 or 200 are included a month by plan, then USD 0.99 each, and when the allowance runs out the AI Agent stops taking new chats. Whether a test chat counts as a resolution is not stated on LiveChat's pages.

Before each audit: This audit sends N questions to LiveChat.

Your connection

How Rotwatch handles your connection.

What Rotwatch does with your access and your chatbot's answers.

  • Your token or key is kept in Supabase Vault, never in plain text, and never shown again, not even part of it.
  • Revoking a chatbot or disconnecting a vendor deletes Rotwatch's copy of its token or key. Deleting the domain or your account deletes it too.
  • No audit question goes to Intercom, Zendesk or LiveChat until you tick that you read its fee note, and the server checks again before the audit runs.
  • Your Intercom key is checked once, with 1 request to your region's server only. No other region is ever tried.
  • Rotwatch uses your Zendesk key only to read which AI agent your messaging setup puts in charge, create its test user and its own conversation, send the question and read the replies. Any other request is refused before it leaves. The key itself can read every conversation, so create one just for Rotwatch.
  • Rotwatch attempts to tag each test chat rotwatch-audit and close it. Failed cleanup can leave a chat open or untagged. LiveChat chats cannot be deleted, so your agents can see them.
  • The policy and chatbot evidence quotes come directly from the captured text, without paraphrasing. The model classifies the comparison and writes the explanation; it does not generate those evidence fields.
  • An answer that arrives as HTML is shown as its text, and the report says exactly how that text was made.
Coming soon

Next connections.

Planned, with no date yet. Until then, a website that runs one of these chat widgets can use the website audit.

  • AdaComing soon
  • BotpressComing soon
  • ChatwootComing soon
  • CrispComing soon
  • DialogflowComing soon
  • DriftComing soon
  • FreshchatComing soon
  • FreshdeskComing soon
  • FrontComing soon
  • GladlyComing soon
  • GorgiasComing soon
  • Help ScoutComing soon
  • HubSpotComing soon
  • KustomerComing soon
  • Microsoft Copilot StudioComing soon
  • SalesforceComing soon
  • tawk.toComing soon
  • TidioComing soon
  • VoiceflowComing soon

Need another one? Tell us at support@rotwatch.com

Questions about a connection?

Email us and a person will reply.

support@rotwatch.com