CallGuard AI works with your dialler and your CRM, not just one of each. Twilio, Amazon Connect, CloudTalk and Microsoft Teams each have a native adapter built for how that system actually sends a call; a REST API, SFTP pickup and a WebSocket streaming protocol cover everything else. On the CRM side, Zoho CRM is the connector already built; for any other CRM, CallGuard builds that same connection as part of setting your account up.
Some of these routes send CallGuard a call while it is still happening; most send it once it has already finished. Which one you're on decides what you get back, and when.
Twilio, Amazon Connect and CallGuard's own WebSocket API send audio as the call happens. The rolling transcript is checked about every 30 seconds, and a breach is sent only when the model rates it at 0.75 confidence or higher, straight to your own systems over the stream or a signed webhook — never as an email or a Slack message to a supervisor. Amazon Connect needs a small Lambda bridge, run in your own AWS account, to re-emit its voice stream to us; Twilio and the WebSocket API don't. When a streamed call ends, its full transcript is scored exactly like a recorded call, except that any consent question on it always goes to your review queue, because a live stream can't confirm who actually answered.
CloudTalk, Microsoft Teams (and any Zoom or Google Meet export), the REST API and SFTP pickup all hand CallGuard a call once it has already been recorded. CallGuard fetches or receives the file, transcribes it and scores it against your scorecard the same way either route works — nothing is flagged mid-call, because there is no mid-call to flag.
Each of these has a purpose-built adapter: vendor-specific frame parsing, its own ID matching, and setup steps of its own. Read the one for your system.
Point your Twilio Voice TwiML at CallGuard's streaming endpoint. Live transcription, mid-call breach detection and HMAC-signed webhooks, with no middleware and no Lambda bridge to run.
The Twilio integration →A small Lambda you deploy and run in your own AWS account re-emits Connect's Kinesis Video voice stream to CallGuard's WebSocket endpoint, so audio never leaves your account until it reaches us.
The AWS Connect integration →CloudTalk's "Call Ended" webhook points at CallGuard directly — no code to deploy. Recordings are fetched automatically, matched to the right agent by CloudTalk's stable ID, and call history can be backfilled for journey scoring.
The CloudTalk integration →Send a Teams meeting recording — or a Zoom or Google Meet export in the same formats — and CallGuard strips the video at ingest, keeping only the audio it needs to transcribe and score the conversation.
The Microsoft Teams integration →A named adapter above is the fastest route to set up, but none of them is a requirement. Underneath every one of them are the same general-purpose routes, open to any dialler, archive or in-house system that can post a file, a URL or a stream.
Push a recording in as a file or a URL, and CallGuard queues it, transcribes it and scores it. Poll the same endpoint for the result, or bulk-import a CSV of historical calls to backfill an archive.
Point CallGuard at a folder your dialler or recording archive already writes to. We poll it on a schedule, over password or private-key authentication, and pull down anything matching the file pattern you set.
The same streaming protocol behind the Twilio and Amazon Connect adapters, open to any dialler or your own agent desktop: mint a session token, stream audio over the socket, and get transcript and breach events back the same way.
Once you set a signing secret, a streamed call's breach alerts and its final score arrive as HMAC-SHA256-signed POSTs to your endpoint. Any call's result, streamed or recorded, can also be pulled at any time from the REST results endpoint.
CallGuard AI connects to whatever CRM your firm runs. Zoho CRM is the connector already built: a sale trigger in Zoho starts journey scoring, Reconciliation picks up the insurer's application once it lands, and the compliance score and a task for any breach write straight back to the record. For any other CRM, CallGuard builds that same connection — sale-triggered scoring, Reconciliation and result write-back — as part of getting your account set up. Either way, a scored call also reaches you the same way regardless of CRM: a signed webhook the moment it's scored, or a call to the REST results endpoint whenever you want to check.
Tell us what your dialler, meeting platform or CRM already does, and we'll tell you honestly which of these gets you scoring fastest.
Request a demo
