> ## Documentation Index
> Fetch the complete documentation index at: https://docs.comforthub.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Draw a service territory

> Add a territory in Zoho, have a developer draw its map area, and watch properties fall into it

export const Touches = ({systems}) => <p>
    <strong>Systems involved:</strong>{" "}
    {systems.split(",").map((s, i) => <span key={s}>
        {i > 0 ? " · " : ""}
        <a href={"/systems/" + s.trim()}>{s.trim().replace(/-/g, " ")}</a>
      </span>)}
  </p>;

<Touches systems="zoho-crm, supabase-backend" />

A territory is two things: a record in Zoho with a name, a code and an active flag, and a map area that lives only on our side. You create the record; a developer draws the area. From then on every property whose address falls inside the area gets that territory on both sides.

## Before you start

* Zoho open, on **Service Territories**.
* A short code for the territory, in the same shape as the codes already in use.
* The rough map area agreed, so the developer knows what to draw.

## Steps

<Steps>
  <Step title="Create the record">
    In **Service Territories**, click **Create**. Fill in **Name** and **Major Service Area** (the code), tick **Is Active**, tick the **Allowed Time Slots** the territory offers, and save.
  </Step>

  <Step title="Ask for the map area">
    Zoho has no map. Ask a developer to draw the area on our side; that is a database change against the territory's code. Until it is drawn, the territory exists but no property falls into it.
  </Step>

  <Step title="Check a property">
    Add or convert a customer whose address sits inside the area. Open the property in Zoho: **Major Service Area** shows the territory.
  </Step>
</Steps>

## How you know it worked

* The record is on our side within seconds, with name, code and active flag.
* A property created inside the area gets its map position, its Street View picture and the territory within a minute, and Zoho shows the territory on the property.

## Good to know

* The **Allowed Time Slots** you tick in Zoho are the arrival windows the territory offers. Zoho owns them: a tick or a clear made in Zoho reaches our side, and nothing on our side changes them.
* **Is Active** is two-way. Switching it off on either side reaches the other.
* **Supabase Territory Id** stays empty on a territory you create in Zoho until our side first pushes an edit back; then it fills in. The pairing between the two records is kept on our side, not in that field.
* A property only gets its territory when its address can be placed on the map. An address the map does not know keeps no territory and no picture. Fix the address and the property is tried again, and a nightly sweep retries any property still without a picture.
* Two overlapping areas: the property goes to the one whose code sorts first.

## Related

* [What lives where](/handbook/catalog-and-staff/what-lives-where)
* [How a lead becomes a customer](/handbook/new-customers/how-a-lead-becomes-a-customer)
* [Names](/reference/names)