BOOKING TO CRM
Keep the appointment connected to the person it was made for.
Carry customer details and a CRM contact association with the booking, so the next visit can start from recognizable customer context.
Please discuss the revised scope during the consultation.
A booking is also a customer interaction
A name in an appointment list is useful, but the team often needs to understand who that person is and whether they already have a relationship with the business. Tsumira’s booking path keeps customer name, contact details and a contact association alongside the service and timing. The relationship can then continue through the customer record rather than being rebuilt from an isolated appointment each time.
Capture the details needed for this appointment
The booking carries the customer’s name and reading, email or phone where supplied, and the relevant note. These fields remain part of the appointment context, explaining for whom the promise was made. Keep the information factual and sufficient for service preparation and communication. A booking note should explain the specific visit; it need not become a copy of every private detail the business knows about the customer.
- Customer name and reading
- Email and telephone information
- Appointment-specific note
Use defined identity matching, not a universal guarantee
The booking creation flow uses the shared customer matcher against the loaded CRM contact pool and can create a customer contact when no match is found. The contact association is saved with the appointment. Accurate identifiers help the process, but the presence of a matcher is not a claim that every changed name or shared telephone resolves perfectly. Review unclear identity before relying on a historical customer association.
- Shared customer-matching rules
- Contact creation when appropriate
- Saved appointment-to-contact association
The appointment and the customer record keep separate access rules.
Continue into authorized customer work
A linked contact can help the team find related customer context from the appointment. The booking has its own state and conversation, while the customer record has its own activity and permissions. A cancelled appointment is still a record of an earlier promise; cancelling it does not mean the customer should be erased from the CRM. Keep changes to service timing separate from judgments about the relationship itself.
- Customer reference from the booking
- Separate appointment and CRM context
- Cancellation does not erase the customer
A concrete workflow
Collect the booking details
Use the customer’s actual name and reliable contact information for the appointment.
Create through the booking flow
The supported path matches or creates a contact and saves its association with the confirmed appointment.
Check the relationship
Open the visible customer context and resolve uncertainty before using earlier history.
Continue service and follow-up
Keep appointment changes and the relevant customer communication in their proper record context.
An illustrative working example
Illustrative workflow: a returning consultation customer
A customer books a further consultation using their usual contact details. The supported creation path can recognize the existing contact and keep that association on the appointment. The service colleague reviews the visible customer context before preparing. If details have changed or the association is unclear, they clarify identity rather than assuming the booking proves which person owns every earlier note.
Questions about this topic
Does a booking keep a customer reference?
The appointment model carries a CRM contact association, together with its own customer details and service information.
Can a first-time customer become a contact?
The supported creation path can create a customer contact when the shared matcher does not find an existing one.
Is matching a promise that duplicates never occur?
No. Real-world changes, limited source data and shared identifiers can require review. Check uncertain associations rather than treating them as identity proof.
Does cancellation delete the CRM customer?
Appointment cancellation changes the booking lifecycle. It is not a command to erase the customer’s CRM relationship or history.
Explore connections around this workflow.
Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.
HubSpot
Workflow concept: Review booking contact identity before choosing an existing CRM record.
Salesforce
Workflow concept: Compare exported customer identifiers without guessing ambiguous matches.
Google Sheets
Workflow concept: Resolve duplicate booking contacts in a reviewed customer mapping table.