One number,every branch.
Multi-site, IVR branch picker, one bill, no per-site setup chaos.
Built for UK retail and hospitality groups: an IVR sends the caller to the nearest branch, every site shows up in one head-office dashboard, and adding a new site is a few clicks rather than a BT engineer visit. No per-site phone bills, no per-site sign-ups.
- Multi-site restaurant group
- Independent retail chain
- Hotel front-desk
- Café franchise
- Per-siteAnalytics + IVR + hours
- 1 billEvery site, one account
- Same dayNew-site provisioning
What you actually get.
Features tuned to retail & hospitality — included on every seat, no upsells.
IVR branch picker
One central number, IVR menu sends the caller to the right branch ('press 1 for Liverpool, 2 for Manchester'). Per-branch hold music, opening hours, voicemail. Out-of-hours falls through to a group voicemail.
WhatsApp Business per site
Register WhatsApp Business against each branch's number (voice verification works on the landline). Customers text bookings, orders, 'what time you closing?' to the same number they'd ring. Each branch runs the WhatsApp Business app on the front-desk device.
Holiday hours by site
Per-site holiday calendars. Christmas Eve shorter hours? Set it once per site; the IVR + voicemail messaging swap automatically. No staff manually changing greetings.
Group-wide call analytics
Head-office dashboard shows call volume per site, missed-call rate, average wait, peak hours. Spot the site that's burying calls before they bury you in lost-customer complaints.
AI summary on every booking call
Every recorded booking call gets a structured AI summary on the call card — party size, time, allergens flagged — so the manager scans a week's worth of calls in 10 minutes rather than playing them back.
Roll out a new site in an afternoon
New branch opens? Add the site in the portal, pick a local number, hand the new manager a desk phone or the VoiceCloud app on a tablet. Live on your dial plan the same afternoon — no engineer visit.
Three days in the life of a retail & hospitality.
Concrete moments — what triggers a call, the features that handle it, the outcome. These are scenarios you'll recognise; map them onto your own week.
- 01Scenario4 features
Friday-night booking surge
The triggerCustomer rings to book a table for 8 — 19:30 on a Friday, three sites taking calls at once.
What happensCaller hits the central number, the IVR menu offers 'press 1 for Liverpool, 2 for Manchester, 3 for Leeds' — they pick Liverpool and land on the right branch's queue.
Branch is mid-service; caller hears '2nd in line, ~90s — please hold' instead of an engaged tone. Hold music + branded messaging keep them on the line.
Call ends, the AI summary appears on the call card in the portal: party size, time, allergens flagged. Manager copies the booking into the EPOS / reservations system.
Manager pings the customer on WhatsApp Business from the branch's Giant mobile: 'Booked you in for 8 at 19:30 — see you Friday.' Same brand, no new channel for the customer to learn. Business SMS runs on the same mobile number for people who prefer text over WhatsApp.
OutcomeFriday-night queue throughput holds. Customers who would have hung up wait the 90 seconds instead. Manager confirms the booking without scribbling notes.
- 02Scenario3 features
Opening a new branch in an afternoon
The triggerAcquired site goes live next week. Head office needs phones working before the doors open.
What happensHead office adds the new branch as a site in the VoiceCloud portal — picks a local geographic number for the door signage, sets opening hours.
Ship the new branch a pre-provisioned Yealink. They plug it in, it registers itself. No engineer, no manual SIP credentials. Or skip the hardware and run the VoiceCloud app on a tablet.
New site joins the central IVR menu; out-of-hours diversions follow the group rota; per-site analytics start populating immediately.
OutcomeNo engineer visit. No 'we need a phone line installed' BT engineer wait. New branch takes calls from day one.
- 03Scenario3 features
Group-wide call analytics on Monday morning
The triggerHead of ops opens the weekly dashboard to spot underperforming branches.
What happensPer-site dashboard shows call volume, missed-call rate, average wait — colour-coded against group baselines. Three sites flagged for high abandonment.
Click any flagged site — see the recordings from missed-call hours. Listen to two; obvious staffing gap at 12:00 lunchtime peak.
Pull the hourly call-volume chart for the flagged sites — confirm the 12:00 peak is consistent, not a one-off. Pass the data to head of ops as a CSV export for the rota review.
OutcomeOperational problem spotted, root cause identified, and the staffing rota tweaked — all from one dashboard, no per-site phone-system to log into separately.
Talk to the UK team about retail & hospitality.