CallRail
CallRail provides call tracking, dynamic number insertion, and call recordings. Kenzsys connects to CallRail via a webhook — no OAuth — so every completed call lands in your dashboard within a second or two of hanging up.
What gets synced
- Caller name and phone number
- Tracking number called (so we know which campaign or location)
- Source and campaign data attached by CallRail (Google Ads, organic, GBP, etc.)
- Call duration and recording URL
- Call transcript (if you have CallRail Conversation Intelligence)
Step 1 — Find your Kenzsys webhook URL
In Kenzsys, go to Settings → Integrations → CallRail and click
Show webhook URL. Copy the URL — it looks like
https://app.kenzsys.com/api/webhooks/callrail/<your-org-id> and is unique to
your organization.
Step 2 — Add the webhook in CallRail
- In CallRail, go to Settings → Integrations → Webhooks.
- Click Create Webhook.
- Choose the trigger: Post-Call (this ensures we receive completed calls with recordings).
- Paste your Kenzsys webhook URL into the URL field.
- Set the request format to JSON.
- Under Companies, select the CallRail company (or companies) you want to sync.
- Save.
Step 3 — Send a test call
Place a test call to any of your tracking numbers, let it go for at least 10 seconds, and hang up. Within a minute, the call should appear in Leads → All with full attribution. The CallRail card in Kenzsys will flip to "Connected" and show the time of the last received webhook.
Recordings: Kenzsys does not store CallRail recordings — we link to the recording URL CallRail hosts. If a call is older than your CallRail retention window, the recording link will 404 even though the call metadata remains in Kenzsys.
Troubleshooting
If calls aren't appearing, check CallRail's webhook log (Settings → Integrations → Webhooks → your
webhook → History). You should see a 200 response from Kenzsys. A 404
means your webhook URL has a typo. A 401 means the org-id segment is wrong — get a
fresh URL from the Kenzsys settings page.