echowin opens outbound calling campaigns to its API and MCP server
BOULDER, Colo., November 3, 2026. echowin today announced that outbound calling campaigns are available through its public API and its hosted MCP server, so builders can have their voice agent call a list of people straight from their own workflows or from coding agents such as Claude Code and Cursor. Until now, most campaigns were set up by hand in the echowin dashboard. Now a form submission, a CRM stage change or a single prompt can hand the next call to the agent.
What builders can do with it
A campaign has four parts: the agent that makes the calls, instructions for what the calls are for, a list of people to call, and the hours the agent may call them. Through the API, a builder can:
- Create a campaign with an agent, instructions and calling hours, and include the first contacts in the same request.
- Add people in batches of up to 100, up to 5,000 per campaign. Each person can carry a name and custom details, such as a quote amount or an appointment time, and the agent sees them on the call. Invalid, duplicate and do-not-call numbers are skipped and reported back.
- Start or pause a campaign, and see each person's status and, when a call didn't go through, the reason.
The same steps work from any MCP client. A builder connects Claude Code, Cursor or another client to the echowin MCP server with an API key, then asks it to set up a campaign or to call one person. The two steps that place a real call are flagged as destructive, so clients that respect the flag ask before dialing.
How the calls run
The agent calls one person at a time, from its own phone number, and only inside the campaign's calling hours. Those default to 9 a.m. to 8 p.m., Monday to Saturday, in the agent's time zone. Before each call, the agent gets the campaign instructions plus that person's name and details, so it can open with the reason they asked to hear back. Each call shows up in the dashboard with its transcript, and the agent's post-call workflows run as they do on inbound calls. If a person asks not to be called again, echowin marks them do-not-call so later campaigns skip them.
There is no "dial this number" shortcut. Every outbound call comes from a campaign, and calling one person creates a one-person campaign. That way every call starts with instructions.
Built for calls people asked for
Outbound campaigns fit callbacks, appointment confirmations and follow-ups with people who gave their number and asked to hear back. In the US, the FCC treats AI-generated voices as artificial voices under the Telephone Consumer Protection Act, so callers need prior consent. Our guide to AI outbound calling covers the rules, the costs and a full build.
"For most builders, the call isn't where the workflow starts," said Kaushal Subedi, CEO and co-founder of echowin. "A form comes in, a deal moves stage, a part arrives, and that's the moment someone should get a call. With campaigns in the API and the MCP server, the workflow you already run can hand that call to your agent."
Availability and pricing
Outbound campaigns are available through the API and MCP server today. Outbound calling is turned on per team, and any team can ask for it through support. Building and testing an agent is free. Outbound calls are $0.20 per minute on every plan, and each phone number is $10 per month. echo.win/pricing has the full price list. Setup for Claude Code, Cursor and other MCP clients is on the AI integration page.
About echowin
echowin is a platform for building AI phone and conversation agents. Builder-operators configure their agent's instructions, knowledge, tools and workflows, and deploy it on phone, SMS, chat and other channels, while echowin runs the speech, model and telephony layers underneath. Building is free. For more information, visit echo.win.
Media contact: press@echo.win
