One Phone Line Per Location Is Not a Problem. It Is the System.
For a restaurant group, the challenge is not managing multiple lines — it is making sure each location answers its own calls with its own menu, while the group sees everything in one place. That is how DineCall handles multi-location AI phone answering.
The most common assumption about multi-location AI phone answering is that it requires some kind of central hub managing everything from one place. It does not. Each location runs its own line, with its own menu, its own routing, and its own AI — and the group sees all of it together.
What multi-location actually means for the phone
The three restaurants in Hao's Restaurant Group — Hao's Lamb Restaurant, Royal Beef, and Hao's Tapas Kitchen — are minutes apart in Richmond, BC. All three ring during the dinner rush. None of them wants the AI answering Hao's Lamb to quote Royal Beef dishes, or for a caller to Royal Beef to hear Hao's Tapas menu options. Each location needs its own AI, its own menu, and its own routing — configured independently but managed under one group account.
Hao's Lamb Restaurant at 4260 Number 3 Road serves Henan roasting and braising — twelve menu categories and 126 dishes. Their biggest calls are for the whole roast lamb, at $788.99, which must be booked 24 hours ahead because the oven needs the head start. The AI at that number knows those dishes, knows the $788.99 price, and knows that the lamb booking is a table reservation type — so it captures the date, time, party size and name, confirms on the call, and writes it to the live board so the kitchen can plan accordingly.
Royal Beef at 4791 McClelland Road is a different menu. Hao's Tapas Kitchen at 6451 Buswell Street is a third. The AI at each number knows which kitchen it belongs to. A caller to Hao's Lamb hears Hao's Lamb dishes. A caller to Royal Beef hears Royal Beef.
One board, three rooms
From the group dashboard, the owner sees calls, orders and bookings from all three rooms — a live view of all three locations in one place. Each location's orders and bookings appear with their source. The individual restaurant boards are also available, so a manager at Hao's Lamb sees only their own line.
Online ordering runs across the group the same way. The group website at haoscatering.ca shows all three restaurants; a guest ordering from the Hao's Lamb section of the site places an order that routes to the Hao's Lamb kitchen board. Phone, web, and QR orders all arrive the same way per location.
What the AI handles differently at each location
The whole-roast-lamb booking is the clearest example: it is a reservation call that starts with a food item. The AI at Hao's Lamb recognizes this — it knows the lamb must be booked ahead, and it knows that this call type is a table reservation with a high-value food item attached. It captures the details and confirms the booking on the call.
At Royal Beef, the AI answers from the Royal Beef menu, confirms the booking, and if the caller has a question about banquet options that goes beyond a standard booking, it hands the call to a person.
Hao's Tapas Kitchen is open 10 to 10 with no afternoon break, which means the lunch call, the mid-afternoon call, and the late-supper call all arrive on the same line. The AI holds them all simultaneously — the kitchen never misses a call regardless of when it arrives.
What the group manages in one place
The group dashboard is where multi-location shows its value. One view of all three phones, all three order boards, all three reservation boards. Customer records are visible per-location or across the group. And because DineCall owns the phone channel that most restaurant software has historically ignored, the group finally has visibility into phone-order volume per location — data that has not existed before.
POS integration works the same way per location. If the group runs POS KING across all three, the ordering API routes tickets into each location's POS workflow. If locations use different systems, each is configured separately. The group does not need to standardize its POS to use DineCall.
Pricing for multi-location groups
Multi-location groups get custom pricing that reflects the scale and complexity of the deployment. A group with three locations, each running its own menu and board, has a different cost structure than a single-location restaurant. Custom pricing is available by writing to hello@dinecall.ai with the number of locations and approximate monthly order volume.
Setup is 2-3 business days per location. The group account is configured first — the website, the shared brand presence, the group dashboard — and then each location's AI is trained on its own menu and routing. Locations can go live on different days as the configuration is completed.
FAQ
Q: Does the AI at one location know about the other locations? A: No — and that is intentional. Each line is its own restaurant. A caller to Hao's Lamb hears Hao's Lamb menu, not Royal Beef. What they share is the group dashboard that the owner watches, not the AI that answers the phone.
Q: Can the AI take a booking that spans multiple locations — like a private event across two rooms? A: Those calls go to a person by default. The AI knows what it should handle and flags the rest for the team.
Q: Does each location need its own phone number? A: Yes — the existing number at each location becomes the DineCall line for that restaurant. No new numbers required.
Q: Can we add a fourth location later? A: Yes. Each location is added independently. New pricing is confirmed based on the updated location count.
Q: How is customer data handled across locations? A: Each location has its own customer records. The group account can see aggregated data across all locations or drill into individual location performance.