A guest eats at your wine bar nine times, your steakhouse twice, and your new place once. At group level she is one of the most valuable people you have. At the door of the new place she is a woman with a 7:30 booking whom nobody has ever met.
Most writing about cross-concept recognition stops at the first half of that. The second half is the operational problem, and it is not solved by knowing more — it is solved by deciding what the host actually gets told.
Two different questions wearing the same coat
Group-wide recognition answers a commercial question: who supports this group, how much, and what happens when they stop.
Service recognition answers a floor question: what do I do when this specific person reaches the podium in forty seconds.
They run on the same data and need completely different outputs. Collapsing them is what produces a host greeting a stranger like an old friend — which is worse than no greeting at all, because it is a small lie and guests hear it immediately.
What group-level recognition is genuinely good for
It is worth being clear about the wins, because they are real and most groups are not getting any of them.
- Seeing your actual supporters. A guest who spreads twelve visits across four concepts is invisible in every individual site's reporting and looks like a casual at all four.
- Lapse detection that is not a false alarm. Someone who "stopped coming" to the steakhouse may simply have moved to the wine bar. Per-site lapse lists send win-back emails to people who ate with you on Tuesday.
- Not sending four newsletters in one week. Groups do this constantly, and it reads to the guest as one company being disorganised, because that is what it is.
- Opening a new site. The people most likely to try it are already in your data, and on day one they are the only audience you have.
What to tell the host, and what to withhold
The rule: give the host a fact they can act on and a fact they can say out loud. Anything they cannot say out loud should not be in the briefing, because it will leak into their manner anyway.
UNUSABLE Sarah Okonjo — group VIP, high value, regular. USABLE Sarah Okonjo, 7:30, two. First time in this room. Goes to the wine bar most months and Andrés knows her — Loire reds, never oaked. Say: "First time with us — Andrés said to look after you." Then let her lead. Do not say: anything implying we already know her here. We do not.
A model that holds: status per site, relationship per group
The version that survives contact with a floor has two layers, and groups usually discover they need both about a week after deciding they only need one.
- Per site — has this guest been to this address, how often, how recently. This drives the greeting, the table, and whether anyone should pretend to remember anything.
- Per group — total relationship across concepts: visits, spend, tenure, lapse status. This drives who you write to, who you worry about, and who gets the first invitation to the new site.
- Both at once — a guest can be a group regular and a site first-timer. That combination is common and it is precisely where recognition goes wrong, so design for it rather than treating it as an edge case.
Where consent stops travelling
This is the part groups get wrong with entirely good intentions. A guest who agreed to hear from your wine bar has not necessarily agreed to hear from your steakhouse, and "we are the same company" is a fact about your cap table rather than about her inbox.
The rules vary by where you operate and none of this is legal advice, but one operational principle is safe everywhere: record which brand the consent was given to, and keep that record. Groups that store consent only at group level cannot unwind it later, and cannot answer the question when somebody eventually asks it.
Recognition travels freely inside your own business. Permission to send things does not.
What to write down
Four fields carry most of the value, and the last one is the one almost nobody keeps.
- Which sites a guest has visited, held separately rather than as a group total.
- Which brand each consent was given to, and when.
- Preferences that are portable — allergies, wine, pace — kept apart from ones that are not. "Table 9" means nothing at a different address.
- Who at the group knows this guest personally. One name. It is the most useful field on the record and it exists almost nowhere.