Case study10 min readUpdated 7 Aug 2026

A Bangkok mid-to-high-end restaurant goes digital, part 5: build a customer base profile — make a guest who came once feel like a regular

Orders hold steady; the next step keeps the guest in memory: record tastes, preferences, and birthdays — with consent and in line with privacy rules. A guest who came only once, on their second visit, gets recognized by the server and treated like a regular. It's the lowest-cost starting point for better experience and return visits.

Last chapter got orders to the kitchen. This one turns in a different direction: an order is the record of “this service” — and the restaurant also wants to keep “who this guest is.”

Regulars live in memory, and memory disappears

Customer relationships at this restaurant work like this today:

  • Servers recognize regulars by face and carry the conversation by memory: “your usual dish”, “you like the window table”;
  • After two or three visits, servers start remembering preferences, and guests start feeling “this place gets me”;
  • But change the server, change the shift, or let a guest come back after months — and the memory is gone.

The owner is clear: a mid-to-high-end restaurant’s competitiveness runs largely on being remembered. Guests pay more for experience, and “you still remember me” is a very expensive part of that experience. But he’s also clear that relying on servers’ memory is unreliable — people change shifts, forget, and leave.

What this step does: a customer base profile

This step builds a basic customer profile, saving only what is genuinely useful and what the guest agrees to share:

  • Tastes and preferences: what they don’t eat, what they like, allergies, a preference for the window or a quiet table;
  • Birthday: used for a greeting or special treatment, within compliance;
  • Basic contact: name, phone or LINE, for booking confirmation and necessary contact.

The core is not the profile itself — it’s that “being remembered” can be sustained. On the guest’s second visit, the server can see the preference and say “last time you had the tom yum — same again?” — making a guest who came once feel treated like a regular.

Saving customer data isn’t “the more the better” — it has boundaries and consent:

  • Get consent: collect data only when the guest volunteers it, and be clear about what it’s used for (like remembering taste preferences, or a birthday greeting);
  • Keep only what’s useful: no collecting for the sake of collecting; every field maps to a real hospitality use;
  • Honor deletion: guests have the right to know what’s stored and to ask for deletion — the restaurant must be able to respond;
  • Not a full CRM: this is basic data servers can use at ordering and hosting, not marketing blasts, profiling, or cross-branch customer management.

Why this step matters most for a mid-to-high-end restaurant

  • Differentiated experience: street-side shops compete on price; mid-to-high-end restaurants compete on experience. Being remembered is the heart of experience, and the reason guests come back;
  • Return visits are cheap: making a one-time guest come back is far cheaper than developing a brand-new guest;
  • The profile is the base for later membership: who gets a membership card, who gets invited to stored value, how they’re cultivated — all built on this profile.

What this phase was deliberately not

  • Not a full CRM. No profiling, no marketing automation, no cross-branch customer sharing.
  • No marketing blasts. The purpose of collecting is first to improve hosting experience, not to mass-message.
  • No membership system. Membership cards and stored value are the marketing upgrade that comes later, not this step.

The server’s daily hosting gains a reference they can look up. But whether this phase lands depends on whether servers want to use it — so the data must be light, must have an on-the-spot use, and must make the server feel “this helps me do my job better”, not “one more form to fill”.

What entering the next step requires

Once the customer profile is built, the owner watches:

  • whether guests are willing to leave data, and whether servers can use it naturally during hosting;
  • whether “being remembered” actually happens — on a guest’s second visit, does the guest feel a difference;
  • whether the accumulated profile is enough to support designing the next membership plan.

Once the profile holds steady, the next step is the marketing upgrade. Part 6 is about membership cards, stored value, and social-media operations.

Boundary matters: the customer profile and CRM system belong to separate business-system projects, not a standard website package. The membership stored value and social-media operations in this series are likewise separate projects with their own scope; collecting and using customer data must comply with privacy rules and require consent.