Customer Care
Keep the booking. Take care of the customer.
A booked visit still needs a clear conversation. CentralComs sends reminders, handles routine questions, and helps customers tell you when their plans change.
Your team sets the rules and handles the decisions that need a person.
Tomorrow’s visit, confirmed
A full calendar only helps when the visits stay on track.
Missing details and last-minute changes create extra calls and wasted trips. Keep customers informed and make it easy to flag a problem before your team arrives.
Put the details where the customer can find them.
A reminder is useful when it answers the practical questions: which day, what arrival window, and how to reply. Use the actual booking details so the customer knows what to expect before the visit.
- Use the saved appointment date and window
- Make it clear how the customer can respond
How this works: Visit details
Read the appointment information available to the workflow. An arrival window is not a live technician ETA. If the team changes the plan, confirm the updated details before sending a new commitment to the customer.
Chris’s visit details
- Appointment
- Tomorrow · 10 AM–noon
- Work
- Scheduled service visit
- Customer action
- Reply to confirm or ask a question
Let the reminder become a conversation.
Customers often have a useful detail to add when they confirm. Capture the reply and any access information, so your team can arrive prepared instead of discovering a locked gate or a missing contact.
- Keep confirmation and access notes together
- Ask a clarifying question when a detail is incomplete
How this works: Two-way confirmation
A confirmation should reflect the customer’s response, not simply that a reminder was sent. Keep access instructions factual and limited to the job. If a note affects whether the visit can happen, make that issue clear to the team.
A detail the team needs
Catch a changed plan before it becomes a wasted trip.
Give customers a way to say the time no longer works. CentralComs can clarify what needs changing and help with the next step using your scheduling rules, while exceptions remain with the office.
- Ask what changed and which times may work
- Check availability before confirming a replacement
How this works: Changes and questions
A requested change is not a completed reschedule. The original and replacement bookings must be handled through the connected scheduling workflow. If a change needs team approval, communicate that it is awaiting a decision.
A change needs attention
Give the office a clear exception to handle.
When a customer’s request affects the job, keep the facts and pending action together. The office should be able to see what the customer needs and what still has to be decided.
- Separate confirmed details from pending requests
- Keep the original customer message available
How this works: Office context
Use your team’s agreed handoff process for requests the assistant cannot complete. Avoid telling a customer that a time or exception is approved before it is. A clear pending action is more useful than an optimistic promise.
For the scheduling team
- Current visit
- Chris · Tomorrow · 10 AM–noon
- Requested change
- Friday, if available
- Access note
- Use the side gate
A clear path from conversation to booked work.
Your team sets the rules. CentralComs keeps the next step moving.
Send the details
Remind the customer of their visit date and arrival window.
Hear back
Ask for confirmation and handle routine questions in the same conversation.
Keep the team informed
Surface changes or requests that need your staff’s attention.
Keep your tools. Connect the next step.
Know what information comes in, what happens next, and what your office receives.
Your information
Saved appointment details, the customer contact, and current scheduling instructions.
The conversation
Send a useful reminder, capture the reply, and check requests for changes.
Back to your team
Confirmation, access notes, or a clearly marked scheduling request.



Thumbtack

We’ll confirm the available connections, required access, and any steps your team needs to handle before setup.
Frequently asked questions
Can customers actually reply to an appointment reminder?
Yes. A reminder can start a two-way conversation, so the customer can confirm, ask a question, or tell you something has changed. That matters when the reply is more useful than a simple yes: “Use the side gate” or “I won’t be home until noon” may affect how your office prepares for the visit.
The reminder should use the saved appointment details and your instructions. CentralComs can answer routine questions from the information provided and keep new details with the conversation. Questions that need an operational decision should reach the people responsible for the schedule.
What happens if someone asks to move or cancel their visit?
The first step is to understand what the customer wants and which appointment they mean. A request to move to Friday is still a request until the change has been checked and confirmed. CentralComs should follow the scheduling workflow configured for your shop and bring the office in when approval or a manual update is needed.
We’ll agree on how change requests reach your team and who updates the booking. The customer should know whether a new time has been confirmed or the office still needs to review it. That distinction helps avoid two people working from different versions of the schedule.
Can it tell customers exactly when the technician will arrive?
It can share the appointment time or arrival window supplied by your booking workflow. If the saved visit says 10 AM to noon, that is the information the reminder should use. An exact arrival time would need current, reliable information from your operation; it shouldn’t be guessed from the appointment window.
The same applies to late-running jobs and technician changes. During setup, we’ll identify which details are available to CentralComs and which questions need the office. Customers get a more useful answer when the conversation is clear about what is confirmed and who can help with an update.
How does this fit alongside the people who already handle customer service?
Your staff can spend less time repeating appointment details and chasing straightforward confirmations. CentralComs handles the routine conversation, while your people deal with complaints, unusual changes, and decisions that require knowledge of the customer or the work. Those responsibilities should be agreed before the workflow starts.
When a person needs to step in, the useful handoff is specific: the current visit, what the customer asked, and what still needs a decision. We’ll confirm where your office can find that context and how requests reach the right person, so the conversation produces an actionable task.
How do we add reminders without sending customers duplicate messages?
Start by reviewing what your scheduling software and office already send. You may already have a booking confirmation, a reminder the day before, or a manual call on the morning of the visit. Decide which part CentralComs will handle and which messages should remain in your existing process.
We’ll check the appointment source, timing, and reply path as part of setup. This is also the time to assign responsibility for any changes required in your other tools. A clear division of work helps keep the customer informed without receiving several versions of the same reminder from different systems.
