OperationsScheduler

City Clusters

If you operate across several nearby towns, a City Cluster groups them into one region in the service scheduler. Instead of jumping between Gdańsk, Gdynia, and Sopot — or Sorrento, Positano, and Amalfi — your coordinators pick one region and see every task in that area together.

Advanced module — City Clusters are part of the operations vertical, available on request. Ask support to enable them for your workspace.

What a cluster does

In the scheduler (Service → Planning, the “Grafik”) every task belongs to a property, and every property has a city. The location picker at the top of the scheduler lets a coordinator filter to one place at a time.

A cluster tells the platform that several cities belong to the same operating region. When you pick that region, the scheduler shows tasks for all of its cities at once — and the picker shows one clean label instead of a long list of towns.

Two kinds of clusters

A cluster is just a label and the cities it covers. How it behaves depends on whether the label is itself one of those cities:

Region — the label is a group name that is not one of the cities. Use this to combine distinct towns into an operating area.
Trójmiasto → Gdańsk, Gdynia, Sopot, Straszyn
Amalfi Coast → Sorrento, Positano, Amalfi, Praiano
Spelling variants — the label is one of the cities, and the rest are alternate spellings of the same place. Use this so differently-written city names all resolve to one location.
Kraków → Kraków, Krakow, Cracow
München → München, Munich

You don't choose the type explicitly — the platform infers it. If the label matches one of the listed cities it's treated as spelling variants; otherwise it's a region.

Why it matters for multi-city operators

A team running a single city rarely needs clusters. But if your portfolio spans a coastline, a metro area, or several countries, clusters keep the scheduler workable:

Coordinators plan and dispatch one region at a time instead of scrolling a mixed list of every town.
A cleaner or driver who covers “the Amalfi Coast” gets one region to work from, matching how your operation is actually run on the ground.
Matching is diacritic- and spelling-insensitive, so “Gdansk” and “Gdańsk” land in the same place.

Setting up clusters

Clusters are configured under Settings → General → City Clusters (Admin only). To add a region:

Click Add cluster.
Give it a label — the name shown in the scheduler's location picker (e.g. Amalfi Coast).
Add the cities it covers, one at a time. Each city name should match how it appears on your properties.
Click Save.

The next time a coordinator opens the scheduler, the new region appears in the location picker and gathers all of its cities' tasks together.

How cities are matched

Clusters match against the city on each property. A city that isn't part of any cluster still works — it simply appears in the picker on its own. Nothing is hidden: clusters only change how cities are grouped and labelled, never which properties or tasks exist.

Start small. Add a region only where you genuinely dispatch across several towns as one area — leave standalone cities alone. You can adjust the clusters any time.

Clusters shape the location picker used throughout the scheduler. For how tasks themselves are created, assigned, and tracked, see Coordination Tasks.