Extensions

Multi-Location Setup

One product serves every branch, each with its own hours, details and contacts, without buying a separate build per site.

When a customer asks about opening hours, they mean the branch near them, not head office. This add-on configures the product you already run for several locations, each with its own hours, address, services and team. Requests are routed to the right branch, while you manage one setup instead of paying for a separate build per site.

Answers with each branch's own hours and services
Routes every request to the right branch team
Keeps one setup for all your locations

$2,500 10–20 working days

Choose delivery and add to cart Ask an expert

Wooden house blocks linked by threads to one brass pin, several branches served by one shared setup.

What it is

Multi-Location Setup is an add-on that configures one Upmark Labs product for several locations or branches. Each location gets its own details, such as hours, address, services and the people who handle its requests, while sharing one setup. Requests are routed to the right branch team.

Why businesses buy it

Multi-site businesses lose customers to small errors: the wrong opening hours, a booking at the wrong branch, a message sent to a central inbox nobody watches. Separate builds per location cost more and drift apart over time. One product configured per location gives every customer accurate local answers while you maintain a single setup. The written scope lists the locations, their details and routing, and tests each one with the parent product before launch.

Problems this solves

One product gives the same hours and address for every branch

Multi-Location Setup gives each location its own details, such as hours, address and services. Customers get the right answer for the branch they actually mean.

Requests reach head office and then need forwarding by hand

Each request is routed to the right branch team, based on the people set for that location. Staff at head office no longer sort and forward messages by hand.

Running a separate setup per branch is hard to keep consistent

All locations share one setup while keeping their own details. Changes that apply everywhere are made once, and the documentation shows where branch details live.

Scope card SKU UPM-A0043

Multi-Location Setup

Everything this build includes, written down before you pay. Choose how you want it, own the code or license it yearly, then the delivery speed and any add-ons.

$2,500 one-time build price

What is included

Channel: As per the parent product
Integrations: As described in the add-on
Knowledge: As per the parent product
Workflows: Configures one product for several locations or branches
Languages: As per the parent product
Testing: Tested together with the parent product
Revisions: 1 round
Handoff: Written handover report
Support: 14 days after launch

A good fit if

You run several branches, clinics, stores or offices under one brand.

Locations differ in hours, services, prices or staff, and customers need the right answer for theirs.

Requests should reach the team at the right branch, not a central inbox.

You run an Upmark Labs product, or are buying one now, and want it to cover every site.

Not the right fit if

Your locations trade under different brands with different voices. Multi-Brand Setup separates brands.

Your branches need a second language, not separate details. Additional Language Pack adds it.

You only need one more calendar connected. Additional Calendar Integration covers a single extra calendar system.

Each location needs a completely different workflow. Each workflow can be added with Additional Workflow.

How it works

Locations are listed. For each one we collect its hours, address, services, prices and contacts.
Location is identified. The product works out which branch a customer means, from what they say, the number they called or the page they are on.
Answers and actions follow the branch. Hours, details and bookings come from that location's settings.
Requests are routed. Handoffs and notifications go to the team at the matching location.
Each location is tested with the parent product, then you review with one revision round and get a written walkthrough.

What you provide within 72 hours

Your portal lists these the moment you order. Delivery starts the working day after everything is in and your access is checked.

The order reference of the product being extended
A list of locations with hours, addresses, services and any price differences
Who handles requests at each location, and how to reach them
Access to any per-location calendars or systems, shared securely as agreed at intake
One person who approves the details for all locations

The 72-hour rule. Send everything on your checklist, including access, within 72 hours of ordering so your build starts on time.

Timeline

Start Location list and contacts received

Week 1 Per-location details checked with you

Week 2 Location settings and routing built

Week 2 Each location tested with the parent product

Week 2 Your review and one revision round

Go-live All locations live, walkthrough recorded

Delivery options, in working days (Monday to Friday) from completed intake. They can extend because of national or public holidays, technical issues outside our control (such as platform outages, third-party changes, account approvals or access delays), or natural disasters and other events beyond our control. If a delay happens, we tell you in writing with a new date.
Option	Delivery time	Price
Standard	10–20 working days	$2,500

What you receive at handover

Your existing product configured for several locations or branches
Branch details such as hours, address, services and contacts set per location
Routing of requests to each branch team
Updated documentation, a test report, a handoff note and a written walkthrough

Expected benefits and how to measure them

Helps customers get branch-specific answers
Can cut time spent forwarding requests between branches
Makes shared changes easier to manage

Misrouted requests: Ask branches to log requests that reached the wrong team, before and after launch.
Wrong-branch answers: Sample conversations monthly and count answers with another branch's details.
Forwarding time: Ask head office to note weekly time spent forwarding requests, before and after.

Before you start: List each branch's details and how requests reach them today. Note how many are forwarded by hand each week.

These are things to track, not promised results. Outcomes depend on your data, your team and your market.

Running costs

Running costs follow volume, not the number of locations. Usage stays billed to your accounts as for the parent product, though a separate phone number or calendar per branch may add its own small fee.

Ask about running costs

Custom requirements

Separate reporting per location, different workflows per branch, or a location count beyond what was agreed at intake can be quoted. Add a note at checkout for a written Change Quote. Larger or bespoke projects go through the Custom AI request form instead.

Request a custom version

Keep it running

Changing a branch's hours or contacts is routine upkeep under the parent product's maintenance, which grows in line with the add-on's price. Opening a new branch may need a separate quote.

Adds $125/mo to maintenance

Covered by the main product's maintenance, which grows by this amount.

How maintenance works

How this compares

	Do it yourself with a SaaS tool	Hire a custom agency	Upmark Labs
Price	Many tools bill per location each month	An agency may quote each site separately	Ours is one fixed price, shown before you buy
Branch details	Often one set of answers for all	Depends on the brief	Ours answers from each location's own hours and services
Routing	A central inbox	Set per project	Ours sends requests to the right branch team

Questions about this product

How does the product know which location a customer means?

From the clues available on that channel. A caller may dial a branch number, a website visitor may be on a branch page, and anyone can simply name the location. If it is still unclear, the product asks. We agree the method for each channel at intake and test every branch.

How many locations can Multi-Location Setup cover?

The locations agreed at intake for your order. There is no published count, because it depends on how different the branches are. Most businesses with a handful of similar sites fit comfortably. A large network with very different branches may need a Change Quote, which you see before work starts.

Can each branch have different prices or services?

Yes. Each location carries its own hours, address, services and prices, so a customer asking about one branch hears that branch's details. Shared information, such as company policies, stays in one place so it is not repeated or contradicted across locations.

Can I add a new location later?

Yes. Updating an existing branch is routine maintenance. Adding a new branch with its own contacts and settings often fits within the monthly change hours of maintenance; a large addition can be quoted separately through a Change Quote. For each new branch, share its hours, address, services and who handles requests there.

Can new locations be added after Multi-Location Setup goes live?

Yes. Changing details for existing branches is routine upkeep under maintenance. Adding a new location beyond those agreed at intake is quoted as a Change Quote before work starts. The setup itself follows the delivery speed chosen for the product, with a fixed price and date shown before you pay.

Do branches need separate phone numbers?

No, but they can have them. One shared number works, with the agent asking or detecting which branch the caller wants. Separate numbers per branch make that identification instant. Any extra numbers are rented in your own telephony account, at that provider's rate.