THE DEVELOPER PLATFORM

Your tools. Your logic.
Lacy handles the conversation.

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.

01 / CONVERSATIONEXAMPLE
JD
Jamie DavisIncoming call · illustrative example
↗
02 / YOUR LOGIC⌘
{ }
Your connected tool
RUNNING
● ● ●tool request
↳
TOOL RESPONSE
✓
03 / OUTCOME↗
✓
CONVERSATION → ACTION

Status
Structured result ready for your system
A conversation becomes a completed action.SIMULATED PRODUCT STORY
LESS GLUE CODE. MORE CONTROL.
Mid-call toolsFlow BuilderWebhooksMCP
A PLATFORM TO BUILD ON

Start with the platform.
Make the workflow yours.

Design the conversation and the work around it.
Extend either with your own tools and logic.

DURING THE CALLVisual agent builder

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.

+   ↖   ⌘ CONVERSATION FLOW / EXAMPLE
◉   Greet the caller
◇   Understand the request
◷   Check availability
↗   Human handoff
See the agent builder guide ↗
BEFORE & AFTER THE CALLDrag-and-drop automation

Build the next step.
Keep the work moving.

Enrich an incoming call with customer context. After it ends, use call outcomes to update your CRM or trigger a follow-up.

+   ↖   ⌘ AUTOMATION FLOW / EXAMPLE
01Call ended ✓
02Map call outcome ✓
03Update HubSpot contact ✓
Explore the automation editor ↗
Configure the foundation. Code the custom parts.Visual flows + custom tools + APIs + webhooks + MCP
BUILT AROUND YOUR STACK

The conversation is just
the beginning.

Keep your business logic where it belongs.
Give Lacy the tools to put it to work.

01 / LIVE API ACTIONS

Mid Call Tool

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.

Explore custom tools ↗
“Is there anything open on Friday?”
check_availability()✓
09:0010:3014:00 ✓
“I have 2 PM. Shall I book that for you?”
Illustrative scheduling tool
02 / FLOW BUILDER

Your rules.
A clear next step.

Shape the conversation with the logic your workflow needs.

Explore Flow Builder ↗
Incoming call ↘
What does the caller need?
Book a visit ✓
Talk to a person
You define the path. Lacy follows through.
03 / STRUCTURED CALL DATA

A call ends.
Your data begins.

Define the information you want to capture in a post-call schema.

Explore post call schema ↗
“Friday afternoon works.
It’s for a repair at my home.”
↓ EXTRACT THE DETAILS
{
  "intent": "repair",
  "preferred_day": "Friday",
  "property_type": "home"
}
04 / APIs & WEBHOOKS

Make your systems
part of the conversation.

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 ↗
Lacy.ai
⌘Your applicationRequest received ✓
◫Your CRMRecord updated ✓
↗Your workflowNext step triggered ✓
Illustrative connected workflow
05 / CONNECT A WHOLE TOOLSET

MCP Server

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 ↗
MCPCONNECTED
⌘   search_records◷   check_availability↗   create_booking▤   get_order_status
06 / HUMAN HANDOFF

Some moments
need a person.

Build a path to your team when the conversation calls for a human.

Design your handoff ↗
L
↗
✓ HUMAN HANDOFFConnect the caller to your team.

A designed next step.
A smooth continuation.

YOUR STACK BELONGS HERE

Connected by design.
Flexible by choice.

Use a documented integration or connect your own system.
Know exactly how each connection works.

START WITH ONE USEFUL WORKFLOW

A clear starting point.
Your own implementation.

Three practical paths into Lacy.
Follow the guides, connect your systems, and test.

01 / BOOKING

Turn a call into
an appointment.

Capture the caller’s needs, check your calendar, and confirm a suitable time.

Caller → Availability → Booking
Build a booking workflow ↗
02 / LEAD QUALIFICATION

Give your team
a useful next conversation.

Ask the right questions, capture structured answers, and route the result to your CRM.

Questions → Call data → CRM
Define your lead schema ↗
03 / CUSTOMER SUPPORT

Answer with context.
Know when to hand off.

Look up information in your system and provide a path to a person when needed.

Request → Your tool → Resolution
Connect a support tool ↗

These are implementation starting points, not one-click installations. Flow Builder also supports pre-built flow templates you can customize.

FROM IDEA TO FIRST CALL

Build visually.
Connect your logic.

Start with one useful workflow.
Expand when you’re ready.

YOUR WORKSPACE / EXAMPLE↗
WHY BUILD WITH LACY

A head start on the platform.
Room for your own logic.

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.

01 / CONFIGURE

Start with working building blocks.

Visual agent flows and drag-and-drop automation give you a foundation to configure around your use case.

02 / CUSTOMIZE

Keep your business logic yours.

Connect APIs, webhooks, and MCP tools. Define what the agent can do and where the result goes.

03 / LAUNCH

Build yourself. Or build with us.

Work in the platform yourself, or choose paid implementation and ongoing optimization support from Lacy.

Evaluating Bland, Vapi, or Retell?Explore the platform comparisons
SKIP THE GUESSWORK

Go straight to the source.

BEFORE YOU BUILD

The details developers
want up front.

Practical answers.
Direct links to the documentation.

What can I do for free?

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 ↗

Do I have to build the phone-agent platform from scratch?

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 ↗

Can I use my own APIs and business logic?

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 ↗

How do I authenticate API requests?

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 ↗

Can I connect my existing telephony?

Lacy documents SIP integrations, including Twilio. Compatibility and setup depend on your provider and number configuration. Read the Twilio connection guide ↗

What happens after a call?

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 ↗

How do I approach testing and failures?

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 ↗

Can I control data retention?

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 ↗

What if I have specific scale or deployment requirements?

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 ↗

MAKE SOMETHING THAT ANSWERS BACK

Your next workflow.
One conversation away.

Start building for free ↗

Create an account, build an agent, and design your workflow for free.
Add minute credits when you’re ready to test or run it.

Want to build with our team? Book a demo ↗