Oblyss Logo
Sign In
Get Started
Oblyss Logo
Get Free Trial
Sign in
Locations + Product Catalog

Two branches. One platform. Zero crossed wires.

The Nashville crew should not show up on the Memphis board. The Dallas office should not fight the Denver office over a shared calendar login. When you run more than one location, the software has to keep them separate where it matters and together where it counts.
See it across branches
How it works
Per-branch calendars and timezones. Branch filters on the map and reports.

Dispatcher map · branch filter

Nashville only
Nashville 4 techs on route
9 jobs
Memphis 3 techs on route
6 jobs
Dallas 5 techs on route
11 jobs
The multi-branch mess

Most software was built for one office. You outgrew that a while ago.

You opened the second location because the first one worked. Then the trouble started. Two offices sharing one calendar account, so appointments land on the wrong screen. A scheduler in Nashville booking a tech who is actually assigned to Memphis. An owner trying to read the numbers and having no idea which branch is carrying the month and which one is quietly bleeding.

Foundation repair adds a wrinkle a lot of trades do not have: you cross state lines. Tennessee has its own rules about deposits and draw schedules. Texas is different again. If your software treats every job the same regardless of where the house sits, someone is fixing payment schedules by hand and hoping they got it right.

Timezones do it too. An eight in the morning appointment in Denver is not eight in the morning to a scheduler looking at a board set to Central. Miss that by an hour and a crew rolls up to an empty house.

What separate should mean

Each branch has its own address, its own timezone, and its own calendar, so appointments land where they belong and show at the right local time. The dispatcher map and the reports filter down to one branch when you want to run that office, and roll up to the whole company when you want the full picture.
How multi-location works

Set each branch up once. It behaves like its own office after that.

You are not spinning up a separate account per location and logging in and out all day. It is one platform, with each branch configured so the software knows where a job lives and which office owns it.

Every branch, set up as itself

Add each office with its address and timezone in the locations manager. From that point on, the platform knows a Denver job runs on Mountain time and a Memphis job runs on Central, so the calendar shows every appointment at the right local hour instead of forcing one clock on the whole company. Schedulers can add and edit branches themselves as you grow.
  • Address and timezone per branch, so the calendar is timezone-aware and "today" is the branch's today.
  • Its own calendar connected per office, so branches stop fighting over one shared login.
  • Locations management where schedulers add and edit offices as the company expands.

Locations

Nashville, TN Central
calendar linked
Memphis, TN Central
calendar linked
Dallas, TX Central
calendar linked
Denver, CO Mountain
calendar linked

Its own calendar, not a shared inbox

This is the one that quietly wrecks a growing company. Two offices on one calendar account means appointments blur together and someone is always double-booked. In Oblyss, each branch connects its own office calendar, so a booking made in Dallas syncs to the Dallas calendar and nowhere else. The offices stop stepping on each other.

Homeowners still get a confirmation when their appointment is booked, and the scheduler still runs the day from the drag-and-drop board. It is the same scheduling and dispatch workflow, just scoped so each office sees its own work first.

  • Per-location calendars so a branch's appointments sync to that office, not a shared one.
  • Automatic homeowner confirmations on booking, per branch.
  • One scheduling board that can focus on a single office or show them all.

Booking · routed to branch

New appointment booked Dallas office
Synced to Dallas calendar
Homeowner confirmation Sent
Shown on Nashville board No
Zoom in or zoom out

Run one branch this morning. Read the whole company this afternoon.

An owner needs both views. The office manager in Memphis only wants Memphis. You at the top want to know which branch is winning and which one needs a look. Filters give you both without exporting a thing.

Under all of it, every branch still shares one connected job record, one supplier catalog, and one set of customers, so a homeowner who called the Nashville office and later books with Memphis is not two different people in two different systems. It is one company that happens to run from more than one address. See how that connected record holds it together.

Dispatcher map

Filter to one branch

The live map shows real-time technician locations and appointment pins. Filter it to a single office and you are running that branch's day: who is on route, who is running late, who is closest to the next call.

Reporting

Branch-level numbers

Filter reports by location to see revenue, pipeline health, and field performance for one office, or roll them up for the company. You can finally tell which branch is carrying the month. See the full reporting suite.

Per-state schedules

Draws that match the state

Set per-state payment schedule overrides so a job in Tennessee bills on its rules and a job in Texas bills on its own, applied automatically by the property state. No fixing draws by hand.

More offices means more people. Not more people in your financials.

A second branch usually means a second scheduler, another CSR, a handful of new techs. Role-based access keeps each of them in their lane. A scheduler runs the board without landing in your profit reports. A CSR manages homeowner communication without seeing revenue. A tech sees only their own assigned jobs, not the whole company’s work.

That matters more as you grow, not less. The bigger the operation, the more it helps that a new hire in a new city sees exactly what their job needs and nothing that invites a mistake or an awkward conversation.

Built to scale past two

This is not a two-office trick. Add Denver, add Tampa, add the next market. Each branch gets its address, timezone, calendar, and its slice of the reporting, while owners keep the one company-wide view that tells them where to put attention next. Bring your branch map to a demo and we will set it up against your real footprint.
Book a demo
The questions multi-branch owners ask

Frequently asked questions

Do I need a separate account for each location?
No. It is one platform. You add each branch as a location with its own address and timezone, and the software scopes calendars, the dispatcher map, and reporting by branch. Your team logs into one account and works the office they belong to.
Yes, and this is the point. Each branch connects its own office calendar, so a booking made at one location syncs to that location’s calendar instead of a single shared account. No more two offices colliding on one login.
Each location carries its own timezone, and the calendar is timezone-aware. An appointment in a Mountain-time branch shows at its correct local hour, and each branch’s “today” is its own day, so a scheduler looking across offices is not off by an hour.
Yes. The live map shows real-time technician locations and appointment pins, and a branch filter narrows it to a single office. Run one location’s day on its own, or clear the filter to watch the whole company at once.
Yes. Filter reporting by location to see revenue, pipeline health, and field performance for a single branch, or roll it up company-wide. That is how you tell which office is carrying the month and which one needs attention, without building a spreadsheet.
Yes. Set per-state payment schedule overrides and the right draw schedule applies automatically based on the property’s state, so a Tennessee job and a Texas job each bill on their own terms. See payments and milestone billing for the detail.
Shared where it should be. Every branch works from one connected job record, one customer database, and one supplier catalog, so a homeowner is not duplicated across offices. What is scoped per branch is the operational layer: calendars, the map view, and the reporting filters.
Multi-location capabilities are part of the platform rather than a bolt-on, and the right plan for a multi-branch operation depends on your team size and the tools you need. Bring your branch count and headcount to a demo and we will point you to the plan that fits.

Run every branch from one place, without them colliding.

Book a 30-minute demo, bring your branch map, and watch each office get its own calendar, its own map view, and its own numbers on a single platform.
See it across branches
Start a free trial