Loyalty event definition map
Separate check-ins, appointments, completed jobs and redemptions before measuring a loyalty program. Use an event-definition worksheet.
No signup. Enter reference codes, add records and download a CSV. Entries stay in the browser tab. Filled fields do not establish completion, approval or compliance.
| Event name | What proves it occurred | What it does not prove | Source record | Counting rule | Review owner |
|---|---|---|---|---|---|
| Check-in | Recorded arrival | Completed paid service | Program record | Once per defined visit | Manager |
- Starting values are fictional examples, not customer records.
- Keep confidential evidence in your approved business systems. Record only a reference here.
- Complete each row from observed evidence. A completed worksheet does not certify legal compliance or provider compatibility.
- Export your CSV to approved storage before leaving this page.
A customer checks in, asks a question, then leaves without buying. Another pays for a future appointment but doesn’t visit today. If your loyalty report treats both as completed sales, the program will appear more successful than the business records support. Define each event before you measure results or reward staff for growing activity counts.
Use with this guide
customer loyalty workspace
Continue with customer loyalty workspace.
Books workspace
Continue with Books workspace.
Measure a repair-shop loyalty program by repeat visits, not enrollments
Enrollment is the start of a record. Compare completed repeat visits only after the selected customers have the same defined opportunity to return.
Give each event a precise meaning
Keep enrollment, message sent, check-in, appointment booked, service completed, payment received, and reward redeemed separate. One visit can trigger several events, but they don’t mean the same thing. A sent message doesn’t prove it was delivered. And a booking doesn’t prove the customer showed up. Label each event based on what your systems can actually confirm.
The customer loyalty workspace shows enabled check-ins, rewards, and message activity. BlueFinch's public product facts explicitly caution that a sent message doesn’t prove a customer came back. Keep that same discipline across your reporting. Don’t turn a handy count into a revenue measure just because it’s sitting on the overview screen.
Sources for this section: BlueFinch: customer loyalty
Follow one illustrative visit
A tint customer might check in for a quote, come back two weeks later for installation, then redeem a reward at pickup. That’s at least two visits, one completed installation, and one redemption under the chosen definitions. If the program counts both check-ins as installations, the reported conversion and average sale become misleading.
A machine-shop buyer might never physically check in. All of their orders arrive remotely, so don’t let a loyalty tool that emphasizes visits erase their completed work from your business performance report. Pick measures that fit how the operation runs, and be clear about what the program doesn’t track. Missing coverage doesn’t mean zero customer activity.
Connect the right source records
Use the scheduling system for appointments, the job record for completed service, and the payment provider for verified collections. The Books workspace helps organize supported financial records, subject to review and reconciliation. One loyalty event does not prove all those outcomes. Keep internal references so staff can trace an aggregate figure back to its source.
For an illustrative month with fifty check-ins, thirty-five completed jobs and twenty reward redemptions, report those as three distinct counts. Don’t say the program generated fifty sales or twenty extra jobs. Some customers may have redeemed rewards on visits they would’ve made anyway. To measure extra behavior, you need a more careful comparison.
Make the worksheet an operating definition
The worksheet asks what proves an event, what it doesn’t prove, where the source lives, how it’s counted, and who owns the definition. Sort out duplicate events, reopened jobs, and canceled visits before putting a total in a monthly report. Keep personal records in approved storage. Use aggregate numbers here.
Keep communication permissions separate from event counts. A customer checking in hasn’t automatically asked for promotional messages. The FTC's email guidance protects members’ opt-out rights, and BlueFinch requires customer permission and channel readiness before follow-up. Your activity report should stay accurate without signing every visitor up for marketing.
Document whether a repeated check-in on the same day represents a second visit, a correction, or a duplicate. Then apply that rule consistently. Don’t change it just to make the monthly total look better. If your system can’t automatically tell these cases apart, keep that limitation visible and review the exceptions before showing the count to the owner.
At your next owner meeting, pick one business question and bring the evidence that answers it. Want to know if customers come back? Check completed return visits over the right period. Want to know if customers use a reward? Check redemptions and what they cost. Clear definitions help you get more from the included loyalty software. Your team can see which decisions the numbers support and which need another record.
Sources for this section: FTC: commercial email requirements · BlueFinch: customer loyalty
Primary sources
BlueFinch last reviewed these sources on October 23, 2026. Check the linked sources for current requirements and product details.
Use this page for general business information. It is not legal, tax, or accounting advice.