Duplicate Appointment Requests: Check Before Canceling

Two similar appointments are not automatically duplicates. Compare the client, service, provider, time and status, then confirm what was intended before canceling either record. A repeat click, an alternative request and two genuine visits can look similar in a busy calendar.

The aim is one clear outcome for each intended visit, with the client and staff using the same current information.

Compare the records directly

Open both appointments and write down what matches and what differs. Check the contact details rather than relying on the displayed name alone. Two clients may share a name, and one person may be arranging separate visits.

Useful questions include:

• Are the appointments for the same service and provider?
• Do they overlap or represent different days?
• Is one Pending and the other Accepted?
• Was a time change discussed outside the booking system?
• Does the client expect one visit or more than one?

Use client appointment history for context, but keep the decision tied to the actual bookings.

Distinguish common situations

An illustrative client requests Tuesday at 10:00, then requests Wednesday at 11:00 after realizing Tuesday will not work. Both requests may remain until the business handles them. The second request alone does not establish that the first was canceled.

Another client may book two different services for separate occasions. Similar names and prices do not make those appointments duplicates.

A third situation is an external calendar event appearing twice while FindSlot contains only one appointment. Investigate that display and account connection separately; canceling the source booking would change a real visit to solve a calendar-view question.

Ask a short clarification

Suggested manual message:

We can see requests for [first date and service] and [second date and service]. Did you intend to arrange both visits, or should we keep one? Please tell us which arrangement you want us to review.

Avoid telling the client that a time is confirmed unless the current state supports that statement. Review the request and confirmation distinction when drafting a response.

Assign one person to handle the clarification so multiple staff members do not make competing changes.

Save and verify the agreed outcome

Use permitted appointment controls to record the resolution. Check the booking that remains: service, provider, date, time and status should match the agreed visit. Check the other record's actual outcome instead of leaving it active with a note saying "duplicate."

Supported recent changes may appear in the Activity Log. Use the available history to understand what happened, rather than assuming it records every possible action.

If a connected calendar is involved, allow processing and check it after the FindSlot record is correct.

Reduce avoidable confusion

Explain what happens after a booking request and provide a recognizable contact route. A client who cannot tell whether a submission worked may try again. When moving a visit, complete the actual reschedule rather than asking for another booking without resolving the original.

Can a missed appointment be used to clear a duplicate? Use the state that accurately describes what happened; an unwanted duplicate is not evidence that the client failed to attend.

What if the customer does not reply? Follow your business's review process and keep an owner assigned to the unresolved request.

Explore FindSlot's booking workflow and make the final appointment state the reference for both staff and clients.