This comprehensive guide walks you through creating and managing ๐ Lists and use ๐ Voice AI Campaigns in Kayse.ai. Law firms can use these tools to automate case-related communication using human-like ๐ค AI Voice Agents that make calls and send SMS messages at any scale ๐ฒ.
๐ก Important: Before creating a Voice AI Campaign, you must create a List of people or cases that you would like to contact.
A "List" is any group of leads or cases you want your AI agent to call. You can select existing records from Kayse or upload new ones via Excel ๐.

๐ List Name: Enter a unique name (e.g., "Unreachable Camp Lejeune Cases").
๐ Select Case Source:
From Existing Cases:
Import via Excel:

โ Next Step: Youโre ready to launch a Voice AI Campaign!


๐ Calling Days: MonโFri by default. Selecting Sat/Sun will trigger a โ ๏ธ warning popup:
"It is not recommended to call consumers on the weekends. Are you sure you want to proceed?"
๐ Calling Hours: 12:00 PM โ 8:00 PM default; allowed window is 8:00 AM โ 9:00 PM (recipientโs time)

๐ Default retry after 4 hours
โ Recommended retries:
โ ๏ธ Do not exceed 5 callbacks/month per contact
In addition to the default and recommended retries, clients can now request a callback at a specific time and date.
Double-check:
โ Click "Start Campaign" to go live

Improve campaign conversion rates by adding pre-call and follow-up SMS texting to AI campaigns.

Message configuration:
Choose a custom message or use our prebuilt templates for ease of use
**Delay timer (before each AI call)๐*๐ We recommend a delay of at least 2 minutes after SMS are sent. Each AI call will occur near your specified delay time, with small variations possible due to processing and wireless carrier ecosystem factors.
Automatic SMS sync to third-party systems: All SMS texts that are sent are synced as notes to third-party systems (requires activation of integration in Company Settings such as Law Ruler legal CRM or SmartAdvocate legal practice management software.
Compliance Warning Regarding Mass Sending of SMS Text Messages: โ ๏ธWhen sending mass SMS messages, texts are delivered at a rate of 3 to 5 messages per second, depending on the type of phone number used. This pacing helps ensure compliance with carrier guidelines and industry best practices, reducing the risk of message blocking. Please be aware that larger batches may take a bit longer to send, as our system automatically manages delivery to support reliability and regulatory standards.
When scheduling outbound Voice AI calls, it's essential to be mindful of time zones โ and the real-world location of your contacts.
Even though we can estimate a contactโs time zone based on their phone numberโs area code, this isnโt always accurate:
๐ฑ Someone with a New York (Eastern Time) area code might now live in California (Pacific Time).
People often keep their original phone numbers even after moving to a different state, which means calling too early could unintentionally violate TCPA rules.
To stay compliant and respectful of your contacts' time:
By waiting until 11 AM ET, you:
Kayse automatically determines the most accurate local time zone for every contact so Voice AI Campaigns always run at compliant hours.
Each contact record stores a timezone, source, and confidence tag, allowing the system to track how reliable the data is and when to recalculate it.
Primary Source โ ZIP Code The system first checks the clientโs ZIP code (from imports, integrations, or LawRuler/SmartAdvocate syncs). ๐ก ZIPs missing a leading zero are automatically padded to ensure accurate detection.
Fallbacks If the ZIP code is unavailable or invalid:
Automatic Recalculation Whenever new contact data is imported or updated (via Excel, LawRuler, SmartAdvocate, or Voice AI List uploads), Kayse automatically re-runs the ZIP โ phone โ country resolution flow and updates the timezone instantly.
Results are cached, so subsequent recalculations are faster.
Manual Overrides Stay Persistent If a user manually sets a timezone in the UI, itโs stored as Manual โ High Confidence and wonโt be changed automatically unless explicitly overridden.
Operational Guidance for Voice AI Campaigns โ Keep ZIP codes complete and accurate (including leading zeros) to maintain high-confidence local times. โ Even when using fallback sources (phone or country), campaigns still respect the 11 AM ET earliest-dial rule to ensure TCPA compliance โ no calls before 8 AM PT.
See all campaigns at a glance:
๐งพ Campaign Details View
๐ง Controls: Pause, Resume, Edit (paused only), Delete (with confirmation).
The interface introduces two distinct tabs for better organization and clarity:
Displays high-level campaign performance statistics such as:
Ideal for monitoring outcomes and overall campaign effectiveness.

Shows a detailed list of all calls made during the campaign.
Includes individual call data such as call status, result, duration, and more.
Use this tab when you need to drill down into call-by-call performance or review specific cases.

Both the Metrics and Calls tabs can be filtered using the call direction filters located in the top right:
โ Note: The selected filter applies independently to both tabs - Metrics and Calls, so the data you view will always reflect the chosen direction context.
Shows how many clients have been contacted, displayed as:
Number of clients actually called/Total number of clients assigned to the campaign
225/ 456Displays the average length of conversations across completed calls.
๐ Note: this metric is based on the volume of converted cases/clients, not the number of calls.
Includes clients with statuses:
SignedQualified โ Intake Completed๐ Note: this metric is based on the volume of DQ cases/clients, not the number of calls.
DQ โ Intake Completed
๐Note: this metric is based on the volume of converted cases/clients, not the number of calls.
The percentage of clients who were marked as converted out of all clients called such as Intake Completed-Qualified or Signed statuses.
Example: If 1 out of 2 clients called were converted, the gauge will show 50% Conversion Rate, and Converted Clients will display
1 / 2.
๐Note: this metric is based on the volume of DQ cases/clients, not the number of calls.
The percentage of clients who were marked as disqualified after completing intake, out of all clients called.
Example: If 1 out of 2 clients called were disqualified, the gauge will show 50% Disqualification Rate, and Disqualified Clients will display
1 / 2.
๐Note: this metric is based on the volume of in-process cases/clients, not the number of calls.
CBNeeded โ Partial Intake or other in-process / chasing statuses - means they didn't complete the intake yet.To export your calls data, go to Calls tab and choose one of the following options:
Export to List โ Create or update case lists
Export to File ๐พ Download CSV




Each row = 1 call with:
* Note: Post-Call Statuses will likely vary across each AI Agent as each use case is unique.

The AI Campaign Detail export improves post-campaign analysis and reporting.
Inside of the Calls screen within each AI campaign, you are able to export the campaign details at any time with the Export to File button as shown here:

These are the available fields in side of the Export to File feature:
๐ ฐ๏ธ No. Weโre importing only the main number for each case due to data quality.
๐ ฐ๏ธ Not yet. Weโre using toll-free numbers due to fewer carrier filters.
๐ ฐ๏ธ Default: 30 seconds | Max: 90 seconds
๐ ฐ๏ธ Yes. For example:
โ Carrier Restrictions
๐ Is there a limit to how many toll-free numbers we can use?
๐ ฐ๏ธ Yes. The wireless carrier ecosystem enforces a limit of 5 toll-free numbers per company.
๐ Is there a limit to how many local numbers we can use?
๐ ฐ๏ธ No. The wireless carrier ecosystem has no current limit for the number of local numbers per company.
Carriers are using AI to label spam-like behavior:
๐ง Pro Tip: Clean lists + Opt-in language = Fewer flags
Weโre here to support you! ๐ฌ
Let us know if you need:
โจ By following this guide, you can confidently launch, manage, and scale your AI Campaigns in Kayse.ai for efficient and intelligent client engagement ๐