Which customers a venue should actually record

A cafe serves several hundred people a week, and keeping a record of each one would be both impossible and pointless. About forty relationships do deserve a record. Most venues keep those in a diary, a phone and three inboxes, which works until the person holding the phone is away for a week. The four groups below are the whole list. Everybody else is a transaction the till already handles.

The four groups worth recording

• Function and event customers, who book a room and spend more in one evening than a busy Saturday.
• Catering and order ahead customers, usually offices, who repeat.
• Suppliers, with their account numbers, delivery days and reps.
• Regulars the venue actually knows, where a name and a preference change the service.

Those four are relationships rather than transactions, and a relationship needs somewhere to live. Each one costs the venue money when it goes wrong. A lost function, a catering order missing its gluten free platter, a supplier nobody could ring on a Sunday. Diract CRM keeps all four in one list with a classification on each record, so one search finds anybody. A field asking for a supplier never offers a birthday booking, and a field asking for a function customer never offers the roaster.

A function enquiry is the most valuable call of the week

A birthday for thirty is worth more than most Saturdays, and it usually arrives as a voicemail or a message on a social account. Whoever picks it up answers warmly and then forgets, because nothing recorded the promise. Diract CRM keeps those as enquiries with an owner and a next action, which is the whole mechanism. One name per enquiry, set at intake, is the difference between a booking and a voicemail somebody meant to return. Our guide to functions and venue hire covers the arrangement that makes the night profitable.

The money belongs to the event, not the customer

A function's deposit, minimum spend and balance belong to that event. A customer who books twice a year has two sets of those, and merging them produces a number describing neither. Diract CRM keeps the money on the booking with the customer linked beside it. A table reservation for Friday is an event too. The office that books a long lunch quarterly is the relationship behind it. Recording both, linked, lets a venue recognise the second booking as a returning customer rather than a new name.

Office caterers repeat, so history pays

An office ordering sandwiches monthly has dietary requirements, a delivery time and a person who signs for the delivery. Recording that once means the second order takes a minute and arrives correct. Arriving correct is the entire reason they keep ringing, and one wrong platter can end a year of orders in a morning. Diract CRM repeats a standing order so it appears in the kitchen's list ahead of time, with the customer and the lines attached. Our guide to catering customer records covers what the first order should capture.

Suppliers belong in the same list

The produce supplier's delivery days, the roaster's rep and the account number all get looked up under pressure. A drawer cannot answer at six in the morning, and neither can a phone in somebody's pocket at home. Our guide to suppliers and subbies in the CRM covers keeping those beside the customers. The classification does the separating, so a supplier never appears where a customer belongs.

A regular is a name, not a loyalty scheme

A venue does not need points to remember that table four takes oat milk and dislikes the seat near the door. Twenty names with a preference beside each change the service more than any app installed on a customer's phone. Staff turn over, and a preference held only in somebody's head leaves with them. Our guide to regulars covers recording the handful that matter without installing anything.

The list stays small on purpose

A venue that starts recording every walk-in ends with ten thousand useless records and stops trusting the list. Forty to two hundred records, each of them a real relationship, is a list somebody will actually keep current. The discipline is the feature here. A short list gets read before a quiet month. Last year's function customers and the offices that stopped ordering are the two lists worth calling in a slow fortnight. Neither is available to a venue whose customer records are a diary and a phone.

How a venue uses Diract CRM

Diract CRM keeps function enquiries, catering customers, suppliers and named regulars in one list, separated by classification. A function's deposit and balance sit on the booking rather than the customer. A standing catering order repeats on its own schedule, and the kitchen sees it ahead of time with its lines attached. One search covers all four groups, which is what a venue needs at eight in the morning.

What to change first

• Four groups get records: functions, catering, suppliers and named regulars
• Function enquiries carry an owner and a next action
• A catering customer's requirements record on the first order
• Suppliers sit in the same list, with account and delivery details
• Classification separates the groups rather than four systems
• A function's deposit and balance belong to the event
• The list stays small enough that somebody keeps it current