Direct Guest Relationship

In practice

For a manager, the practical question is not how many orders a channel brought in this month, but who can reach the guest again without paying for that reach a second time. An order placed through a marketplace leaves the restaurant with a completed transaction and little else: the marketplace, not the restaurant, holds the guest's phone number or email, and decides whether and when to invite that guest back. An order placed through the restaurant's own page, app or a phone call leaves the restaurant with a contact record, an order history and, where the guest agreed to it, permission to message that guest directly next time. The channel a guest happens to use on a given order therefore decides more than that order's margin — it decides who holds the next one.

How it works

A direct guest relationship rests on three things a restaurant either holds for a repeat guest or does not: contact details, an order history, and consent to be contacted again — captured by the restaurant itself, not only by an intermediary. It builds one order at a time: a single order placed directly does not create it on its own, and a restaurant with almost all of its repeat volume running through marketplaces can end up with almost no direct relationships despite serving the same guests every week. Direct guest relationship is Menuella's term for this pattern. The wider business language for the same distinction is first-party customer data, and hotels — which face an equivalent choice between a direct booking and an OTA booking — usually call it guest data ownership; food service itself had not previously had one name for holding onto a repeat guest's contact rather than losing it back to the platform on every order.

Example

A restaurant identifies 500 guests who ordered from it more than once in the past twelve months. Of those, 350 placed at least one order through the restaurant's own channel, so the restaurant holds a phone number or email for them: 350 ÷ 500 = 70%. The remaining 150 ordered exclusively through marketplaces, and the restaurant has no way to contact them directly: 150 ÷ 500 = 30%. When the restaurant announces a temporary closure, it can message the 70% directly; reaching the other 30% depends entirely on whether the marketplace chooses to pass on the notice.

What it depends on

• Whether the guest's order runs through a channel the restaurant controls — its own site, app or a phone line — rather than staying inside a marketplace's app
• Whether the restaurant actually captures contact details and consent at the point of ordering, not only a delivery address
• Whether the guest has a reason to come back to the restaurant's own channel rather than reopening the marketplace app — a saved order, a loyalty balance, a faster repeat checkout
• Whether the restaurant uses the contact record afterward — a relationship that is captured but never contacted again decays like an unused list
• Local rules on marketing consent, which decide whether a captured contact can lawfully be messaged again
• How clearly the restaurant's own ordering option is shown next to its marketplace listings when a returning guest searches for it