Customer Requirements Tool

AI Phone Agent Warm Call Transfer Rules

Tell Lacy.ai when live callers should be transferred, who should receive them, and what details should be shared.

Caller → Team briefing → Connected conversationTM
Caller → Team briefing → Connected conversation
Lacy.ai TM

Live Escalation Workflow

Caller → AI Agent → Supervisor → CRM

The Agent can brief your team, connect the caller, document the outcome, and trigger the right follow-up.

01

Identify the reason

Apply your rules for when a live person should take the call.

02

Brief the recipient

Share the caller’s context before connecting the conversation.

03

Record the outcome

Follow your fallback path when the recipient is unavailable.

Complete the transfer requirements below.

Use this intake tool to document the client, business hours rules, after-hours handling, supervisor briefing language, escalation contacts, and internal routing requirements.

Client Contact Information

Tell us who is completing this form so Lacy.ai can associate the warm transfer requirements with the right company, team, and contact person.

A

First Name

Provide the first name of the person completing this form.

This helps Lacy.ai confirm who submitted the transfer requirements.

B

Last Name

Provide the last name of the person completing this form.

This helps Lacy.ai identify the correct stakeholder for questions or approvals.

C

Company Name

Provide the company name these transfer rules belong to.

This ensures the transfer configuration is associated with the correct client account.

D

Email Address

Provide the best email address for follow-up.

Lacy.ai may use this email if clarification is needed before configuration or testing.

Transfer Setup

Name the transfer rule and identify how Lacy.ai should reach the right person, team, department, or phone system.

1

Transfer Name

Provide a clear internal name for this transfer rule.

Use a short name your team will recognize later. This helps Lacy.ai identify the transfer scenario during configuration and QA.

2

Supervisor Name or Department Name

Provide the person, role, team, or department the AI Agent should transfer the caller to.

Enter the name, role, or department that should receive this type of transfer. Examples include Service Manager, Emergency Dispatch, Sales Department, or Customer Support.

3

Supervisor Phone Number

Provide the number the AI Agent should call when initiating the warm transfer.

This should be the direct phone number, department line, or call queue the AI Agent should dial when the transfer rule is triggered.

4

Custom SIP or Internal Extension

Use this if your team routes calls through an internal phone system, PBX, or call center.

Only complete this field if your team uses a SIP address, PBX extension, internal call queue, or non-standard phone routing path.

5

Outbound Phone Number

Identify the number Lacy.ai should use to place the outbound call.

Enter the Lacy.ai approved outbound number that should be used to dial the supervisor, department, or call queue.

6

Caller ID Shown to Supervisor

Confirm what number the receiving party should see.

Choose what the supervisor or department should see when the AI Agent calls them.

Only complete this field if you selected Custom number above.

7

Hold Music and Volume

Select the caller audio experience while Lacy.ai attempts the transfer. Recommended volume is 40%.

Select what the caller should hear while the AI Agent attempts to reach the supervisor or department.

Enter a value between 0 and 100. Lacy.ai recommends 40%.

Transfer Logic

Define when Lacy.ai should transfer, when it should collect information, and what should happen after hours.

8

When to Transfer

Select common transfer scenarios and add any custom rules.

Select every scenario that should cause the AI Agent to initiate a warm transfer.

Use this box to add company-specific rules, edge cases, or exact language that should trigger a human transfer.

9

Business Hours Transfer Logic

Confirm when warm transfers should be attempted.

Choose whether the AI Agent should transfer calls only during open hours, after hours as well, or follow different rules by scenario.

10

After-Hours Handling

Define what the AI Agent should do if no transfer should happen after hours.

Explain how the caller should be handled when a live transfer is unavailable.

Messages and Briefing Language

Confirm what the AI Agent should say to the caller and to the supervisor.

11

Hold Message

What should the Agent say before placing the caller on hold?

Write the exact sentence the AI Agent should say before placing the caller on hold.

12

Supervisor Summary Instructions

Define what context the Agent should provide before connecting the caller.

Include caller name, reason for calling, urgency, and any details already collected.

13

Briefing Initial Message

The first message the Agent says when the supervisor answers.

Write the first message the AI Agent should say to the supervisor or department before it gives the call summary.

14

Connected Message

The message the Agent says when the supervisor joins the call.

Write the message the AI Agent should say once the supervisor or department is ready to join the live call.

CRM, Notifications, and Follow-Up

Tell Lacy.ai how every transfer attempt should update your CRM and notify your team.

15

CRM and Internal Notification Requirements

Select the system actions that should happen after a transfer is triggered.

Select the CRM updates, tags, records, or notifications that should happen once the AI Agent attempts a transfer.

Add any CRM field names, owner assignment rules, notification recipients, tags, or workflow details.

16

Failed Transfer Handling

What should the Agent do if the supervisor or department does not answer?

Explain how the AI Agent should recover if the transfer fails.

17

Priority or Emergency Transfer Rules

Identify urgent scenarios that need faster handling.

List high-priority scenarios that should follow a different path, trigger faster notification, or route to a specific person or department.

18

Approved Escalation Contacts

List people, departments, phone numbers, and routing logic.

List every person, department, number, or queue that can receive a transfer.

19

Variable Usage

Confirm which fields should appear in messages, summaries, CRM updates, and notifications.

Select the data fields Lacy.ai should use where available.

Explain where each variable should be used.

20

Final Approval

Confirm that the transfer rules above are approved for configuration inside Lacy.ai.

Enter the name of the person approving these transfer requirements.

Select the approval date so the Lacy.ai team knows these requirements are ready for buildout.

Use this space for anything that does not fit above.

Submitting your transfer requirements...

Thank you. We have received your form.

Your warm call transfer requirements have been submitted to the Lacy.ai team. We will use this information to configure, test, and validate your AI Phone Agent transfer workflow.

Return to Lacy.ai
Your next step

Put your call workflow into practice.

Explore the next step for your service business with Lacy.ai.

Book a Free 30-Minute Demo →
Lacy.ai robot with green tie, thick halo and TM