Run Setup — Targeting and Scheduling

The Run Setup card is the most important section on the Email and LinkedIn pages. It answers WHO gets contacted, WHAT gets updated after a send, and WHEN the sends go out.

Target CRM Views

Views are pre-saved lists of leads inside your CRM. Leadmeister fetches leads from whichever views are selected here.

• Tick one or more views.
• If a lead appears in multiple selected views, they're only contacted once per run.
• If no view is selected, Run Once and the scheduler are disabled.

Criteria — narrowing the view

The Criteria builder layers extra filters on top of the selected views. Useful when a view is broad (e.g. "All UK Tech Leads") and you only want a subset.

Structure

• One row per condition: Field, Operator, Value.
• Each row matches a CRM lead field (including custom fields).
• Operators depend on field type: text shows "contains" / "is not", dates show "before" / "after", etc.
• Groups with AND / OR combinators — click + Group for nested logic.

Date offsets ("current date ± N days")

For date fields, the value picker offers:

• Current date — resolves to today at run time.
• Current date ± N days — e.g. today − 30 for "30 days before today". This stays accurate automatically as time passes.
• Specific date — hardcoded YYYY-MM-DD.

Prefer offsets over hardcoded dates for recurring criteria so you never have to edit them.

Example criteria trees

• Inactive leads in Tech: (Industry is Technology OR Industry is SaaS) AND Last_Activity before current date − 30 days.
• New trial users: Pipeline_Stage is Trial AND Created_Time after current date − 7 days.
• Warm inbound, not contacted yet: Lead_Source is Website AND Last_Outreach_Date is empty.

Field Updates After Sending

After every successful send, Leadmeister can update fields on the CRM lead. Up to 10 mappings per run.

Configuring

• Click + Add Field Update.
• Left dropdown: pick a CRM field (custom fields appear at the top).
• Right box: enter the value. For date fields, a date picker with offset modes appears (same as Criteria).

Common patterns

• Pipeline_Stage → "Outreach Engaged" — marks lead as in-flight.
• Last_Outreach_Date → Current date — stamps today's date.
• Follow_Up_Date → Current date + 7 days — schedules a human review in a week.
• Outreach_Channel → "Email" — report on which channel touched which lead.

Schedule

Turns Run Once into recurring automated sends. Configured per-channel (Email and LinkedIn have independent schedules).

Fields

• Enable scheduled runs — master toggle.
• Rate: Send up to N leads per hour / day / week. Most teams start at 20/day.
• Active days — day pills (Mon Tue Wed Thu Fri Sat Sun). Unchecked days = no sends.
• Active window — earliest and latest clock time. 09:00–17:00 is a reasonable B2B default.
• Timezone — IANA timezone the window and active-days are interpreted in.

The safeguard modal

Ticking Enable scheduled runs shows a confirmation modal: exact time of the next run, summary of rate/window/timezone, and a Cancel button. Closing the modal without cancelling is the deliberate "go live" step.

Nothing fires silently. The modal exists specifically to prevent accidents.

Run Once

Fires an immediate one-off run using the full configuration. Ignores the schedule.

• At least one view must be selected.
• Click Run once.
• A confirmation dialog appears listing every lead that would be contacted — first name, last name, title, company. The count at the top reflects the full match count even when the visible list is capped at 200 rows.
• Cancel closes the dialog with nothing queued.
• Continue — contact N leads queues the run and the Dashboard shows live progress (processed / skipped / errored).

The list mirrors the same filters the run will apply: CRM view selection, email-presence (email runs only), and the Criteria tree. What you see is what gets contacted. The list is also restricted to leads owned by you in the CRM — teammates running the same campaign will see their own leads only.

Run Once is the safest way to test changes — use it with a small view (5–10 leads) before scaling up.