AnyxKey takeaways
- A technician's proposed arrival time is not a customer-confirmed appointment.
- Name who checks the change, who updates the customer and when they report back.
- Ask Anyx to separate recorded facts, commitments and missing confirmations.
- A draft or a generated note does not establish that the customer was notified.
A reschedule appointment message should go out only after the team has checked the new time and named who sends it. In a WhatsApp crew group, record what changed, who confirms the time and who tells the customer. Anyx can review the captured discussion and prepare a draft. A person still sends it and reports back.
This is the Anyx blog. All people, messages and times below are fictional. The chat and checklist illustrate a process to try, not a customer testimonial, a recorded Anyx session or a guaranteed result.
Where does a changed appointment get lost?
An installer says the morning job is running late. Someone suggests moving the next visit. The dispatcher says they will check with the customer. Then the group switches to a parts question. When the technician leaves, the team still needs to know whether the new time was accepted.
The problem is the handoff between three different states: the technician can arrive later, the business approves that proposal, and the customer agrees to it. Writing a new time in the crew group does not establish all three. Even when everybody acts sensibly, the record may omit the final confirmation.
Start with one internal crew group, rather than assuming that an agent can combine every staff and client conversation. Decide who owns the customer relationship. If another group or a phone call contains the answer, have that person report the relevant result without copying private or unnecessary customer details.
What should the team put in the group?
Use a short update with the affected job, the proposed change and the next owner. For the example below, the previous appointment is 9:00, the proposed arrival is 11:30, and Dana explicitly takes responsibility for checking with the customer by 8:30. Those times come from the fictional messages, not an estimate supplied by the assistant.
- NoaToday's service visit was agreed for 9:00. The current job needs longer. I can reach the next job at 11:30 instead.Question8:10
- DanaI'll check whether 11:30 works for the customer and update them by 8:30. It is not confirmed yet.Task8:12
- OmriDo we also need another fitting for that job?Question8:14
- @Anyx what changed, who owns the customer update, and what still needs confirmation? Draft only.
- AnyxNoa proposed 11:30 instead of 9:00. Dana committed to checking with the customer by 8:30. Customer acceptance is not recorded here. The fitting question also needs an answer.
This is an illustrative answer, not a promised exact response. Its important property is the distinction between a proposed time and confirmed customer acceptance. It also preserves the separate equipment question rather than treating it as answered by the scheduling discussion.
If nobody took responsibility, the right next step is to assign someone. Do not fill the gap with the person’s usual role or the last name mentioned. If no deadline was stated, choose one with the team instead of attributing an invented commitment to a colleague.
How can the dispatcher turn that into a checked handoff?
Use this small checklist in the group or your existing job record. It is a template you maintain, not a claim that Anyx creates or synchronizes a work-order system.
| Check | Fictional case | Evidence still needed |
|---|---|---|
| What changed? | Noa proposed 11:30 instead of 9:00 | Whether that arrival estimate is still realistic |
| Who contacts the customer? | Dana volunteered | An explicit replacement owner if Dana becomes unavailable |
| By when? | Dana said 8:30 | A new deadline if the team changes it |
| Did the customer accept? | Not recorded in the example | Dana’s report after the actual contact |
| Is equipment ready? | Omri asked about a fitting | A separate answer from the responsible person |
Check the proposed time
Confirm the crew's availability and who can approve the change. Keep a proposal separate from an agreed appointment.
Prepare the customer wording
Draft the change and the question you need answered. Do not imply the customer has already agreed.
Send and report back
The responsible person uses the usual customer channel, then records whether contact and acceptance actually happened.
For a first pilot, ask for an answer in the group and handle customer contact yourself. Anyx is the group agent: a tagged question gives the team a shared place to review the discussion. This example requires no connected email account, calendar change or automated outbound message.
What should the customer update say?
Keep it short and conditional. Identify the visit through your normal customer conversation, explain the proposed change and ask whether it works. Do not include the internal parts discussion or another customer’s situation.
Draft for review: We need to change today’s agreed 9:00 visit. Our proposed arrival is 11:30. Would that work for you? Please confirm before we treat it as the new appointment.
Check the date, time, recipient and current availability before sending. If 11:30 is only an estimate, say so. If the original appointment can no longer be met, do not leave the customer waiting for an internal note to be generated. Use your normal escalation process.
After contact, Dana might report that the customer accepted, asked for a different day or did not answer. These are different outcomes. “I sent the proposal” is not “the customer accepted,” and “I’ll call” is not “I called.” Preserve that distinction when updating the crew.
Where do AI Notes fit after the immediate change?
Use a tagged group question for the immediate check. Separately, an Anyx note can help the owner review captured decisions, action items and open questions. According to How AI Notes work, notes go to the account and email, not into the group. They are scheduled outputs, not an urgent dispatch alert.
Compare the note with the messages before relying on a commitment. If contact happened by phone, the group needs a clear follow-up report for that result to appear in its captured conversation. An older open item may carry forward; check whether it was resolved elsewhere before chasing it again. Our unanswered-questions guide includes a labelled founder-owned example of a scheduling update and an older question appearing together. That case is not evidence that this fictional dispatch process has been tested.
For a longer change history, use the decision-log guide. For the distinction between a private request and a shared answer, see personal or group assistant.
How do you know the pilot helped?
Try one changed appointment and inspect four things: whether the assistant preserved the original agreement, kept the new time conditional, named only an explicit owner, and left missing customer acceptance visible. Then ask the dispatcher whether the checked answer helped them decide the next step. A generated response alone does not establish value.
Stop and correct the record if the assistant invents an owner, mixes jobs or calls a proposal confirmed. Anyx may have incomplete captured history and cannot establish what happened in a phone call from silence in the group. This workflow promises neither timely customer contact nor fewer missed visits. Its practical test is narrower: can the team see the changed proposal, the owner and the remaining confirmation clearly enough to act?
FAQ
Can Anyx tell the customer automatically when a technician is late?
This workflow does not automate customer contact. Ask for a draft, have the responsible person check the time and recipient, then send it through your normal customer channel. A generated draft is not a sent message.
Does a proposed arrival time replace the appointment?
Not by itself. Check who can approve the change and whether the customer accepted it. Keep the old agreement and the new proposal distinct until the responsible person confirms the change.
Are Anyx AI Notes posted into the crew group?
No. AI Notes are account and email outputs. Send to my WhatsApp is a manual action to your private chat with Anyx. Tagged group answers and configured group routines are separate outputs.
Can a missing confirmation prove that nobody contacted the customer?
No. Contact may have happened by phone or outside the captured conversation. Ask the owner to confirm what happened instead of declaring that the customer was not told.