Core Operations
Customer records built for real service operations.
Bring customer details, booking history, receipts, packages, credits, membership, notes, and follow-up context into one staff-facing profile.
Profile
Operational record
History
Bookings and receipts
Context
Notes and follow-ups
AI role
Summarize safely
Customer profile
Maya Tan
Member / package active
Last visit
12 Jun
Next booking
24 Jun
Visits
18
Wallet
$120
Activity timeline
History before staff action
Follow-up facial
Upcoming / Aileen
Package session used
Receipt linked
Serum + treatment
Counter sale
Review after next visit
Staff-owned
Staff note
Prefers weekday mornings. Check package balance before checkout.
The gap
What fragmented customer context costs
01
Staff search across systems
Customer details, bookings, receipts, notes, and messages should not be scattered.
02
Checkout lacks history
Staff need package, credit, membership, and balance context before completing a sale.
03
Follow-up depends on memory
Retention tasks should connect to customer activity and status.
04
AI is mistaken for the record
Customer truth should live in durable records, not only conversation summaries.
Core capabilities
What the customer record brings together
A staff-facing profile that connects identity, bookings, receipts, notes, packages, and follow-up readiness before the next action.
Customer overview
Show the high-signal fields staff need before acting.
- Contact details, last visit, next booking, and key commercial indicators stay together.
Booking and visit history
Connect CRM to the appointment workflow.
- Past and upcoming bookings show what happened and what is next.
Sales and receipts
Keep checkout history visible from the customer record.
- Receipts and purchase history stay separate from changing catalog prices.
Packages, credits, and membership
Surface retention and commercial context where supported.
- Package balance, credits, and membership context are visible where supported.
Notes and preferences
Support better service quality with controlled internal context.
- Preferences, treatment notes, and sensitive context stay permission-aware where supported.
AI assist boundary
AI can summarize context or draft replies where enabled.
- AI should not invent facts, merge customers, or send follow-ups without approved policy and consent.
How it runs
From profile to staff action
Customer opens
Staff see the customer record before booking, checkout, or follow-up.
History reviewed
Bookings, receipts, notes, packages, credits, and membership context are checked where available.
Action chosen
The team can book, check out, update notes, or follow up from real context.
Record stays current
Operational activity keeps the profile useful for the next visit.
Every step is tracked, every outcome logged — nothing disappears.
The result
Customer context supports daily decisions.
Staff understand the customer without searching across disconnected tools.
Booking, checkout, and follow-up workflows use the same customer context.
Receipts and purchase history remain available for operational review.
AI assists with summaries without replacing source records.
Built for your business
See how it works in your industry
Ready to see how Runbook would work for your business?
We’ll walk you through the workflow, show how enquiries move from message to action, and help you evaluate the best starting setup.