ElevenLabs automates follow-up calls: customer reports processing 100% of leads

One customer did not pick up. Another asked for a call tomorrow. A third explained that a relative handles the contract. For a sales team, each such conversation creates another task: save the details, choose a time and pick up where the conversation left off. ElevenLabs has introduced ElevenAgents Campaign Manager to handle that sequence. For developers and product managers, it is an opportunity to assess how much outbound campaign logic is now available within the platform.

The team supplies contacts and a desired outcome, such as a confirmed appointment or a qualified lead. According to ElevenLabs, the system automatically arranges follow-ups, carries context between conversations and stops contacting someone once the goal is achieved or they ask not to be called again.

How the agent resumes the conversation

The announcement gives an example of renewing a plan with a telecom provider. On Tuesday, the agent calls a subscriber, but there is no answer. The system schedules another attempt within the permitted calling window. During the next call, the subscriber explains that their daughter manages the family plan. The agent confirms that she is listed on the account, contacts her and continues discussing the renewal.

The value here lies in continuity across actions. A follow-up call needs to account for the previous response, the agreed time and the person who makes the decision. If that information is lost, automation reproduces a familiar call center problem: customers have to explain their situation all over again.

Campaign Manager uses agents and phone numbers already configured in ElevenAgents. Contacts can be uploaded as a CSV file or sent from an in-house system via API. At the time of the announcement, the listed channels include phone calls, voice outreach and WhatsApp messages. Email and SMS are described as future capabilities; it is too early to build current workflows around them.

What the campaign manager can see

Each campaign has a funnel spanning contact creation through to the outcome. Every contact has a decision history showing what the agent did and why. Cases where the system needs help go into a separate queue with the call context attached. Data can be exported to CSV.

For product managers, this makes it possible to analyze drop-offs at each stage. A contact not answering, requesting a rescheduled conversation, reaching a handoff to an employee or opting out of further contact are different outcomes that call for different actions. The contact history helps identify where to change the workflow and where to involve a person.

ElevenLabs cites feedback from AA Ireland chief technology officer Jeremy O'Sullivan: the team previously processed 50–60% of its daily lead list; with Campaign Manager, it processes 100%. This is a customer claim in a vendor publication. It describes coverage of the list, but does not establish that everyone answered, expressed interest in the offer or made a purchase.

The article provides no comparable data on sales conversion, cost per outcome or complaint volumes. The promised impact therefore needs to be tested in a team's own campaign: a processed contact and a paid order remain different metrics.

What to check before launch

Campaign Manager allows teams to set calling hours, the number of attempts and a separate callback limit. Each campaign has a do-not-call list that, according to the company, is updated immediately after someone asks for contact to stop. Required disclosures are configured in the opening of the conversation and in the agent's instructions.

The company also lists real-time checks of agent responses, detection of another automated participant and redaction of sensitive information in transcripts and recordings. The presence of these tools alone does not demonstrate how well they work in a particular campaign. Key pilot checks include whether the agent respects opt-outs, correctly understands callback requests and passes enough context to an employee.

For a team already using ElevenAgents, a practical next step is a limited campaign with a predefined goal. Metrics should include the cost per achieved outcome, attempts per contact and the share of cases requiring a person. Developers need to check contact transfers via API and reconcile final statuses with the CRM: the announcement provides no details of that synchronization. These checks will show how much manual work the product actually removes.