Integrations

Connect Kayse AI with the tools you already use to make your work easier. 🔗

🌟 Overview

Kayse AI works behind your existing CRM, practice management system, and other tools to keep everything in sync. Integrations help you:

• Sync cases and clients with your CRM or practice management system
• Automatically update records across systems
• Trigger actions in other tools
• Import data from your existing systems
• Export data for reports and analysis

🔄 CRM Integrations

Connect Kayse AI with your CRM or practice management system so data flows between them automatically.

📋 Available CRM Integrations

Kayse AI works with popular CRM and practice management systems. Talk to your admin or our support team to get an integration set up.

✨ Integration Features

Feature	Description
Bidirectional Sync	Changes go both ways
Real-Time Updates	Syncing happens right away
Field Mapping	Match Kayse AI fields to your CRM fields
Status Mapping	Match case statuses between systems
Selective Sync	Pick which data gets synced

🛠️ Setting Up CRM Integration

1. Go to Settings → Integrations
2. Click your CRM from the list to open its detail screen
3. Use the Configuration tab to enter your CRM API credentials and turn on the integration
4. Use the CRM Mappings tab to set up which fields and statuses match
5. Test it with a sample record

🗺️ Field Mapping

Match Kayse AI fields to your CRM fields:

Kayse AI Field	Maps To
Case Name	Matter Name / Case Title
Case Type	Practice Area / Matter Type
Case Status	Status / Stage
Client Name	Contact Name
Phone	Phone Number
Email	Email Address
Custom Fields	Custom CRM Fields

📝 LawRuler and SmartAdvocate Mapping Notes

• Field mappings are designed to be safe: updating refreshes the available CRM fields while keeping your saved mappings.
• SmartAdvocate mappings handle both regular statuses and substatuses (which many SmartAdvocate firms use).
• If a CRM field can't be loaded, Kayse AI shows an error message in the mapping screen instead of failing quietly.

🔀 "Send mapping to LawRuler / SmartAdvocate" toggles

• Enabled: Kayse AI sends your mapped field/status updates to the CRM when changes happen in Kayse AI.
• Disabled: Kayse AI won't push mapped updates to that CRM. Your saved mappings stay safe - they just aren't used while the toggle is off.
• These toggles don't delete your mappings. They only control whether updates get sent.

📊 Status Mapping

Set up how case statuses translate between systems:

1. Go to integration settings
2. Click Status Mapping
3. For each Kayse AI status, pick the matching CRM status
4. Save your mappings

⚙️ Sync Settings

Setting	Description
Sync Direction	One-way or both ways
Sync Frequency	Right away, every hour, or once a day
Conflict Resolution	Which system wins when there's a disagreement
Initial Sync	Bring in existing records

📈 Sync Monitoring

Keep an eye on how syncing is going:

Metric	Description
Last Sync	When the last sync happened
Records Synced	How many records have been synced
Errors	Sync failures to look at
Pending	Records waiting to be synced

📅 Scheduling (Appointment Booking)

Connect a scheduling integration so Agent Builder agents can check availability and book appointments during calls.

Setting Up the Scheduling Integration

1. Go to Settings → Integrations
2. Click the Scheduling card and then Connect
3. Enter your scheduling API key and click Save
4. The integration card shows a green Connected badge when active

Using Scheduling in Agent Builder

When the scheduling integration is active, you can enable appointment booking on any agent:

1. Open the agent in Agent Builder
2. Turn on Appointment Booking
3. Enter your Event Type ID (the number at the end of your event type URL)
4. The company timezone is used automatically for all bookings

All booking-enabled agents share the company-level API key. There is no need to enter a key per agent.

Disconnecting

1. Go to Settings → Integrations → Scheduling
2. Click Disconnect

Disconnecting removes the stored API key. Agents with appointment booking enabled will no longer be able to book until a new key is added.

🔔 Webhooks

Send real-time event data to your CRM, Zapier, or any external system whenever something happens in Kayse AI. Webhooks are set up at the company level and can be reused across campaigns.

Setting Up a Webhook

1. Go to Company → Integrations
2. Select Webhooks to open the detail screen
3. Click New
4. Enter your destination URL (must be HTTPS and publicly reachable)
5. Select which events to subscribe to, or leave empty to receive all events
6. Optionally attach an App Key for extra verification
7. Save and send a test

You can also create webhooks from within a campaign under the Workflows tab. Campaign-scoped webhooks only fire for events in that campaign.

Available Events

Event	Trigger
call_started	A campaign call begins
call_ended	A campaign call finishes
call_analyzed	Transcript and summary for a call are ready
transcript_updated	Live transcript updates arrive during a call
transfer_started	A live transfer is initiated
transfer_bridged	A transfer successfully bridges
transfer_cancelled	A transfer is cancelled or fails to connect
transfer_ended	The transfer leg ends
message_sent	An outbound message (SMS, email, etc.) is sent
message_delivered	The provider confirms a message was delivered
task_completed	A case task is marked as completed
form_submitted	A form task is submitted

TIP

Leave the event selection empty to receive all event types, including any new types added in the future.

Filtering

Filter	Description
Campaign	Limit deliveries to events from specific campaigns. Only works with call events.
Case Type	Limit deliveries to events matching specific case types.

Authentication & Security

Every delivery includes an HMAC-SHA256 signature in the X-Kayse-Signature header so your server can verify requests came from Kayse. You can also attach an App Key that is sent as X-Public-Api-Key on every delivery.

Method	Description
HMAC Signature	Every webhook is signed with a per-webhook signing secret
App Key	Optional API key sent in the X-Public-Api-Key header

Delivery & Retries

Your endpoint should return a 2xx status within 15 seconds. Failed deliveries are retried with exponential backoff over a 24-hour window. You can also manually replay failed deliveries from the webhook detail view.

Delivery Logs

Every delivery attempt is logged. Open a webhook and check Recent Deliveries to inspect request headers, payloads, response codes, and errors.

Further Reading

See the Webhooks API Reference for full payload schemas, signature verification examples, and detailed retry behavior.