Zones

Group your team by zone, with its area, service days and hours and a per-slot limit, and let each task find its own zone.

Updated:

A zone is a group of people with an area and service days and hours. It works for deliveries, technical visits, routes or any job done at the customer's address: for example, the North Zone serves Tuesdays and Thursdays and the South Zone, Wednesdays and Fridays.

Create a zone

In Team and resources, open the Zones tab and tap New zone. Each zone has:

  • Name.
  • Area: neighborhoods, cities or postal codes, as tags. A postal code matches by prefix: 20 covers every code that starts with 20.
  • People: the ones who serve the zone. A person can belong to several zones.
  • Days and hours: for example Tuesday and Thursday from 9 to 6. If you leave it empty, the zone does not restrict days.
  • Per-slot limit (optional): the maximum number of tasks that fit in each time slot of the zone.

You can also ask Wagy: "North Zone, Tuesday and Thursday, Camila and Diego". Wagy builds the plan, you review the change and confirm it.

How the zone is assigned

Each task with an address finds its zone by itself, comparing postal code, neighborhood and city while ignoring accents and capital letters. When several match, the postal code wins, then the neighborhood, then the city. If none match, the task is left without a zone and shows up in Today → Needs your attention; fixing the address assigns it automatically.

In Work you can filter by zone or see only what has no zone, and on the map each task shows its zone.

Times and the bot

When a delivery or visit has a time, only the zone's days and hours are offered, crossed with the availability of its people and the per-slot limit. The bot asks the customer for their neighborhood, city or postal code and says, for example: "For your zone (North Zone) we serve Tuesday or Thursday".

Unclaimed tasks

An unclaimed task in a zone is announced, and offered for Take, only to the people in that zone. Owners and managers see them all and can assign them to anyone.

The "zone" used to be a resource with capacity. Those resources keep working; the migration command converts them into zones without losing any task.