Measure. Understand. Act. Improve.
One system for every angle you have on the guest.
Three streams that separately tell you half a story. Together, they surface hundreds of audits, thousands of surveys, and thousands of reviews per cycle — pulled from your existing stack through a single data layer.
Operational truth from inside your venues.
A trained diner visits, follows a custom questionnaire, and reports on service, cleanliness, standards and product quality. Backed by 10,000+ diners in the UK and a partner network worldwide.
See mystery auditsPerception the moment it forms.
Trigger a short, contextual survey right after the visit, via wifi, booking flow, receipt QR, or your app. Every answer ties back to venue, visit and dish, and Halo diagnoses the pattern across thousands of responses without any survey fatigue.
See surveysEvery platform your guests write on, one queue.
Import ratings and comments from 17 platforms across social review, booking and delivery. Respond to Google and Facebook directly from HGEM, compare per channel and per location, and benchmark against local competitors.
See reviewsHalo diagnoses the why, not just the what.
Halo reads every audit, review, and piece of feedback across your estate — not summarising, diagnosing. A typical diagnosis cross-references 300+ audits, 4,000+ surveys and 1,000+ reviews in 1–2 seconds. Ranks fixes by projected revenue impact, so your team doesn't have to guess where to spend attention.
At 6 venues, NPS drops most sharply when starter-to-main exceeds 14 minutes. Estimated impact: £2,340/venue/month.
Response to the guest. Action plan to the team.
Every diagnosis Halo makes turns into two things at once. Reviews and complaints get answered — auto-published in your brand voice or drafted for approval, within the guardrails you set. Operational patterns get an action plan — owned by a named person, tracked to completion, with impact measured after.
Predict the outcome. Before you commit.
Halo models the commercial impact of an operational change before you make it — using your estate's own data, not industry averages. Measures the delta after each cycle. Board-ready ROI evidence closes the diagnosis, and Halo carries what worked into next month's read.
Attach your tech stack.
Your CRM knows the guest. Your POS knows the order. Your reviews know how it went. Halo reads all three at once. Because a signal from one tool tells you something happened. The pattern across all three tells you what to do about it.
Every review platform your guests write on, one queue.
Import ratings and comments from every social review platform and delivery aggregator. Respond to Google and Facebook directly from HGEM. Compare performance per channel and per location, and benchmark against local competitors.
The review stream you'd otherwise miss.
Guests review restaurants inside their booking platforms and hotels through OTAs. HGEM ingests those reviews too, tied back to visit and venue — so a slow starter-to-main on OpenTable and a low value-for-money on Booking.com surface in the same diagnosis.
OpenTable and Booking.com exclude reviews with no comments. The Fork was previously Bookatable. DishCult was previously ResDiary.
Recognise the guest. Prefill the survey.
Use your CRM to invite guests who left a digital footprint (booking, wifi) to provide feedback. Pre-populate surveys with visit date, location, guest ID, order ID or dish codes. Pass headline results back for campaign segmentation via our API or a regular file export.
Only rate what the guest actually ordered.
Import your menu so we capture feedback on the dishes or products that matter. Options depending on your POS: send dish codes straight to the feedback site, send an order ID for us to look up, or receive a daily export of orders. Product-level ratings without the noise.
Your BI stack, powered by HGEM data.
HGEM gives you reporting and analysis out of the box, but many clients want the data in their own BI system alongside sales and labour. Developers can use the HGEM Key Results API for visit and question results across audits, feedback, and reviews — or take a regular data extract to an sftp server or inbox.
The right ticket, in the right system, in real time.
Trigger support tickets in Zendesk or Freshdesk based on your parameters (score thresholds, sentiment, keywords). Tickets are created in the name of the requester so you can respond directly. Or push tasks to Trail, or to Fourth Engage for employee-facing follow-ups.
Send recovery, right from HGEM.
For those with a toggle or Eagle Eye account, send gift cards directly from HGEM in response to guest feedback. Or provide us a series of voucher codes and expiries and we send them from your email domain — an effective incentive for repeat visits where it fits the brand.
Open API for custom sources · managed onboarding sets it all up during the 6–8 week rollout
What closing the loop looks like in numbers.
What operators ask before switching.
The short answers. Longer conversations happen in demos.
How does Halo decide which reviews to auto-respond to?
How long does Halo take to respond to a review?
How does Halo learn across cycles?
Can I start with one module and add others later?
How long does implementation take?
Which systems does HGEM integrate with?
What size operator is HGEM built for?
Do we own our data? What happens if we leave?
See Halo run on your estate.
A 45-minute demo. Your brands, your venues, your priorities. If HGEM isn't the right fit we'll say so.
Book a demo