Cafe CRM
In a cafe you see the same person three times a week but their name appears nowhere in the system; the loyalty card is in their pocket and the preference is in the barista's memory. The day the staff change, that memory goes too, and the customer has to explain themselves all over again.
A regular customer is a record; the preference note, the visit frequency and the last visit date are its fields. The campaign goes to the list filtered out of those fields.
- Record regular customers with their preferences and visit history, so the information stays in place even when staff change
- Send the loyalty status and the campaign to a filtered list, and write a separate message to those who have not been in for a long time
- Tie group bookings for meetings and celebrations to the calendar, and keep the table and time on the record
- Follow office and company orders as repeating orders under the account, and turn the delivery day into a task
| Customer Card | A regular customer is a record; the preference note, the visit frequency and the last visit date sit in its fields. |
|---|---|
| Loyalty and Campaign | A campaign is sent to a list of records pulled out with a filter; who received which message is visible on the customer card. |
| Table Booking | A booking is a record with date and time fields; the number of people, the table and the celebration note sit on the same card, and the day's reserved tables are read from a single list. |
| Corporate Order | Offices and companies are each an account record; the repeating order sits under the account, and the delivery day is opened as a task. |
A cafe's revenue comes less from the passing crowd than from the regular who drops in a few times a week; but that customer is not recorded anywhere. The campaign announcement goes to everyone at once, and the person who has not been in for months gets the same message as the one who came yesterday. The request from someone booking a table for a meeting or a celebration is written in a notebook, and the office order stays in a message thread; both end up depending on whoever happens to be on shift that day.
Rapitek CRM keeps every customer as a record together with their preferences and visit history; the campaign goes to a list filtered out of those records, and a separate message can be written to someone who has not been in for a long time. Because a group booking is a record with date and time fields, it lands in the calendar rather than in the shift notebook; and the office order is followed as a repeating order under the account. Across several branches the same customer carries the same record, and what they bought where is visible from one place.
The scope of the plans and the items priced separately are written on the pricing page.
