Knoxville Restaurant Group Unifies 4 Locations, Cuts Phone Costs 44%

4 locations · Bar & Dining · Hospitality

44% — Cost Reduction
4 locations — Unified System
100% — Calls Answered
0 — Missed Reservations

The Challenge

Lockwood Hospitality Group operated four Knoxville venues — a downtown gastropub, a west Knoxville sports bar, a North Knoxville neighborhood bistro, and a Bearden cocktail lounge. Each location had its own landline through a different carrier, and the group owner had no visibility into call volume, missed calls, or peak hours at any location. Staff frequently couldn't answer phones during rush service. Managers had no way to forward calls between locations when one venue was closed or short-staffed. Monthly phone spend across all four locations totaled $2,800.

The Solution

ATS Voice deployed a unified cloud phone system across all four Knoxville locations. Each venue kept its existing direct number. A shared management dashboard gives the group owner real-time visibility into call volume, missed calls, and response times across all locations from a single login. After-hours calls route to a voicemail-to-email system so reservation requests are never lost overnight. During service rushes, calls that go unanswered at one location can be configured to overflow to another location's host stand. The owner and all four managers use the mobile app.

Results

Combined monthly phone costs dropped from $2,800 to $1,568 — a 44% reduction and $14,784 in annual savings. In the first 60 days, the owner identified that the North Knoxville location was missing an average of 11 calls per week during the dinner rush — a previously invisible problem. After adjusting staffing at the host stand, missed calls dropped to zero. Reservation no-shows decreased 18% after implementing the voicemail-to-email confirmation callback workflow.

The Challenge: Four Locations, Zero Visibility

Lockwood Hospitality Group built its reputation one venue at a time. The downtown gastropub came first, followed by the west Knoxville sports bar, then the North Knoxville bistro, and finally the Bearden cocktail lounge. Each opened with a basic landline and local carrier service — functional for a single location, but never designed to scale across a multi-venue operation.

By 2025, the group owner had a problem he could feel but couldn't measure: calls were being missed. During Friday dinner service at any of the four locations, the host stand was managing walk-ins, managing the reservation list, and trying to answer phones — simultaneously. When calls went unanswered, there was no record of it, no callback, no voicemail notification. Reservations were lost silently.

The other problem was cost. Four separate carrier accounts with four monthly invoices totaled $2,800 per month — an amount that had grown through annual rate increases without anyone noticing, because no single bill looked large enough to question.

The Visibility Problem

The owner had no management dashboard, no call analytics, no way to know which location was struggling with call volume on any given night. He relied on managers self-reporting — which meant the problems that never got reported were the ones no one knew to look for.

When ATS Voice conducted a pre-sales consultation and walked through what a unified system could show him, the owner's first reaction was: "You're telling me I can see missed calls by location, by hour, from my phone?" The answer was yes. That single capability drove the decision.

Migration Across Four Active Venues

Migrating an active restaurant group requires working around service hours. ATS Voice scheduled each location's cutover during its weekly closed period:

All four locations were live on the new system within the same week, with no service disruption during operating hours.

What the Data Revealed

Within two weeks of going live, the owner had data he'd never had before. The North Knoxville bistro was missing an average of 11 calls per week between 5:30 PM and 7:00 PM on Thursday, Friday, and Saturday. The call log showed the pattern clearly: calls coming in at 5:45 PM — prime reservation time — going to voicemail because the single host was managing the door.

The fix wasn't technical — it was operational. The owner added a second staff member to the host stand at 5:30 PM on Thursday through Saturday at the North Knoxville location. Within 30 days, missed calls at that location dropped to zero. The owner estimated the recovered reservations from that single adjustment more than covered the first year's system cost.

The Voicemail Workflow

The after-hours voicemail-to-email setup changed how reservation requests were handled overnight. Previously, voicemail went unchecked until the opening manager arrived — sometimes hours after a message was left. With voicemail-to-email, every overnight reservation request arrived in the location manager's inbox immediately. Managers began responding to reservation requests before they arrived at the restaurant, improving the guest experience before the guest ever walked in.

Results at Twelve Months

After twelve months on the unified system:

For the group owner, the most valuable outcome wasn't the cost reduction. It was the management visibility. For the first time, he had objective data about how each venue was performing on the phones — and the ability to act on it.

The Technology Behind the Visibility

The unified dashboard that changed Lockwood's operations isn't a complex piece of software. It's a browser-based portal that any manager can access from a phone or laptop. For the group owner, the weekly ritual became simple: Sunday evening, before the new week's service schedule, he opens the dashboard and reviews the prior week's call data for all four locations.

What he actually watches: total calls by location, answered vs. missed ratio broken down by hour, average time to answer, and voicemail volume. The peak call windows showed up immediately in the data. The downtown gastropub received its highest call volume between 5:00 PM and 7:30 PM on Friday and Saturday. The sports bar saw a secondary spike at 11:30 AM on Sundays — the pre-game reservation window the owner hadn't consciously tracked before.

The cloud PBX itself runs entirely off-site. There is no server in any of the four locations, no hardware to maintain, and no per-location IT vendor to call when something fails. Each venue has a VoIP adapter plugged into the existing network connection. The ATS Voice platform handles routing, queuing, voicemail transcription, and analytics in the cloud. From the owner's perspective, the system is just the dashboard on his phone and the phone on the host stand.

What the reporting revealed about staffing was specific. The sports bar was consistently understaffed for Sunday lunch calls — a shift no manager had flagged as a problem because tips from the lunch shift were lower than dinner. The call data told a different story: Sunday lunch call volume rivaled Friday dinner. That insight led to a permanent staffing adjustment.

Training Across Four Locations

Training a restaurant staff isn't like training an office team. Availability is fragmented, shifts overlap, and the people who need the training most — host stand staff — are often the least available during prep hours. ATS Voice structured the training for Lockwood Hospitality Group in a staggered format that worked around service schedules.

Each location received a 45-minute in-person training session during its pre-service prep window. The session covered three things: how to answer and transfer calls, how to use the mobile app if they were pulled off the host stand, and how to retrieve voicemails. Most staff were comfortable with the system within the first hour of live service.

Manager training was separate and longer. The four venue managers each received a one-on-one session on the analytics dashboard: how to read the daily call report, how to configure overflow rules for their location, and how to forward calls to another venue when their location closed early. The owner received training on the group-wide view — the multi-location summary that shows all four venues simultaneously.

The downtown gastropub's general manager later said the training was simpler than expected because the system's logic matched how the team already thought about phone coverage. The learning curve wasn't about the technology; it was about the new visibility.

Competitive Context: Why Restaurants Miss Calls

The missed call problem Lockwood experienced is not unique to their group. Industry research consistently shows that restaurants miss between 15% and 30% of inbound calls during peak dinner service hours. The cause is structural: the host stand is simultaneously managing the door, the waitlist, and the phone, with no call queue and no backup.

Most restaurant operators know this is happening in a general sense. What they don't know — because traditional phone systems provide no data — is the precise magnitude, the exact time windows, and which locations are performing worse than others. The absence of data doesn't mean calls aren't being missed; it means the problem is invisible.

Lockwood's North Knoxville bistro was missing 11 calls per week. That number sounds manageable until you calculate it: 11 calls per week at an average reservation value of $85 per table means roughly $935 in potential weekly revenue at risk, or approximately $48,600 annualized assuming 50 operating weeks. The owner's comment after seeing the data — "I didn't even realize how many calls we were missing" — reflects an experience that most multi-location restaurant operators would recognize. The data doesn't create the problem. It makes an existing problem impossible to ignore.

Year Two: Building on the Data

The first year of call data created a baseline. The second year allowed Lockwood to act on patterns that only became visible after twelve months of consistent reporting.

The voicemail-to-email transcriptions revealed something unexpected: a significant share of inbound calls were asking about the same specific menu items. At the downtown gastropub, callers frequently asked whether certain seasonal dishes were still available and what the current happy hour offerings were. The owner worked with each venue's manager to update answering scripts with current information, reducing the average call length on those inquiries by more than a minute and freeing up host stand time during peak windows.

Peak booking time analysis across all four venues allowed for more precise hiring decisions. The owner had historically scheduled openings based on service volume; the call data added a reservation inquiry layer that wasn't visible before. Two locations adjusted their host stand coverage to start 30 minutes earlier on peak days, driven by the data showing reservation calls concentrating before the dinner rush rather than during it.

The North Knoxville bistro made the most significant operational change in year two: it adjusted its reservation cutoff time from 8:30 PM to 8:00 PM based on call volume patterns. The data showed that after 8:00 PM, inbound reservation calls dropped sharply and were primarily callers seeking next-day or weekend tables. Moving the cutoff earlier allowed the host to close the reservation queue earlier and focus on in-house service without the distraction of late calls during the most demanding service window.

What $14,784 in Annual Savings Represents

For a four-location restaurant group operating on hospitality margins, $14,784 in annual savings is not a rounding error. It represents approximately 740 hours of server labor at Knoxville's current prevailing wage for tipped staff — or roughly five months of food cost for one of the smaller venues.

The owner reinvested the savings in two ways. The first was the North Knoxville staffing addition: a part-time host position added at the Thursday-through-Saturday peak, funded entirely by the phone savings. That position directly addressed the missed call problem the data revealed and more than paid for itself in recovered reservations. The second use was a small upgrade to the Bearden lounge's front-of-house technology — a wireless reservation tablet that allowed the host to manage the list while staying near the entrance during busy periods.

Neither investment would have been possible without the phone system savings making them visible as an option.

Advice for Multi-Location Restaurant Operators

The Lockwood experience offers specific lessons for other restaurant groups evaluating communication infrastructure.

Start with the data, not the cost. The cost reduction at Lockwood was significant, but the owner would not have acted without understanding what visibility meant operationally. Before any vendor conversation, ask whether the system provides per-location, per-hour call analytics. If the answer is no, it is not a multi-location solution.

Migrate during closures, not slow periods. There is a difference between a slow Tuesday and a scheduled closure. Lockwood's migration ran smoothly because each location's cutover happened during its actual weekly closed period — not during a period when staff were present and distracted. A restaurant in active service, even a slow one, is not a good migration environment.

Use the data for staffing before technology. The biggest operational improvement at Lockwood came not from a technical change but from a staffing adjustment driven by call data. The technology provided the information; the human decision followed. Restaurant operators who treat phone analytics as a cost-control tool miss the more valuable use case: staffing optimization. The call data shows exactly when each location needs more hands near the phone.

I didn't even realize how many calls we were missing until I could actually see the data. That alone paid for the system.

— Owner, Lockwood Hospitality Group — Knoxville, TN