Calling campaigns and cadences that are ready

Most sales teams know this one. A list of 200 prospects comes out of a trade show or an export. It goes into a spreadsheet with a "called" column and a "notes" column. Two reps split the list in the hallway. Three days later nobody knows who is calling back, which voicemail was already left, or whether that one director was interested or not.

Then comes the follow-up. Someone has a good conversation and promises an email with a price indication. That email gets written on Friday afternoon, or it does not. A LinkedIn request lives on a sticky note. A WhatsApp message goes out from a personal phone and never shows up in the CRM. The call went well. The follow-up was luck.

That is rarely about the people. It is about the lack of one place where the calling and what comes after it sit together. So in Lumo they do. A call campaign is a named group of call tasks that you work through person by person in call mode. A Cadence is the set of steps around those calls: an after-call email, a LinkedIn step, a WhatsApp message or a task, tied to the outcome of the call or running from the start. On screen they live together under Cadence campaigns. A campaign without extra steps is simply a call campaign: calls only.

The idea is the same as in the Lumo launch film. Do you still have to pick it up, or was it already done? With a Cadence the answer is usually that the work around the call was already done. Lumo spreads the call tasks over the days and over your people. After an outcome, Lumo prepares the next step with the text filled in. What does not happen automatically is the conversation itself. A person has it. And most messages are sent by a person too, after one look at the text.

This page walks through setting up a call campaign, how call mode works, what the steps in a Cadence do, and what is deliberately left out. To see how LinkedIn fits in as a channel, read LinkedIn in your outreach. If you care most about bringing in and qualifying new names, start with lead management.

Say a software reseller with eight account managers wants to call 180 customers whose licence renewal is coming up in the next quarter. This is a made up example to show how it works, not a customer case.

The sales lead builds a saved filter in People called "Renewal next quarter". On Cadence campaigns she clicks New campaign and picks the starting point Call, then email. Owners: all eight. Per day: 20. Start: Monday at 09:00. In the instruction she writes three questions every caller asks about usage and seats. Lumo creates 177 call tasks and reports that 3 people were skipped because no phone number is known. Those three get an email later.

The after-call email is already in the sequence. She sets it to Spoken to, zero working days after the call, with the call note in it and a link to the renewal terms. Then she adds two steps. A LinkedIn connection request on Voicemail and No answer, two working days later, as a task. And a task "Call again" five working days from the start, which is skipped on the Reply signal.

Monday at 08:00 Priya opens call mode. Three call tasks are waiting for her. The first person picks up, wants to add seats and asks for a quote. He also wants a short call with the solutions consultant. Priya presses M and puts a 30 minute meeting in the consultant's calendar, with a Meet link. Then she types the note and presses 1, Spoken to. A few minutes later the after-call email sits in the Steps panel with "Thanks for the call just now about the extra seats" in it. Priya reads it, changes one line and sends it.

The second does not pick up. Key 2. On Wednesday a LinkedIn task is on her Today screen with the text and the profile link. The third has left the company. Key 6, Wrong number, and every step for that person stops. On Friday the sales lead sees in the Call campaigns list how many were reached and how many need a call back. No spreadsheet, no sticky notes.

A call task is an activity. So it sits in activities and calendar and on the Today screen. What you note in call mode lands on the timeline of the person and the company.

The people you call often come from lead management or a form on your website. In call mode you open the lead or deal in a side panel. If the call looks like an opportunity, you convert the lead or move the deal from there.

If you call with CloudTalk, every call sits on the same timeline with recording, transcript and summary, and the CloudTalk outcome carries over to the campaign. That is explained on calling with CloudTalk. A meeting you plan in call mode lands in the host's Google Calendar, just like a booking through the meeting scheduler.

If you want rules that go beyond a Cadence, such as creating a deal when someone shows a certain signal, you build them in automations. There you also find the action Add to a Cadence, so an automation can put someone into a running sequence.

If you work with your own AI agents, they can do the whole job through the MCP server. With create_cadence an agent sets up a Cadence, and with add_people_to_cadence it adds up to 5000 people in batches of 100. With get_call_queue it reads the queue, with record_call_outcome it logs an outcome and with replace_call_campaign_steps it changes the steps. Signals go in through record_person_signal or the API. Steps that send automatically need an explicit confirmation in create_cadence. How agents work in Lumo is on headless CRM and AI agents.

For mailings to large groups you use email campaigns. A Cadence is for personal follow-up around a call, not for a newsletter.