Build the conversation.
See every branch.
Drag and drop conversation nodes, define decisions, and connect actions. Start with a flow template or design your own.
Build AI phone agents that use your APIs during calls
and send structured results to your systems afterward.
Free to build. Minute credits required to test or run an agent.
Design the conversation and the work around it.
Extend either with your own tools and logic.
Drag and drop conversation nodes, define decisions, and connect actions. Start with a flow template or design your own.
Enrich an incoming call with customer context. After it ends, use call outcomes to update your CRM or trigger a follow-up.
Keep your business logic where it belongs.
Give Lacy the tools to put it to work.
Your API. Part of the conversation.
Look up availability, retrieve records, or trigger an action while the caller is still on the line. Configure your endpoint, HTTP method, headers, parameters, and timeout.
Order-status example: Collect the order reference, call GET /orders/{order_id}, and explain the returned delivery status. Or check appointment availability, as shown here.
check_availability()✓Shape the conversation with the logic your workflow needs.
Explore Flow Builder ↗Define the information you want to capture in a post-call schema.
Explore post call schema ↗{
"intent": "repair",
"preferred_day": "Friday",
"property_type": "home"
}Connect compatible, reachable HTTP endpoints using GET, POST, PUT, PATCH, or DELETE and the authentication your API requires. For multi-step logic, call a Lacy automation webhook, combine requests, and return the result during the conversation. Your integrations still need configuration and testing.
Explore APIs and webhooks ↗
One connection. Multiple actions.
Connect a compatible remote server you build and host, or an existing one. Lacy discovers its tools; you choose which to expose and assign to your assistants.
Support example: Your server exposes lookup_customer, get_order_status, and create_support_ticket. The agent checks the order and opens a ticket when needed.
Supports Streamable HTTP or SSE with static authentication headers. Interactive OAuth login is not supported for these agent connections.
Explore MCP servers ↗Build a path to your team when the conversation calls for a human.
Design your handoff ↗A designed next step.
A smooth continuation.
Use a documented integration or connect your own system.
Know exactly how each connection works.
Check availability and book appointments during calls.
Setup guideHAUTOMATION INTEGRATIONUse call outcomes to create or update contact records.
Automation guide••Connect your telephony setup using the documented SIP configuration.
Connection guide{ }CUSTOM API CONNECTIONConnect your CRM, backend, or workflow through APIs and webhooks.
Developer guideThree practical paths into Lacy.
Follow the guides, connect your systems, and test.
Capture the caller’s needs, check your calendar, and confirm a suitable time.
Ask the right questions, capture structured answers, and route the result to your CRM.
Look up information in your system and provide a path to a person when needed.
These are implementation starting points, not one-click installations. Flow Builder also supports pre-built flow templates you can customize.
Start with one useful workflow.
Expand when you’re ready.
Build the agent, automate the follow-through, and connect your systems in Lacy. Start visually. Extend with code. Get implementation help when you want it.
Visual agent flows and drag-and-drop automation give you a foundation to configure around your use case.
Connect APIs, webhooks, and MCP tools. Define what the agent can do and where the result goes.
Work in the platform yourself, or choose paid implementation and ongoing optimization support from Lacy.
Practical answers.
Direct links to the documentation.
Create an account, build an agent, and design workflows for free. To activate an agent or flow for testing or production, purchase minute credits. View pricing ↗
No. Configure your agent and conversation in Lacy, then connect the tools your use case needs. Use the visual Flow Builder, start from a flow template, or work with prompts. Your own integrations still need configuration and testing. See the builder ↗
Yes. Custom mid-call tools let the agent call your systems during a conversation. APIs, webhooks, and MCP connections provide other ways to connect your software. You define the tool inputs and the behavior your workflow needs. Read the custom tools guide ↗
Create an API key in your Lacy account and send it in the Authorization header as a Bearer token. Keep the key on your server rather than in browser code. Authentication reference ↗
Lacy documents SIP integrations, including Twilio. Compatibility and setup depend on your provider and number configuration. Read the Twilio connection guide ↗
Define a post-call schema for the fields you want to capture, then use an automation to send the outcome to another system or trigger the next action. Explore post call schema ↗
Test the full path, including tool responses and unavailable services. Define when to offer a callback or route to a person, and confirm a booking only after your connected system reports success. Add minute credits before testing an active agent. Design the conversation paths ↗
Account settings let you configure retention periods separately for calls, leads, chat history, and SMS. Review the documented settings against your requirements. Data retention guide ↗
Discuss your expected call volume, concurrency, countries, and integration requirements with the Lacy team before deployment. Confirm the limits and commercial terms for your intended workload. Talk through your requirements ↗
Create an account, build an agent, and design your workflow for free.
Add minute credits when you’re ready to test or run it.