Before you begin
You should have:- a clear use case for your first agent
- one small group of teammates who will test it
- the business rules the agent must follow
- access to the systems the agent may need to reference or update
Recommended rollout path
Create your workspace
Set up a workspace for the team that owns the calls. Keep the pilot small at first so feedback stays fast and clear.
Define one job for your first agent
Pick a narrow use case such as front-desk coverage, booking requests, or lead qualification. Avoid trying to solve every call type with the first version.
Write the agent's role in plain language
Describe what the agent should help callers accomplish, what information it must collect, and when it should hand off to a human.
Connect the actions the agent needs
Give the agent access only to the actions required for the job. Start small. You can add more capabilities once the core flow works reliably.
Set up phone coverage
Connect or assign the phone numbers the agent should answer from or call from. Confirm whether you want inbound, outbound, or both.
Test with real call scenarios
Run through the most common customer conversations, including edge cases such as missing information, unclear requests, and handoff situations.
Good first goals
Your first rollout is usually successful when:- callers can reach the agent on the right number
- the agent handles the main call path clearly
- the agent captures the information your team actually needs
- the connected actions work consistently
- your team can review call outcomes and improve from them
Avoid this in the first version
- too many use cases in one agent
- broad action access without clear guardrails
- trying to automate rare edge cases before common calls work well
- rolling out to every team or number at once
Next steps
- Read Key concepts
- Read Conversation styles
- Read Phone numbers and routing