Bring restaurant visits, online orders, reservations and guest preferences together. Know what each guest has ordered, where they visited and which benefits they used, so your team can make the next interaction more personal.
Visits, reservations, preferences and loyalty in a shared guest record.
Dishes, payments and discounts, with the brand and branch behind each order.
Turn purchase history and visit patterns into relevant follow-up audiences.
01 / GUEST PROFILES
Look up a guest by phone and see their relationship with your restaurant: previous orders, spending, last purchase, reservations, service notes and loyalty. The team has useful context before taking the next order or answering a question.
Identified orders from POS, your ordering website and customer app connect to the guest record. Saved delivery addresses, feedback and purchases stay available when the guest returns through another channel.
02 / ORDERS, BRANDS & BRANCHES
For a restaurant group, the guest history spans your connected brands and branches. Open an order to see the brand, the exact location and whether it came through restaurant service or an online channel.
Read the dishes, quantities, selected options, service notes, payment and total behind that visit. It helps the team find a previous choice, answer a question about a charge or serve a familiar guest at a different location.
03 / RESERVATIONS & ARRIVAL
A reservation belongs to a guest with a history. Check the date, party size, table, branch and occasion alongside the context already recorded about them. The host can prepare for an anniversary, recognise a returning guest or pass a useful request to the service team.
Open the booking from the guest profile. When the host seats the party, the linked POS order keeps the guest identity, so the visit continues in the same restaurant history.
04 / PREFERENCES & FEEDBACK
Keep useful service notes with the guest: a preferred preparation, a special occasion or a request the team should remember. Check earlier dishes and modifiers before making a recommendation.
Read feedback with its order reference before calling back. The next person handling the guest can understand what happened and respond with context. Saved addresses are there for the next delivery, too.
05 / DISCOUNTS & LOYALTY
The guest record shows loyalty membership, tier and points, with a link to the transaction history. Your team can check the balance and understand previous earning and redemption activity before explaining the next reward.
For a question about a previous bill, open its order details. Applied promotions, POS discounts and loyalty redemptions remain part of the check, alongside the final amount and payment. The next conversation starts with what actually happened.
06 / ACQUISITION & REPEAT VISITS
See recorded acquisition sources and campaign details alongside guest purchases. An order can retain the source, campaign, restaurant and branch, helping your team understand how the guest first found you and where they ordered afterwards.
Use order count, total spending, average check and the last purchase to recognise regulars and changes in their buying pattern. Connected marketing reports add repeat-purchase and campaign analysis when you need to look across the guest base.
07 / GUEST AUDIENCES
Build an audience from the way guests buy: their last order, visit frequency, spending, dishes, brand or branch. Combine conditions and check the group before using it in a campaign.
For example, follow up with repeat customers who have not ordered for more than 30 days. Or choose guests who bought a particular dish at one of your locations. Connected WhatsApp campaigns and loyalty journeys give the group a relevant reason to return; marketing reports let you review what happened afterwards.
IMPLEMENTATION & DATA TRANSFER
Our team helps you move guest records, past orders and the history available from your current systems. Keep the context your team has built over time, so returning guests are familiar from the first day in HoreX.
We review your available exports with you and agree what can be carried over before the switch — including order details, discounts and booking records where available.
Guest history, restaurant service, multi-branch context and the information behind a relevant follow-up.
Find a returning guest by their phone number.
Orders with an identified guest build on the same customer record. Staff can open their contact details and previous purchases when taking the next order.
Return to the order behind a guest’s question.
See dates, restaurants, order types, amounts and order status. Open an order to review its items instead of asking the guest to remember what they bought.
See what a guest has spent with you.
The profile brings together total spending, order count, average check and the last order date. These figures describe recorded purchases; they are not a forecast of future value.
Choose guests by their actual orders.
Build audiences using visit dates, order count, spending and items purchased. Combine conditions to make a list that fits the offer you plan to send.
Use guest audiences in your restaurant’s campaigns.
Send a relevant offer through the connected WhatsApp Business workflow. Approved templates, messaging permissions and provider delivery status remain part of the campaign setup.
Check previous choices before making a suggestion.
Order details show the dishes and modifiers the guest selected. Item-based audience filters also help you find people who have ordered a particular dish or category.
Keep a shared guest history within your business.
Connected branches use the organisation’s guest records. Staff see the information allowed by their access, and order history retains the restaurant behind each visit.
Make an important service detail easy to find.
Mark a guest as VIP and add useful notes to their profile. Keep notes specific, current and appropriate for the team that will use them.
Include birthdays in your loyalty programme.
A recorded birthday can be used by the configured loyalty journey. Choose the guest benefit and message in the loyalty workflow, then review how it fits your service.
See when the guest last ordered.
Use order count and last-order date to understand how often a guest returns. Marketing reports add cohort and repeat-customer views when you need to compare groups.
Build a follow-up list from time since the last order.
Marketing analytics groups inactive guests by elapsed time, including 30, 60 and 90-day bands. Review the guest’s history and your restaurant’s usual visit pattern before choosing an offer.
Keep useful context with the guest.
Record preferences or a service issue in the profile notes so the next colleague can pick up the conversation. Update the note when the situation changes.
Find the address used for a guest’s delivery.
The guest record keeps saved delivery addresses and their details. Check the selected address and any instructions with the customer when taking a new order.
Read a review with the order in view.
Feedback linked to a guest appears with their profile. Check the associated visit and follow up through your service process when a guest reports a problem.
Record what the guest tells your team.
Keep relevant dietary information in the guest record and confirm it when taking an order. Staff should still communicate the requirement to the kitchen for that meal.
Connect an invitation to the member who made it.
Configured loyalty referrals can credit the referring member and the new guest. Review referral and bonus rules in the loyalty programme before using them in a campaign.
Check the phone number before making a second profile.
Phone-based matching helps staff find an existing guest. If records need correction, review the contact details and linked orders first; ask support about duplicate records that need consolidation.
Take a selected guest analysis into a spreadsheet.
Export the supported audience or marketing report when your team needs to review the data elsewhere. Choose the relevant guests and fields, and limit access to people who need that information.
Prepare for an arrival using the guest’s existing context.
Open a linked reservation from the guest record to review its date, party size, table, branch and notes. Hostess connects booking and seating with the same guest identity in POS. Booking states also help the team understand cancellations and no-shows.
See the promotion or reward behind the paid check.
Open a previous order to review its applied promotion, named POS discount, manual discount or loyalty redemption. Check the final amount and payment alongside the dishes rather than treating a discount as an isolated guest attribute.
Keep the source of a guest’s relationship in view.
View recorded acquisition sources and order campaign data with the guest context. Where captured, source, medium and campaign remain available alongside the order. Staff can also record a known source without replacing existing order attribution.
Bring available guest and purchase history with you.
The HoreX implementation team helps review exports from the current systems and agree the history to transfer. Available guest records, past orders, dish details, discounts and booking records can be assessed together. The transfer scope follows the records and exports the previous systems provide.
When an order identifies the guest, HoreX matches or creates the customer record using their phone number. Staff can also manage contact details in the guest directory.
Yes. Audiences can use order dates, count, spending and purchased items. Combine conditions and preview the matching group before using it in a campaign.
Connected branches within the organisation share guest records. Order history keeps the branch context, and staff access controls determine which information is available.
The profile shows recorded spending, order count and average check. This is historical guest value, not a prediction of future spending or profit.
Yes. The guest record connects to membership, points and tier information. Loyalty earning, redemption and guest journeys are configured in the loyalty programme.
Inactive-guest views use time since the last order, including 30, 60 and 90-day bands. They help build a follow-up list; they do not predict whether an individual guest will leave.
Phone matching helps avoid creating a second record. Review the contact details and linked orders when you find duplicates, and ask support about records that need consolidation.
Supported audiences and marketing reports can be exported for further analysis. Select the relevant data and share it only with the people who need it.
Yes. The guest history links to orders across your connected restaurant brands and branches. Each order retains its brand and specific branch, so staff can see the location behind the purchase.
Yes. Linked bookings can be opened from the guest record, with the date, party size, table, branch and reservation notes. Seating through Hostess retains the guest identity on the linked POS order.
Yes. Our implementation team reviews the available records and exports with you and agrees the transfer scope. This can include guest records, past orders and available details such as dishes, discounts and booking records, depending on what your current systems provide.
Explore guest history, orders across brands, reservations, loyalty and follow-up audiences with your team.
