Automated Sales Follow-Up: Run a Routine Over a List
Set up automated follow-up for a list of contacts: build the nodes yourself or let Relationship Assist pace each person, set a goal, check the first drafts and approve what Lumo writes.
- Access
- Permission to create Routines, because a Routine over a list reaches people.
- Lumo
- Drafts, Relationship Assist and Lumo review need a plan with Lumo. Building the nodes yourself works on every plan.
- Credits
- Drafting, Lumo review and reasoning nodes use workspace Lumo credits.
- Where
- Routines
What automated follow-up does
A Routine that starts over a list works through each person on that list, over days or weeks, until they reach the goal you set: a reply, a booked meeting, or simply staying in touch. Lumo writes each message from what your CRM knows about the person, and the draft waits in the Feed for your approval. An admin can allow automatic sending in Lumo settings.
It is a Routine like any other: same Routines page, same History, same nodes. Only the Start is a list. For Routines that start on an event or a schedule, see Routines.
Before you begin
- A list of the people to follow up with. See Lists.
- A connected mailbox that can send, if the Routine sends email. Turning it on says so when one is missing.
- The browser extension, if the Routine uses LinkedIn.
Create a Routine over a list
Open New Routine
Go to Routines and click New Routine.
Pick how to start
Pick Blank and choose Over a list on the Start, pick a template under Work through a list, or pick Create with Lumo and describe who to reach and why.
Choose how it works
The Routine asks How should this Routine work?
| Choice | What it does | Steps that follow |
|---|---|---|
| Build the nodes | You place the messages, waits and conditions. Every person goes through the same nodes. | Nodes, Goal, Review + launch |
| Relationship Assist | Lumo paces each person toward the goal from your approach, instead of fixed nodes. | Audience, Strategy, Goal, Plan, Lumo review, Review + launch (plus Ties for keep-in-touch goals) |
Launch
Click Launch Routine, then Review and start, which checks each person on the list before anyone is contacted.
How each person moves through it
- A message node writes to the person. The draft waits in the Feed until someone approves it, unless review is off for that node.
- A Wait node can wait a set time, or until the person replies or opens, up to a limit, then takes the matching path.
- A person stops when they meet the goal, leave the list, or reach the follow-up limit or the inactivity freeze in Configuration. A reply also stops proactive follow-ups for that person.
- Suppression, do-not-contact and pacing per mailbox apply to every send, whichever Routine it comes from.
Write the approach
With Relationship Assist, the Plan step holds the approach Lumo drafts from: plain text in sections headed like == SITUATION ==. Five sections are standard:
| Section | What to put in it |
|---|---|
| SITUATION | Who the contacts are, how they were sourced, what has happened so far. |
| APPROACH | The angle and framing, and how to behave once a contact replies or objects. |
| CHANNEL | Email vs LinkedIn posture: which leads and when to switch. |
| PRIORITIZATION | Observable signals that mark a contact for extra attention. |
| CONSTRAINTS | Hard content rules every draft must respect. |
== SITUATION == Heads of sales at Nordic SaaS companies, 50 to 500 staff. Joined our webinar on pipeline reviews last week. Most have not replied yet. == APPROACH == Peer to peer. Lead with one useful idea for their team, not our product. If they reply with a question, answer it before asking for a call. == CHANNEL == Open on LinkedIn. Switch to email once they have replied once. == PRIORITIZATION == Move faster for anyone who viewed the pricing page this week. == CONSTRAINTS == No discounts. No more than 90 words per message.
- Name what to avoid as clearly as what to do.
- Keep one approach per Routine. Make a second Routine for a second approach.
- Change the text when drafts miss. Then re-draft waiting cards from the Feed.
Add more lists
Open the list, then its ... menu at the top right, and choose Link Routine. The picker offers the Routines the list is not in yet. A static list can be in any number of Routines, and a person can be in more than one.
The Routine page
Click a Routine on the Routines page to open it.
| Tab | What it holds |
|---|---|
| Overview | Where people are, by node or by milestone, who can be reached, and how recently each was touched. |
| Goal & Trajectory | What done means for a person, checked from CRM data, and how people are moving toward it. |
| Details | The nodes, when the Routine has them. |
| Configuration | Whether it runs, and how it reaches, paces and drafts. |
| Associated Lists | The lists this Routine works through, and each person on them. |
Configuration
Open the Routine, then Configuration. Which sections show depends on how the Routine works. Hover any setting in the app for what it does.
| Section | Settings |
|---|---|
| Reach | View profile before connecting, View profile before sending message. Not shown when you build the nodes: each node sets its own channel. |
| Email readiness | Whether a mailbox can send for this Routine. |
| Rhythm | End Routine, Follow-ups before it ends, Max daily follow-ups. Not shown for Relationship Assist or built nodes. |
| Follow-up result, or Lumo defaults | Opens conversations, Tone, Draft in, Voice. |
| Signals | Activity monitoring, Fetch recent posts on connect, Keep posts fresh, Meeting reminders. |
| Shared limits | Max daily follow-ups, for a Routine that builds its nodes. |
Check the first drafts
A new Routine writes a few sample drafts first and holds the rest. Until you release them, the warnings bar at the top of the Feed shows a calibration icon. Hover it to see which Routine is waiting.
1 warning
Read the samples. If they are right, click Draft the rest in that warning. If not, change the approach first.
Limits
- A Routine with LinkedIn message nodes can include up to 100 people.
- LinkedIn actions are done by you through the browser extension, then confirmed.
- Activity monitoring counts people across every Routine that has it on. Above 200, each one is checked less often.
- Lumenbase does not buy or bundle contact lists. Bring your own, or connect a provider.
Troubleshooting
No drafts arrive
Check that the Routine is on, that the people are not already done on Goal & Trajectory, and that the Feed is not holding drafts for the first-drafts check.
Turn on says to finish email setup
No mailbox can send for this Routine. Connect or resume one, then turn it on again.
Link Routine is missing on a list
The list is dynamic, or your role cannot edit it. Link a static list, or ask someone who can edit it.
The Feed says a Routine may be miscalibrated
Lumo paused it because its drafts kept being changed. Click Review, edit the approach, then Save & resume.
Quick reference
- Open Routines
- Routines
- Create one
- RoutinesNew Routine
- Add a list
- List page...Link Routine
- Settings
- RoutineConfiguration
- Set the goal
- RoutineGoal & Trajectory
- See the drafts
- Feed
Frequently asked questions
How do I follow up automatically with a list of contacts?
Create a Routine that starts over that list: open Routines, click New Routine, pick Blank and choose Over a list, or pick a template under Work through a list. Each person on the list then gets the Routine's nodes in turn, and the drafts wait in the Feed for your approval.
What is Relationship Assist?
A way to run a Routine over a list where Lumo paces each person for you instead of following fixed nodes. You set the goal and the approach; Lumo decides when to reach out and drafts each message for approval.
Can one list be in more than one Routine?
Yes. A list can be linked to several Routines, and a person can be in more than one. Pacing per mailbox, suppression and review still apply to every send.
When does a Routine stop following up with someone?
When they meet the Routine's goal, such as a reply or a booked meeting, when they leave the list, or when the follow-up limit or inactivity freeze in Configuration is reached. A reply also stops proactive follow-ups for that person.
Was this article helpful?
