Run Every Location As Its Own Business — From One Platform
Each location with its own staff, services, pricing, AI personality, and SMS number. One dashboard for cross-location reporting. True multi-tenancy via Postgres row-level security.
Local Autonomy. Corporate Visibility.
Each location runs how it needs to run. Corporate sees the whole picture without flying between cities. Customers feel the local touch. The database enforces every boundary.
Per-Location Everything
Staff, services, pricing, AI personality, and phone number — all configurable per location. Each location runs like its own business.
Cross-Location Reporting
Drill from company down to location down to person. Revenue, bookings, and staff utilization side-by-side. Export per location or company-wide.
Location-Branded Comms
Per-location phone number, per-location AI receptionist, per-location email sender. Customers reach the location they care about.
True Multi-Tenancy
Postgres row-level security enforces location boundaries at the database layer — not in app code. The architectural difference matters at scale.
Every Location Runs As Its Own Business
Your downtown salon, your suburban spa, and your airport kiosk don't run identical services at identical prices with identical staff. Each location gets its own settings — but they all roll up to one dashboard.
Staff + Technicians Per Location
Staff are scoped to their location by default. Multi-location staff get cross-location access where needed. Schedules, payouts, and commissions roll up correctly.
- Location-scoped staff rosters
- Multi-location staff with cross-site permissions
- Per-location schedules and shift management
- Per-location commission and payout rules
- Per-location specialties and certifications
- Audit log of cross-location access events
Services + Pricing Per Location
Same haircut, different city, different price. Each location sets its own service menu and pricing without forking the platform.
- Per-location service catalog with shared parent definitions
- Per-location pricing overrides on a shared service template
- Per-location service add-ons and combos
- Per-location duration overrides (e.g. longer at the flagship)
- Per-location tax rates baked into checkout
- Bulk-edit pricing across locations when needed
AI Personality Per Location
Each location's AI receptionist has its own name, voice, tone, and prompt set. The customer never feels routed to a corporate phone tree.
- Per-location AI agent name and voice selection
- Per-location persona and tone instructions
- Per-location service catalog and pricing in the AI's context
- Per-location greeting and after-hours behavior
- Per-location handoff rules to staff
- Shared knowledge base with per-location overrides
SMS + WhatsApp Numbers Per Location
Each location owns its inbound phone, SMS, and WhatsApp numbers. Outbound communications go from the right local number — not corporate.
- Per-location inbound phone numbers
- Per-location SMS sender numbers
- Per-location WhatsApp Business numbers
- Outbound automation respects per-location sender rules
- Per-location compliance and opt-out lists
- Number porting supported on onboarding
No credit card required
One Dashboard For Every Location
Most platforms make you log into each location separately to see how it's doing. Ours rolls every location up into one dashboard — and lets you drill back down to the staff member who took the booking.
Revenue + Bookings Side-By-Side
Compare locations on revenue, bookings, services taken, average ticket, and staff utilization in a single view. Spot trends without exporting to spreadsheets.
- Side-by-side per-location comparison views
- Revenue, bookings, average ticket, no-show rate per site
- Staff utilization breakdown per location
- Service-mix comparison across locations
- Time-window controls (day, week, month, custom)
- Per-location goal tracking and variance
Drill From Company To Person
Start with total company revenue. Drill into a location. Drill into a service. Drill into a staff member. Each step preserves the time window and filters.
- Company → location → service → staff drill path
- Filters preserved across drill levels
- Click any chart to drill into its source data
- Saved drill paths for recurring reviews
- Per-staff performance views from any drill point
- Time-window slider stays consistent across drills
Export Per Location or Company-Wide
Export a single location's bookings, a single staff member's payouts, or the whole company's revenue. CSV ready for your accountant or BI tool.
- Per-location CSV exports
- Company-wide rollup exports
- Per-staff payout exports for payroll
- Service-mix exports for inventory planning
- Scheduled email exports to finance
- API access for piping into your BI stack
No credit card required
Customers Reach The Location They Care About
Every customer touchpoint — phone, SMS, email — is branded to the location, not to corporate. Customers feel like they're talking to their local salon, because they are.
Per-Location Phone Number
Each location keeps its own published phone number. Calls route to that location's IVR, that location's staff, that location's AI receptionist.
- Inbound calls routed to the right location's IVR
- Per-location call queues and ring strategies
- Per-location voicemail and after-hours behavior
- Per-location softphone for that location's staff
- Outbound dialing identifies as the local number
- Number porting supported during onboarding
Per-Location AI Receptionist
Each location's AI knows that location's services, prices, staff, and hours. It doesn't try to book a haircut at the medspa next door.
- Location-scoped knowledge base per agent
- Per-location pricing and policy answers
- Books into the right location's calendar only
- Routes to that location's staff on handoff
- Per-location after-hours behavior
- Per-location compliance language and opt-outs
Per-Location Email Sender
Confirmations, receipts, and campaigns send from the local domain or sender name — not from corporate. Customers recognize who's emailing them.
- Per-location SMTP sender configuration
- Per-location email branding and templates
- Per-location reply-to addresses
- Per-location SPF/DKIM domain configuration
- Per-location automated email rules
- Per-location email reputation tracked separately
No credit card required
True Multi-Tenancy Via Postgres Row-Level Security
Most multi-location platforms enforce location boundaries in app code — a where-clause one bug away from leaking data. We enforce at the Postgres layer with row-level security. The database refuses to return cross-location data even if app code asks.
Database-Level Enforcement
Row-level security policies live inside Postgres. Every query is filtered to the caller's location scope by the database itself — not by hopeful application code.
- Postgres RLS policies on every tenant-scoped table
- Location scope set on the database session, not the app session
- App code cannot accidentally leak cross-tenant data
- Audit-friendly policy definitions, reviewable like code
- Standard pattern that scales to thousands of locations
- Backed by years of Postgres production hardening
Location-Scoped Permissions
Roles map to locations. A manager at one location can't see another location's revenue. An ops director at corporate sees them all. Database enforces it.
- Location-scoped roles for managers and staff
- Multi-location roles for ops, finance, regional managers
- Owner role with full cross-location access
- Per-table policy fine-tuning when needed
- Permissions audit trail on every privilege change
- Service accounts scoped to specific locations
Audit Log Per Location
Every read and write is logged with the actor, the location, and the timestamp. Compliance reviews, incident response, and forensics all start here.
- Per-location audit log of every privileged action
- Actor + role + IP + timestamp on every entry
- Searchable from the location's admin console
- Export for SOC 2 and compliance reviews
- Tamper-evident — append-only architecture
- Configurable retention per location's policy
No credit card required
Powered By Five Connected Modules
Multi-location is not one feature — it's a property of the whole platform. Each module respects location boundaries from the database up.
Popular in these industries: