Units: Split your company into geographic departments
Do you run two towns from the same Clientflow account? Units split your company into geographic departments, so each one gets its own calendar, its own routes and its own key figures, without two accounts, two logins and two subscriptions.
What is a unit?
A unit is a geographic department of your company. Every unit has:
- a name: North Jutland, say
- a colour and an icon, which is how you recognise it in the lists
- a priority: a number that decides who wins when two areas overlap
- an area you draw on a map. It's optional, but the area is what places your customers
Once the units are set up, the rest happens by itself:
- Customers are placed in a unit automatically, based on their primary address.
- Workers you place yourself, one unit per worker.
- Route planning solves each department separately, so a job in one department never lands with a worker in the other.
- The department switcher in the sidebar narrows the calendar and the dashboard's key figures to one department at a time.
The feature is called Units in the app. In everyday language a unit is simply a department, and that's how we talk about it here.
Are Units right for you?
Yes, if you run two locations from one account. The classic case is a window cleaner with one crew in Aalborg and one in Aabenraa. Same company, same phone number, same accounts, but two calendars that mustn't be mixed up, and two sets of routes that should never cross the country. That is exactly what Units were built for.
Yes, if you want to measure two areas separately. If you have one crew but two very different service areas (the city core and the outskirts), you can draw them as separate units and see revenue, orders and leads per area instead of as one lump.
No, if you run one crew from one place. Then there's nothing to split, and a department switcher with a single choice is pure noise. The vast majority of Clientflow companies have no units at all, and that's exactly as it should be. You are not missing out by leaving this alone.
Units are not a switch you flip on a whim. You can stop using them again, but it has consequences: customers and open orders lose their department, workers lose their unit, and everything set up per unit stops applying. None of it comes back by itself if you create units again. See the section How to stop using units further down. So think the split through first, and draw two large areas rather than eight small ones.
Setting units up
Note: Only an administrator can create and change units.
Step 1: Create the units
- Go to Settings.
- Pick Units under Company. If you can't see Units, the feature has to be switched on first: go to Features under Settings and switch on Departments.
- Click New unit.
- Fill in Name, choose a Colour and an Icon, and set a Priority.
- Repeat until every one of your departments exists.
Colours the other units already use aren't offered again, so two departments can't end up sharing one colour.
Priority is only a tie-break. As the dialog puts it: "When an address sits inside two units' areas, the lowest number wins." If your areas don't overlap, the number means nothing. You can always reshuffle later with Move up and Move down on each row.
Step 2: Pick the fallback unit
The first unit you create becomes the fallback by itself. That is also true if you have removed all your units and create a new first one. If you want a different unit to catch the customers outside the areas, you move the fallback yourself. If an older setup has no fallback unit, a warning sits on the page:
No unit is marked as the fallback. Customers whose address falls outside every area end up in no unit at all. Pick one unit as the fallback.
To move or set the fallback: find the row and click Make this the fallback unit (the star). The row is tinted and the unit gets the Fallback badge. There is only ever one fallback. Pick a new one and the old one hands the badge over in the same move.
The fallback unit is the one that catches every customer no other area covers. Without it, those customers sit in no department at all.
Step 3: Draw the areas
Click Edit this unit's area (the compass) on a row. The map opens with your own customer addresses as dots, so you can trace the boundary around where your customers actually are.
- Draw the area by clicking. Right-click a vertex to remove it.
- If the department covers several separate zones, draw more than one area for the same unit.
- The neighbouring units' areas are drawn faintly underneath, and a note tells you who wins a shared area.
- Clear area removes the drawing again.
When you save, every customer in the company is re-matched immediately against the new boundaries. There's nothing to do afterwards.
You edit one unit's boundary at a time. To draw two departments, finish the first, close the dialog, and open the next.
Step 4: Put your workers on units
Scroll down to Workers on units. There's one picker per worker, because each worker belongs to one unit at a time. Choose No unit to take someone off again.
It's worth finishing right away: a worker with no unit only receives the jobs that have no department either when routes are planned.
The buttons on each row
| Button | What it does |
|---|---|
| Move up / Move down | Changes the order, and with it the priority that settles overlaps. |
| Edit this unit's area | Opens the map for that one unit. |
| Make this the fallback unit | Makes the unit the one that catches everything outside the areas. If it already is, the button is disabled and reads This unit is already the fallback. |
| Edit unit | Name, colour, icon and priority. |
| Delete unit | Removes the unit. See the limits below. |
How customers are placed
Placement is automatic, and the rule is short:
- Clientflow takes the customer's primary address.
- If the address sits inside a unit's area, the customer gets that unit.
- If it sits inside two areas, the unit with the lowest priority number wins. A customer never ends up in two departments.
- If it sits inside no area (or the address has no coordinates at all, because it was never found on the map), the customer lands in the fallback unit.
- If there is no fallback unit, the customer gets no department.
The fallback unit isn't only a catch-all: if you draw an area for it too, it competes for addresses on exactly the same terms as every other unit.
Placement runs again automatically whenever something could move a customer: when you create a unit, change a priority, save or clear an area, pick a new fallback, delete a unit, and when a customer gets a new primary address.
In the customer list you can see the department in the Unit column and narrow the list with Filter by unit. The fallback unit appears there with (outside every area) after its name, so you can see who isn't inside any drawn area.
An order's department is fixed when the order is created
An order takes its department from the customer the moment it is created, and keeps it.
That means that if you redraw a boundary six months from now, you move customers, not history. Last quarter's completed jobs stay in the department they were carried out in. This is deliberate: otherwise a single correction on the map would rewrite all of your per-department numbers backwards in time.
Orders created before you started using units have no department. That isn't a fault, and they don't disappear. See the next section. Route planning looks up where the customer belongs today when it has to plan a job with no department.
The department switcher in the sidebar
As soon as you have at least one unit, a switcher appears in the sidebar. It shows the department you're looking at right now, or All units when you're seeing the whole company.
The choice is your own. Switching department changes nothing for your colleagues, and your choice follows you to your next login. Field workers never see the switcher; their day plan already shows only their own jobs.
The switcher says what it does, right at the top of the menu:
Choose which unit the calendar and the dashboard's key figures show. The lead figures follow their customer's unit. The contact and worker lists and settings show the whole company.
So the switcher does not decide which settings you see. You choose planning settings per unit on the settings page itself, see the section Planning settings per unit below.
What the switcher does not narrow
Knowing what doesn't happen matters just as much:
- The worker list in the calendar isn't filtered. A worker with no jobs in the selected department stays as an empty row, not because something broke, but because the calendar shows the whole crew.
- The contact and worker lists show the whole company. The customer list has its own Filter by unit, which you control separately.
- The department switcher does not change which settings you see. Under Settings → Planning you have a picker of your own for showing the company's or a unit's settings.
- The MRR chart is always company-wide. That history is stored as one number per day for the whole company and can't be split retroactively. Pick a department and the chart says so on itself.
- The calendar won't stop you dragging a job onto a worker in the other department. The job simply leaves the department you're viewing. It's route planning that keeps the departments apart, not drag and drop.
Rows with no department show up in every department
A job with no department (because it predates your units, or because the customer's address was never found on the map) is shown in every department, never in none.
That's a deliberate call: the alternative is that a real customer visit becomes invisible to the whole company at once, whichever department you look at. If you see a job in the "wrong" department, it's usually an address missing its coordinates.
Route planning per department
When you run units, route planning splits the week and lays one set of routes per department instead of one for the whole company. A job in one department therefore can't land with a worker in the other.
Three things are worth knowing:
- The split is switched on by use, not by setup alone. It only kicks in once at least one worker sits on a unit, or at least one order has a department. With no units, planning runs exactly as before.
- A worker with no unit only gets jobs with no department. This is the most common cause of an unexpectedly empty calendar after rollout. Put every worker on a unit in step 4.
- A department with jobs but no workers gets no routes. Those jobs are left unassigned, because nobody should drive 300 km. That's how it's meant to work, but it's worth knowing before it puzzles you.
Replanning a single day or a single worker doesn't split anything. There's only one worker in play to begin with.
Online booking per department
When you run units, a customer in online booking only sees times from workers in the department that the address they are booking for belongs to. Online booking is part of the Enterprise plan; how to set it up is in Price configuration.
Which department does the customer get?
The address the customer books for is placed by the same rule as customers (see How customers are placed above):
- If the address sits inside a unit's area, that unit is used. If it sits inside two areas, the one with the lowest Priority number wins.
- If it sits outside every area, the fallback unit is used.
- If there is no fallback unit either, the address belongs to no department. Then only times from workers who have no unit are shown.
If the customer reschedules an existing order, the order's department is used. If the order has none, the contact's department is used.
If the customer is tied to a particular worker, times are shown in the order's own department if that worker is there. Otherwise the times follow the worker's department.
What the department controls
- Public holidays. Each department can have its own public holidays. You find them under Settings → Planning in the Public holidays block, where the switch Close public holidays automatically belongs to the department. If the department follows the company, the company's setting is used.
- Replanning after a booking. If the department's Nightly optimization is switched on, only the booked department's week is replanned when a customer books. If the booking is tied to a particular worker or a fixed time, the whole week is replanned.
What does not change
If you have never used units, customers see the same times as before, except for services that require a Competence (see Competences).
A department can only offer times if it has workers. If a department has no workers, customers in it see no times. See also Competences for services that require a particular Competence.
Planning settings per unit
Routes are already laid per department. Each department can also be planned with its own settings, for example a different longest working day or different rules for breaks.
You find this under Settings → Planning. If you have units, a picker, Show settings for, sits at the top with the choices The company and each of your units. That picker applies to this page only. It is not the same as the department switcher in the sidebar.
Follow the company or own settings
When you pick a unit, it is in one of two states:
| Choice | What it means |
|---|---|
| Follows the company | The unit uses the company's planning settings. The cards are read-only, and the page says: "[unit name] uses the company's settings. Choose Own settings to change them for this unit only." |
| Own settings | The unit gets settings of its own, which apply to it alone. They start as a copy of the company's, so nothing changes until you change it yourself. |
To make a unit follow the company again, choose Follows the company. Clientflow asks first: "Make [unit name] follow the company?". The unit's own settings are deleted, and this cannot be undone. If you confirm with Follow the company, the unit uses the company's settings from then on.
When a unit has its own settings, you can borrow a starting point from another unit with Copy from …. Pick the source under Copy from and confirm with Copy. The dialog reminds you that the unit's settings will be overwritten. It needs another unit that has its own settings.
When you are on The company, the page shows the line Units with their own settings, so you can see which units differ.
What can a unit have of its own?
Almost every block on the page can be set per unit, including Rules (for example Longest working day and No break on days under (hours)), Nightly optimization and the priority level. If the unit has Own settings, the cards say that they apply to that unit only. If it follows the company, they say that these are the company's settings, which the unit follows.
Three things always apply to the whole company and cannot be changed under a unit:
- Seasons
- The workers' priority list
- The text for Finishing the day plan
Under a unit they say: "Applies to the whole company. Change it under The company."
Planning rules (Must and Prefer, see Planning rules) can also differ from unit to unit. They need the same plan as usual. A unit's own planning settings in themselves are included on every plan.
Good to know
- If you switch between The company and a unit while you have unsaved changes, Clientflow asks "Discard your changes?". Choose Stay here to save first, or Discard and switch to let them go.
- Route optimization plans each unit with its own settings. A unit that follows the company is planned with the company's.
- Workers and jobs still belong to their unit, as described above. The settings do not change who belongs where.
How to stop using units
You can go back to running without units at any time. An administrator does it under Settings → Units, and how depends on how many units you have.
| Number of units | What to do |
|---|---|
| Three or more | Delete them one at a time with Delete unit on each row. The fallback unit can't be deleted while others exist: first make another unit the fallback with Make this the fallback unit, then delete the old one. |
| Exactly two | The delete buttons on the rows are switched off. Hover over one, or tap it, and the reason appears: "Deleting this unit would leave only one. Use “Remove all units” to stop using units." Click Remove all units at the top of the page and confirm. Both units are removed at once. |
| Exactly one | Delete it with Delete unit. The dialog tells you that you will no longer be using units. |
The Remove all units button appears as soon as you have two units or more, and it always asks first: "Remove all units?". If you are not an administrator, the button is switched off.
What happens when the units are removed:
- Customers and open orders no longer belong to any unit.
- Workers lose their unit.
- Settings and planning rules made for a unit stop applying.
- Completed orders keep their history.
You can create units again at any time. But what hung on the old units doesn't come back by itself: the areas have to be drawn, the workers placed on the units, and the units' settings and rules made again from scratch.
Limits worth knowing
| Limit | What it means in practice |
|---|---|
| No units, or at least two | Exactly one unit exists only right after you create your first. You can't delete your way down to one: from two units the way to zero is Remove all units, and with one unit you can delete it. |
| The fallback unit can't be deleted while other units exist | Make another unit the fallback first, then delete. |
| One worker = one unit | There's no "both". If a worker has to cover both departments, the department-less jobs are the way, or you move them by hand. |
| An order's department is fixed at creation | New boundaries move customers, not completed jobs. |
| The switcher narrows the calendar and the dashboard's key figures | Not the contact and worker lists, not the MRR history, and not the unit you are viewing planning settings for. |
| Only administrators can change units | Everyone else can use the department switcher, but not create, draw or delete. |
If something goes wrong
| What you see | What to do |
|---|---|
| "No unit is marked as the fallback…" | Click Make this the fallback unit on the unit that should catch everything outside the areas. |
| "Deleting this unit would leave only one. Use “Remove all units”…" | With exactly two units you can't delete either one. Click Remove all units at the top of the page to stop using units. |
| "You can't delete the fallback unit while other units exist…" | Make another unit the fallback first. Then the old one can go. |
| A customer sits in the wrong department | Check the customer's primary address. That one, and only that one, decides the department. Fix the address and the customer moves straight away. |
| A customer has no unit at all | Either you have no fallback unit, or the address has no coordinates. Fix the address so it can be found on the map. |
| A worker's calendar is empty after rollout | The worker is most likely still on No unit. Put them on one under Workers on units. |
| A customer sees no times in online booking | Check that there are workers in the department the address belongs to. If the address is in no department, only workers with no unit are shown. If the service requires a Competence, see Competences. |
| The neighbouring areas aren't shown on the map | The dialog said so. You can draw and save anyway. Reload the page if you want them back. |
| The units can't be loaded | Reload the page before creating anything. Otherwise you risk creating a unit you already have. |
Related
- Calendar and route optimization: planning and optimizing the day, department by department.
- Contacts and the customer index: primary addresses, customer data and filters.
- Planning rules: Must and Prefer, also per unit.
- Price configuration: how to set up the services in online booking.
- Competences: which times customers see when a service requires a Competence.