Keep the appointment moving.
Collect the request, check the diary and keep changes with the right person. A cancellation or new time should not disappear in a message thread.
One request. Both dates.
Keep the original booking until the new one is confirmed.
Keep your diary and conversations connected.
Customer conversation
Team diary and documents
Booking system, subject to access
A change of plan should reach everyone.
See how the request reaches the person who can confirm it.
Could I move my Thursday appointment to Friday?
9:41Team handoverReschedule ready for review
Collecting the request- Current slot
- Thursday · 11:00
- Requested slot
- Friday · 14:00
- Duration
- 45 minutes
- Owner
- Reception
Reception confirms the new slot before releasing the old one.
Read the full conversation
- Customer: Could I move my Thursday appointment to Friday?
- Assistant: I’m the team’s AI assistant. Friday at 14:00 appears available for your 45-minute appointment. Would that suit?
- Customer: Yes, Friday at 2 works.
- Assistant: Thank you. The team will confirm the change. Your Thursday appointment stays in place until then.
The customer and the diary agree.
When a time changes, the previous slot, proposed replacement and confirmation state are visible together. The team can see what still needs a decision.
Find a suitable time
Check service duration, staff and availability against the actual diary before offering a slot.
Handle the reply
Capture a confirmation, cancellation or reschedule request and prepare the corresponding update.
Follow up within the rules
Agree consent, contact timing, opt-outs and message approval before enabling reminders or recall sequences.
Your team stays in control.
Reminders, recalls and cancelled-slot campaigns are separately scoped. A request is not a confirmed booking until the system accepts the change.
Connections and setup
The example shows a proposed workflow. Connections, permissions and acceptance checks are agreed for your systems before a pilot.
API access and your plan determine what can be connected. Tool logos identify possible systems, not a partnership.
Map one real handover
A working sheet for the source, next action, owner and exception at each step.
Open the resourceBefore we get started.
Who stays in control?
We start with supervised work: Knot prepares, a named person reviews. Any permission to send, book or update a record is agreed action by action and tested before it is enabled.
Can we keep our existing software?
That is the starting point. We check API access, your subscription, permissions and the records the workflow needs. A logo here identifies a possible tool, not a preinstalled connector or a formal partnership.
Are recalls and re-engagement ready to switch on?
They need a separate scope: the trigger, source data, customer permissions, frequency and stopping rules. We do not present every proposed follow-up as a live feature.
Your business.
A place to start.
Start with your company website, then tell us what you’d like to improve. We’ll find a useful resource or a next step.
We read public pages and use AI to suggest Knot resources. Don’t include confidential information. Privacy