Managing Multiple Locations

Configure your AI to handle calls for multiple business locations with location-specific routing, greetings, hours, and knowledge bases. Perfect for franchises, multi-office practices, and businesses expanding to new areas.

🎯 What You Will Learn

Setting up separate location profiles with independent configurations
Assigning unique phone numbers and routing rules per location
Managing location-specific hours, greetings, and knowledge bases
Using centralized analytics to compare performance across locations

⚠️ Prerequisites

FORAI Enterprise plan (multi-location requires Enterprise)
A list of all locations with their addresses, hours, and staff
Phone numbers (existing or new) for each location
A designated admin for each location (optional but recommended)

🚀 Step-by-Step Guide

Access the Multi-Location manager

Navigate to Settings > Locations. The manager shows all your locations in a list or map view. Click 'Add Location' to begin setting up a new location profile. Each location operates as an independent configuration within your account.

Settings - Multi-Location Manager

Create location profiles

For each location, enter: name, address, phone number, hours of operation, and timezone. Upload a location-specific logo if applicable. Assign a location admin who can manage settings for their location without affecting others.

Location Profile Configuration

Configure location-specific greetings and voice

Each location can have its own greeting, voice, and personality settings. A downtown law office might use a formal tone while a suburban family practice uses a warm, friendly voice. Customize per location under Location > Voice Settings.

Set up location-based routing

If you use a central number, configure the AI to ask 'Which location are you calling about?' and route accordingly. Alternatively, assign unique numbers per location for direct routing with no caller friction.

Build location-specific knowledge bases

Each location can have its own FAQ knowledge base layered on top of a shared company-wide base. Location-specific entries (parking info, specific services, local team names) override the shared base when a caller reaches that location.

Configure per-location calendars and CRM mapping

Connect each location to its own calendar and CRM pipeline. Appointments at Location A go to Calendar A; appointments at Location B go to Calendar B. CRM records are tagged with location for filtering and reporting.

Monitor cross-location analytics

The Analytics dashboard includes a 'Location Comparison' view showing side-by-side performance metrics. Compare call volume, answer rate, booking rate, and sentiment across locations. Identify top performers and replicate their configurations at underperforming locations.

Cross-Location Analytics Dashboard

💡 Pro Tips

Start by fully configuring one location as your 'template'. Once it's working perfectly, clone it for new locations and customize only the differences (address, hours, team). This saves enormous setup time.

Use the 'Shared Knowledge Base' for company-wide policies and FAQs (refund policy, insurance accepted, etc.) and 'Location Knowledge Base' only for location-specific information. This prevents maintaining the same info in multiple places.

Designate one person as the 'multi-location admin' who has global visibility. Individual location admins should manage day-to-day, but someone needs to see the big picture.

Run the 'Location Comparison' report monthly and share it with all location managers. Healthy competition between locations drives improvement.

⚠️ Important Warning

Always test your configuration with the built-in simulator before deploying to live callers. Changes to voice settings, routing rules, and workflows take effect within 60 seconds. Monitor the first 5-10 live calls after any change and revert immediately if you notice issues.

⚙️ Troubleshooting