Insights
The Brief
A weekly trade-report. Hero numbers in display serif, twelve regulars ranked by drift, a Pareto sentence, a 7×24 peak-hours grid. Sample mode shows what your Brief will look like before signal arrives.
Restaurant guest CRMKnow your regulars. Without running a CRM.
The customer-data layer of TablePort, written by an editor. A weekly Brief names the twelve regulars going quiet. Loyalty members carry wallet passes that issue themselves. Recognition crosses venues only when the diner says yes, and the diner sees every word you see.
Opt-in, per-business by default · Symmetric transparency · GDPR-erasure cascade
Monday Brief · People to Call3 of 12
- Mara A.12 visits · quiet 6 weeks
- The Okaforsmonthly four-top · missed March
- Priya K.wine list regular · quiet 5 weeks
The diner sees every word you see
What changes the week after you switch
One brief. One inbox. One trust posture.
A brief, not a dashboard.
Three named stories every Monday morning: The Week, People to Call, The Shape of Your Business. You don't interpret twenty-four tiles. You act on twelve names.
Recognized, with consent.
A card fingerprint already exists on every successful payment. We use it carefully: opt-in cross-business identity, GDPR-erasure cascade built into the schema, and a one-tap revoke for the diner.
Symmetric by design.
Every diner sees exactly what restaurants see when they walk in: same sentence, same fields, same data. No hidden customer profile, no third-party data broker.
Inside the suite
One product, not five.
Loyalty, members, the editorial Brief, house accounts, reviews, and the trust posture all share one data substrate and one console suite. No integrations to wire up. No Zapier glue.
Members
The directory
Name, points, lifetime spend, order count, last visit, cadence. Sort, filter, paginate, all server-side. Per-business by default.
Loyalty
The program
Rewards as tier-driven steps: after N orders, or every N points. Day-of-week windows. Discounts land on the check.
Wallet passes
Apple & Google Wallet
Member cards auto-issue to wallet on enrollment. No third-party loyalty-card SaaS in the loop.
House accounts
Corporate billing
Monthly invoiced accounts for catering, repeat corporate lunch, event credit. Balance, credit limit, authorised users.
Reviews
Feedback per venue
Customer feedback aggregated per place. Reply lands on the Comms inbox alongside calls and messages.
Guest Brief Pill (operator view)
Mrs Patel · network regular · 14 visits across 11 restaurants · first time here
Renders
null until the diner consentsThe trust posture
Identity from the payment, not a profile form.
Every successful card payment yields a Stripe fingerprint: a one-way hash, not a card number. Card numbers never touch our servers. When a diner opts in to cross-business recognition, the fingerprint links them across TablePort restaurants. The restaurant sees a tiny pill on the operator screen: “Mrs Patel · network regular · 14 visits across 11 restaurants · first time here”. Never which other restaurants. The diner sees the exact same sentence on /me/tableport, and can revoke or erase in one tap. Symmetric transparency. GDPR DSAR cascade in the schema, not bolted on.
Built right
Privacy is in the schema, not the marketing.
Card numbers stored
0
Stripe fingerprints are one-way hashes. The PAN never reaches us.
Third-party data brokers
0
Cross-business signal is built on payments you already accept.
Cross-business default
Off
Per-business toggle. Per-diner consent on /me/tableport.
DSAR erasure
1 transaction
Fingerprints, billing, network metrics, wallet passes: atomic cascade.
No. Customers is the data layer of the same TablePort that runs your till, your reservations, and your kitchen. The same closed session that posted £142 to your end-of-day also incremented Mrs Patel's cadence. Nothing to integrate. Nothing extra to log into.
Never. There is no advertising business inside TablePort, and we don't share data with brokers. The cross-business identity signal lives entirely on our infrastructure and is gated by explicit per-diner consent. Read the full posture at /trust.
The exact same sentence we hand the operator. Their banded tier, venue diversity, visit count, last visit, and the literal Guest Brief Pill, so they read it word-for-word. A one-tap revoke button and a delete-everything link sit beneath it.
A single transaction wipes fingerprints, billing addresses, network metrics, anonymises memberships, soft-deletes payment methods, and removes the Stripe customer, with an audit row recording when. The cascade is in the data model, not bolted on with a script.
No. We surface customer voice and ticket-level signal, and propose drafts (birthday, lapsed-60d, post-visit-review, network-cross-sell) inside the Communication Center for a human to approve. The Mailchimp or Klaviyo you already use stays in your hands. No autonomous sending.
The Brief, Members directory, Loyalty program, House Accounts, and Reviews are included on every paid tier. Cross-business identity is a per-business setting you choose to enable. There's no extra fee for turning it on.
See your Brief on Monday.
The first Monday brief lands the week after your first 100 paid orders. The trust posture is on day one.