One Client, A Different Standing At Each Venue

A client barred at your first venue booked at your second the following week. The second venue's desk had no idea.

Meanwhile a regular at the first venue rang the second for the first time — and was treated as a stranger. He said so.

⚠️ Multi-venue client records need one record per client, with a separate standing at each venue.

The short version

• One record per client — don't split the same person by venue
• Category per venue — regular here, new there
• Decide in advance whether a ban crosses venues
• Each desk sees its own category, with the client's standing elsewhere easy to check
• Use the same definitions across venues

Why one record

A separate client list at each venue
⇒ the same person exists three times
⇒ bans and do-not-book entries sit on one copy only

⇒ Split records can't stop problems that cross venues.

Why category per venue

Venue A …regular (three times a month)
Venue B …new

⇒ One shared category is wrong somewhere: either B treats him as a regular, or A treats him as new.

Does a ban cross venues?

Option A …barred at one = barred everywhere
Option B …each venue decides (useful if venues are very different)

⚠️ Either works. Not deciding is the dangerous option.

What the desk sees

This venue's category
The client's standing at your other venues
Do-not-book pairs (per entertainer)

⇒ If he's a regular elsewhere: "Thanks for coming to our other place." One line, big difference.

Same definitions everywhere

Regular …twice a month or more / New / Caution / Barred

⚠️ If "regular" means different things at each venue, you can't compare them.

The numbers to keep

One   clients who use more than one venue
Two   bookings at one venue by clients barred at another
Three category counts per venue

⚠️ If Two isn't zero, your ban rule isn't working.

A sheet for the office

────────────────────────────────────
  Multi-venue clients

  Records: one per client
  Category: per venue (same definitions everywhere)
  Bans: cross venues, or not — decided in advance
  Desk sees: this venue's category + standing elsewhere
────────────────────────────────────

Common objections

"Separate lists are easier"

⇒ Easier to fill in. Impossible to protect across venues.

"Per-venue categories are complicated"

⚠️ Same set of categories everywhere; only the value differs by venue.

"We don't want venues seeing each other's data"

⇒ Show category only — not spend or notes.

This week

One   plan merging per-venue lists into one
Two   agree the categories and their definitions
Three decide whether bans cross venues
Four  count clients who use more than one venue
Five  check whether your desks can see standing elsewhere

Doing it by hand, or on a screen

By hand …compare each venue's list on every call
On screen …one client record carrying a category per venue

⇒ In tasteck, each client is one record within the company, and categories can be set per venue (when per-venue categories are switched on). With CTI connected, an incoming call shows the client's category for the venue whose number was dialled. On the booking screen, clients categorised as "NG" at that venue, and do-not-book pairs, show in red.

⚠️ A ban at one venue isn't copied to the others automatically. If bans should cross venues, set the category at each one.

Wrapping up

• One record, category per venue
• Decide whether bans cross venues
• Same definitions everywhere
• Desks see standing elsewhere too

The advantage of several venues is knowing your clients across all of them. Split records throw that away.