Skip to content
RocketLead Developers

Lead Pools and Calendars

A Lead Pool is a table of customers (leads) for a single Standort. A Calendar is the scheduling surface for that Standort. Both are created independently but are conceptually paired — and they should be linked to the same Standort in Settings → Standorte.

Convention: one pool, one calendar, one Standort

Section titled “Convention: one pool, one calendar, one Standort”

For 99% of orgs, the rule is one Lead Pool and one Calendar per Standort, all sharing the same name and color. This keeps:

  • Lead lists per location easy to read in the table view.
  • Calendar overlays easy to scan when looking at the multi-location view.
  • Automation branching simple — a flow checks the source pool to identify the location.

Cross-pool customers (one person who’s a lead at two locations) come up rarely; when they do, create two leads, not one shared.

Creating a Lead Pool

Section titled “Creating a Lead Pool”

Console → Leads (left nav) → + New Lead Pool → Settings → enter the name.

Out of the box, a new pool ships with a default set of lead-state categories. You can edit them later; for first-time setup, leave the defaults until you have a reason to deviate.

The pool has no fields yet beyond the system-provided ones — you’ll define those via the Ingress webhook bootstrap or by importing data.

Creating a Calendar

Section titled “Creating a Calendar”

Console → Calendar (left nav) → + New Calendar → Settings → enter the name and pick a color.

Use the same color as the Lead Pool. There’s no functional consequence either way, but visual consistency saves the customer time.

A new calendar has no resources or appointment types yet. Those are now defined globally (per org) and then linked into each calendar — see Resources vs. appointment types.

Linking to a Standort

Section titled “Linking to a Standort”

After creating both, go to Settings → Standorte → [your Standort] and tick the Lead Pool and Calendar in the “Linked Pools” / “Linked Calendars” sections. Without this link, $studio.* variables in automations won’t resolve and your emails will go out with empty signature blocks.

What’s next

Section titled “What’s next”