Last updated July 21, 2026
How to Set Up Automated Peek Pro Text Message Reminders
Automatically send booking confirmations and pre-trip SMS reminders through Birdeye when a customer books through Peek Pro. Keep reminders synchronized when reservations are updated, cancelled, or rescheduled.
Clear answer: how Peek Pro text reminders work
Peek Pro text message reminders are not just a single text blast. The clean setup is a reservation-aware workflow: booking platform to webhook to Bizinga integration to Birdeye contact and booking fields to automated SMS workflow. That lets the reminder respect the booking status, activity time, guest phone number, location, and whether the reservation has changed.
For tour and activity operators, this means you can send a booking confirmation after reservation creation, schedule a reminder roughly two days before the activity, send same-day updates when appropriate, stop messages when a reservation is cancelled, reschedule reminders when a guest rebooks, and send a post-trip review request after the activity is completed.
Need help implementing Birdeye with your booking platform?
ConvertLocal helps tour operators connect booking events, map fields, test reminder logic, prevent duplicates, and launch customer communication workflows.
How the integration works
The guest completes a reservation through Peek Pro.
The booking platform sends the booking event to the integration endpoint.
The integration checks booking ID, status, customer fields, activity, date, time, and location.
The existing guest contact is updated where appropriate instead of creating duplicate contacts.
The guest gets a confirmation message when the booking is active and eligible.
The reminder is scheduled relative to the activity start time and only sends if the booking remains active.
Cancelled bookings stop pending reminders. Rescheduled bookings move reminders to the new date.
After the activity is completed, Birdeye can request a review where the workflow is enabled.
What the booking platform does
Peek Pro remains the reservation system. It stores the booking, activity, customer, date, time, status, and operational details.
What ConvertLocal configures
ConvertLocal connects the booking events to Bizinga, validates the data, maps fields to the correct Birdeye location, and helps build the SMS workflow rules in Birdeye.
Booking confirmation text workflow
A confirmation text should send when the booking status changes to confirmed, a valid mobile number exists, the booking has not already received a confirmation, and the booking is not cancelled. The confirmation should only be sent once per active reservation unless the operator intentionally sends an updated confirmation after a meaningful change.
| Rule | Why it matters |
|---|---|
| Send once per active reservation | Prevents duplicate confirmations from repeated webhook events. |
| Use the booking ID or UUID | Keeps updates tied to the original reservation. |
| Require a valid mobile number | Avoids failed sends and bad customer records. |
| Exclude cancelled bookings | Prevents confusing messages after a cancellation. |
Two-day reminder workflow
A common setup sends the reminder about 48 hours before the activity start time. The reminder should only send when the booking remains confirmed, the activity is still in the future, the customer has a valid mobile number, the customer has not opted out, the reminder has not already been sent, and the booking has not been cancelled or moved.
If a booking is created less than 48 hours before the activity, the operator can choose a shorter reminder window or rely on the confirmation message. The workflow should also account for time zones, same-day activities, imported future bookings, and late booking changes.
Cancellation and reschedule handling
When a booking is cancelled
- Change the booking status to cancelled.
- Cancel pending confirmation or reminder jobs for that booking ID.
- Do not send a two-day reminder.
- Do not send an automatic review request.
- Optionally notify the business team.
- Only send a customer cancellation text when approved by the operator.
When a booking is rescheduled
- Find the original reservation using the external booking ID.
- Update the activity date and time.
- Cancel the original scheduled reminder.
- Schedule a new reminder relative to the new activity time.
- Avoid creating a second active reminder for the old date.
- Optionally send a reschedule confirmation.
Peek Pro webhook setup
Peek Pro webhook access and configuration may depend on the operator’s account and approved integration access. ConvertLocal configures the approved webhook path to send booking data into Bizinga, including available fields such as customer name, mobile phone number, activity name, date, time, booking status, booking identifier, and location or meeting instructions when available.
The workflow should account for new bookings, updated bookings, cancelled bookings, and rescheduled bookings. The exact event names and fields should be confirmed during setup rather than assumed.
How to Set Up Booking Text Reminders in Birdeye
1. Connect the booking platform
ConvertLocal configures the Peek Pro webhook to send booking events to Bizinga. The payload should map to the right Birdeye location and include mobile number, name, booking ID, activity, start date, start time, and booking status.
2. Create or update the contact
Search for an existing Birdeye contact using the mobile number and available identifiers. Update existing contacts when appropriate. Store the booking platform, external booking ID, activity, date, time, status, and location.
3. Trigger confirmation
Send the confirmation when the booking is active, has a valid phone number, and has not already received the message. Do not treat every update as a new booking.
4. Schedule the reminder
Schedule the two-day reminder relative to the activity start time. Before sending, re-check status, opt-out, phone validity, date, and send history.
5. Handle changes
Cancellation stops pending messages. Reschedules update the date, remove the old reminder, and schedule the new reminder.
6. Send review requests
Only send a review request after the activity has been completed. Do not send if the booking was cancelled, unresolved, moved, or did not happen.
Screenshots and privacy
No verified Peek Pro setup screenshot is being published on this page. Instead, this guide uses a workflow diagram and field-mapping explanation so the page does not expose private webhook URLs, customer records, booking IDs, API credentials, or account details.
Example text-message templates
These are customizable examples, not legal or compliance advice. Confirm consent, opt-out handling, registration requirements, and message timing before sending production SMS.
Booking confirmation
Hi {{first_name}}, your {{activity_name}} with {{business_name}} is confirmed for {{activity_date}} at {{activity_time}}. Reply here if you have any questions. {{booking_or_meeting_link}}
Customizable example. Review message timing, consent, opt-out handling, and compliance requirements before launch.
Two-day reminder
Hi {{first_name}}, your {{activity_name}} is coming up on {{activity_date}} at {{activity_time}}. Please arrive {{arrival_minutes}} minutes early. Details: {{meeting_link}}
Customizable example. Review message timing, consent, opt-out handling, and compliance requirements before launch.
Same-day reminder
Your {{activity_name}} with {{business_name}} is today at {{activity_time}}. Please meet us at {{meeting_location}} and arrive {{arrival_minutes}} minutes early.
Customizable example. Review message timing, consent, opt-out handling, and compliance requirements before launch.
Reschedule confirmation
Hi {{first_name}}, your reservation has been updated. Your new {{activity_name}} date and time are {{activity_date}} at {{activity_time}}.
Customizable example. Review message timing, consent, opt-out handling, and compliance requirements before launch.
Cancellation confirmation
Hi {{first_name}}, your {{activity_name}} reservation for {{activity_date}} has been cancelled. Reply here if you need assistance.
Customizable example. Review message timing, consent, opt-out handling, and compliance requirements before launch.
Weather or operational update
Hi {{first_name}}, we have an update regarding your {{activity_name}} on {{activity_date}}. {{operational_update}} Please reply or call {{business_phone}} with questions.
Customizable example. Review message timing, consent, opt-out handling, and compliance requirements before launch.
Benefits for tour and activity businesses
Fewer missed arrivals
Pre-trip texts can remind guests about arrival time, meeting point, parking, waivers, and what to bring.
Cleaner communication
Guest replies can flow into a shared inbox instead of getting lost across staff phones and inboxes.
Better review timing
Post-trip review requests can send after the experience instead of at booking or during the wrong moment.
Common mistakes to avoid
Treating every webhook as new
Updates, cancellations, and duplicate webhook deliveries should not create new workflows.
Ignoring the booking ID
The external booking ID or UUID is what keeps confirmations, reminders, and reschedules tied to the same reservation.
Sending after cancellation
Cancelled bookings should stop pending reminders and should not receive automated review requests.
Missing time zones
A reminder scheduled in the wrong time zone can arrive too early, too late, or after the activity starts.
Importing old bookings too aggressively
Historical reservations should not receive new-booking confirmations unless explicitly approved.
Skipping production testing
Test new bookings, updates, reschedules, cancellations, missing numbers, invalid numbers, duplicates, opt-outs, and multi-location routing before launch.
Technical testing checklist
- New test booking
- Booking update without date change
- Booking reschedule
- Booking cancellation
- Missing phone number
- Invalid phone number
- Duplicate webhook delivery
- Existing Birdeye contact
- Different time zone
- Booking less than 48 hours before activity
- Booking after normal reminder time
- Multi-location booking
- Customer opt-out
- Imported historical booking
- Imported active future booking
- Correct Birdeye location and message history
Related integrations and internal links
Frequently asked questions
Can Peek Pro send automatic text reminders?
Peek Pro manages bookings. Automated SMS reminders can be configured by sending approved booking events through a webhook into Bizinga, then mapping the guest and reservation fields into Birdeye.
How do Peek Pro webhook text reminders work?
A Peek Pro booking event sends booking data to Bizinga. Bizinga validates the booking identifier, status, guest phone number, activity, date, time, and location where available, then updates Birdeye and triggers the right workflow.
Can I send a confirmation text after a Peek booking?
Yes, when the booking is active, the guest has a valid mobile number, and the confirmation has not already been sent for that reservation.
Can I send a reminder two days before the activity?
Yes. A typical setup schedules a reminder about 48 hours before the activity and checks that the reservation is still confirmed, not cancelled, not moved, and not already reminded.
What happens when a Peek booking is cancelled?
A cancellation event should update the booking status, stop all pending reminders tied to that booking, prevent review requests, and optionally notify the business team.
What happens when a Peek reservation is rescheduled?
The workflow should update the existing booking record, cancel the old scheduled reminder, and schedule a new reminder based on the new activity date and time.
Can Peek Pro and Birdeye work without Zapier?
In many cases a direct webhook-to-Bizinga workflow can avoid using Zapier as the central automation layer. Exact access depends on the operator's Peek Pro account and approved integration access.
Can the message include the activity, date, and meeting location?
Yes, when those fields are available in the webhook payload or mapped booking data. Meeting instructions may depend on the operator's setup and the fields Peek Pro provides.
How are duplicate reminders prevented?
The integration should use the booking identifier, booking status, event state, and send history to avoid treating every update as a new booking.
Can existing Peek bookings be imported?
Active future bookings may be synchronized into reminder workflows with careful launch rules. Older reservations should not receive new-booking confirmations unless the operator explicitly approves it.
Can different activities receive different messages?
Yes. Messages can be segmented by activity, location, date, booking status, or other mapped fields when those fields are available and the workflow is configured that way.
Can multiple business locations use the integration?
Yes, if booking data is mapped to the correct Birdeye location. This is important for multi-location tour, attraction, and activity businesses.
Can Birdeye request a review after the activity?
Yes, where enabled. The review request should only send after the activity is complete and should not send for cancelled, unresolved, no-show, or future-rescheduled reservations.
Want ConvertLocal to build this workflow?
We can help connect Peek Pro booking events, map fields into Birdeye, configure SMS reminders, handle cancellations and reschedules, and test the workflow before launch.