Standorte — the central glue

A Standort (location) is the primary organizational unit above Lead Pools and Calendars. It holds the location’s address, phone, email, and website, and it’s the join key that lets a Lead Pool know which Calendars belong to it (and vice versa).

This article is short on purpose, but the concept matters: Standorte are what makes location-aware automations possible without a single if/else chain.

Why Standorte exist

Before Standorte, a multi-location org had to encode “which location is this lead from” in branching logic inside every automation. Sending a confirmation email? You’d branch on the Lead Pool name to pick the right reply-to address and phone number. Adding a fourth location later meant editing every flow.

With Standorte, you instead:

1. Define each location once, with its address, phone, email, and website.
2. Map each Lead Pool and each Calendar to its Standort.
3. Reference $studio.phone, $studio.email, $studio.address etc. in automation templates.

At runtime, RocketLead resolves the correct Studio variables based on which Standort the triggering lead or booking belongs to. One automation, N locations.

How to set one up

Console → Settings → Standorte → New Standort. The fields:

Field	Required	Format
Name	yes	The customer-facing location name (e.g. “Studio Nord”)
Address	yes	Street + house number
Zip	yes	Postal code
City	yes	City name
Country	yes	Country (typically Deutschland)
Timezone	yes	IANA tz database name; defaults to Europe/Berlin
Phone	optional	+49<digits> with no spaces — see Phone & website formatting
Email	optional	Whatever the customer wants as their reply-to
Website	optional	With https:// prefix
Description	optional	Free-form internal notes
Linked Lead Pools	—	Pick the pool(s) for this location
Linked Calendars	—	Pick the calendar(s) for this location

The “Linked Lead Pools” and “Linked Calendars” fields are the join — they’re what populates $studio.* in automations triggered by leads or bookings under those pools/calendars.

Conventions

• One Standort per physical location. Don’t combine two locations into one Standort even if they share a phone number; you lose dynamic targeting.
• Same name across Standort, Lead Pool, and Calendar for a given location. Easier visual mapping, easier handoff to colleagues.
• Same color across the linked Lead Pool and Calendar — calendar views look noticeably better.

Future direction

The onboarding flow will eventually create Standorte (and their attached Pools + Calendars) from a single multi-step form. For now, manual creation per location is the path.

What’s next

You’re now ready to create the Lead Pool and Calendar for each location.