Andheri does not keep Bandra’s hours.
A business with more than one place needs more than one set of hours. Branches and departments give an Enterprise workspace a branch for each site and a department for each part of one that shuts at a different time, each with hours of its own, inherited downwards when you leave them blank. The workspace schedule and the booking venues this stands on are live today; hours per branch are in build, and this page says which is which.
One clock for six doors.
A workspace keeps one set of opening hours. That is right for a single shop and wrong for a clinic with an Andheri and a Bandra branch, a showroom whose service desk shuts an hour before the floor, or a chain whose branches keep different Saturday rotas. Two of the three pieces already exist.
One schedule is live today
Settings → Opening hours holds the week, repeating rules such as “2nd and 4th Saturday closed” and particular dates for the whole workspace, and an Auto Flow reads it at the moment it fires. Included on every plan.
Places already exist for bookings
A venue is an address, a voice call, a meeting link or something else — either you publish the details or the customer supplies theirs as they book. When a service is offered more than one way, the booking page asks how they would like to connect before it shows a single time.
What is missing is hours per place
A venue says where. The workspace schedule says when. Nothing today says “when, at this place” — an hour the Bandra branch is shut for is still offered there while the workspace is open. That gap is what branches and departments close.
Two levels, and no org chartIn build
A branch is a site. A department is a part of one that keeps different hours. That is the whole model — deep enough for a service desk inside a showroom, shallow enough that nobody has to draw a tree first. In the console a branch is labelled a Store.
A branch is a site
The Andheri clinic. The Bandra branch. A branch never sits under anything else, and each one carries a name, a handle and, if you give it one, hours of its own.
A department is part of one — or stands alone
The service desk that shuts an hour before the shop floor. A single-site business can add just a department, with no branch invented above it. A department under a department is refused, so the model cannot quietly become a hierarchy.
A handle chosen once
Every branch and department has a short handle for links, set when it is created and never changed afterwards — the same rule services, staff and venues follow. Type one, or leave it blank and it is taken from the name; a handle you typed that is already in use is refused so you can pick another.
Set hours once, let them flow downIn build
You write hours only where they differ. Everything else inherits, and the panel says which schedule it is showing rather than presenting a blank page that looks broken.
Own, then branch, then workspace
A department’s hours are read in that order and the first that exists wins. A department left blank follows its branch; a branch left blank follows the workspace; and the panel reads “inherited from Andheri” so nobody has to guess which.
Silence never closes a door
Hours nobody wrote are no opinion at all, and everything that reads them treats that as open. Clearing a branch’s hours puts it back to inheriting — it never closes it. A schedule that was never written must never start refusing customers.
The same panel, the same rules
A branch’s hours are edited in exactly the panel the workspace already uses — the week, repeating exceptions, particular dates and the live “open now” line — so nothing has to be learnt twice.
A shut hour is simply not offeredIn build
Where a booking venue belongs to a branch or a department, that place's hours bound its diary. Your booking page, WhatsApp, the assistant and the API all keep to them — and one door is deliberately left open.
Not ‘taken’ — shut
Only a time that fits entirely inside the branch’s hours is offered. A time the site is shut for is absent from the diary rather than shown as already taken, because it is not taken — it is shut. Turnaround after an appointment may run past closing; the appointment itself may not, so a 17:45 slot that ends at an 18:00 close is still offered.
Your own counter is exempt
Somebody standing at your desk at 19:30 asking for 20:00 gets it. A booking your team takes in the console is deliberately not held to the hours; the public page, WhatsApp, the assistant and the API are.
When, never where
Attaching a venue to a branch changes only when that venue can be booked. Which places a service is offered at is still what the service says — a booking page never starts or stops offering a location because somebody linked a branch.
An Auto Flow can ask about one branchIn build
The out-of-hours reply you build today asks whether the workspace is open. With branches it can ask about the place the customer is actually writing to.
Name a branch in an opening-hours rule
A Condition step’s opening-hours rule can name one branch or department instead of the whole workspace, read against the clock at the moment the flow fires. Rules you already have keep meaning the workspace, so nothing you built changes under you.
A rule that loses its subject stays open
A rule naming a branch that has since been archived — or one nobody ever gave hours to — falls back to the workspace’s answer, never to “closed”. A rule that has lost its subject must not become a shut door.
Archived, never deletedIn build
A venue may belong to a branch and a booking may name it, so the record has to keep naming the place. A branch is therefore archived rather than removed.
A place is archived, not deleted
An archived branch stops appearing wherever a new one can be picked, and everything that ever named it still names it. A branch cannot be archived while active departments still sit under it — archive or move those first.
An archived branch still honours its hours
Archiving stops a branch being offered, not honoured: a venue attached to it stays bounded by its hours, so a diary never quietly opens up because a place was retired.
Every change on record
Creating, editing or archiving a branch, and every change to its hours, is written to your activity log against that place — the same log that already records the workspace’s own schedule.
On Enterprise and Partner plans — ask us.
Branches and departments are for businesses that run more than one place. They come with the Enterprise and Partner plans, and can be granted to a single workspace by arrangement. Enterprise is quoted after a conversation rather than signed up for on the pricing page.
Included with Enterprise and Partner
The entitlement is a plan one. There is no checkout for it, and no price on this page, because what a multi-site workspace needs is worked out with you rather than picked from a list.
Losing the plan never un-bounds a booking
Moving off the plan stops you creating and editing branches. It hides nothing and un-clamps nothing: hours already written keep resolving, and a venue attached to a branch stays inside them. Offering appointments at a shut branch is a worse outcome than keeping a feature a month too long.
Live today, on every plan
- The workspace opening-hours schedule — the week, repeating rules, holidays.
- The Auto Flow condition that asks whether the workspace is open.
- Appointment venues, including the step that asks a customer how they would like to connect.
In build, and switched on for nobody yet
- Hours for each branch and department, inherited downwards.
- The booking diary following the hours of the place a venue belongs to.
- An opening-hours rule that names one branch instead of the workspace.
- Choosing the branch on the venue form yourself — today we link them for you.
Where it is today. The right-hand column is built and running in our own testing, and it is switched on for no customer workspace. We would rather show you the shape now, and agree what going live looks like for your sites, than describe it as though you could turn it on this afternoon.
The schedule every branch inherits.
The week, the repeating rules and the particular dates a branch falls back to are your workspace’s own opening hours — live today, on every plan.
Tell us how many places you run.
Tell us which sites and departments keep different hours, and where your customers book. We will show you how the branch model fits, what is live today, and what Enterprise costs for a workspace your size.