Booked call reminders with a saved Wallet pass

From confirmed booking to a saved appointment

Start with the booking record: who booked, which appointment they booked, its start time and time zone, and the correct meeting destination. The connected workflow creates a ShowFi claim link. The prospect opens that link and chooses to save the pass. Sending the link does not save it automatically.

Offer the Wallet option on the booking confirmation page, where the prospect is already taking action. Keep the meeting link and calendar option available there too. A confirmation message can provide a return path if the prospect leaves before saving.

Example: a 30-minute consultation

This example describes a configuration to test, not a measured customer result. A prospect books a consultation for October 6 at 2:00 p.m. America/Chicago. Their confirmation page offers a Wallet pass with the consultation title, appointment time, and meeting link.

• Booking: October 6, 2026, 2:00–2:30 p.m. America/Chicago.
• Pass: the same appointment time and attendee meeting destination.
• Reminder settings: review the one-hour and fifteen-minute reminders and the start-time reminder.
• Change test: move the booking to October 7 and verify the saved pass and calendar invitation separately.

Set up the booked-call workflow

Connect the GoHighLevel location to the correct ShowFi workspace, or use a supported Make appointment workflow for your booking tool. Publish the appointment template before sending live contacts through it. Use the linked GoHighLevel guide for the specific webhook configuration.

• Map the contact, appointment identifier, start time, time zone, and join destination.
• Trigger pass delivery from the confirmed booking. Configure reschedule and cancellation events as part of the same workflow.
• Place the resulting attendee claim link on the confirmation page or in the contact’s confirmation message.
• Save a test pass on an iPhone and an Android phone. Open its meeting link and check the displayed time before launch.

Handle changes before the reminder goes out

Use the booking system as the source of appointment status. A reschedule needs to reach ShowFi with the correct appointment identity so that the existing booking can be updated. Updating the calendar alone is not a test of the Wallet workflow.

Test cancellation separately: confirm the appointment is canceled in ShowFi and that future reminders for that booking stop. In a reusable appointment flow, the pass can remain in Wallet after cancellation. A remaining pass does not mean the canceled call is still scheduled.

What the prospect sees on their phone

Apple Wallet and Google Wallet have different save screens and notification controls. The prospect must finish the native save. A claim-page visit or an Apple pass download alone does not establish a confirmed save.

ShowFi supports reminders one hour before, fifteen minutes before, and at the event start; the first two can be configured. Phone settings, Focus, connectivity, and provider processing affect notification visibility. Keep the original meeting link accessible in the confirmation and calendar.

Measure bookings, saves, and attendance separately

Choose a booking cohort and a reporting cutoff. Count eligible confirmed appointments, confirmed Wallet saves, and attended calls as separate steps. Use the booking system or CRM’s attendance outcome for attended calls; a Wallet save or join-link click is not attendance.

For a before-and-after comparison, keep the lead source, appointment type, booking lead time, and attendance definition consistent. If those change, report them alongside the result. Do not attribute every movement in show rate to the pass.

Decide whether this fits your sales workflow

ShowFi fits teams that want a saved mobile appointment pass and help connecting the workflow. Your calendar, CRM, and email or SMS provider still handle their respective parts of the booking journey. Check current plan and usage details on the pricing page, and include reschedule and cancellation testing in onboarding.