Last updated July 21, 2026
How to Set Up Automated FareHarbor Text Message Reminders
Automatically send booking confirmations and pre-trip SMS reminders through Birdeye when a customer books through FareHarbor. Keep reminders synchronized when reservations are updated, cancelled, or rescheduled.
Clear answer: how FareHarbor text reminders work
FareHarbor 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 FareHarbor.
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
FareHarbor 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.
FareHarbor webhook setup
For the current FareHarbor workflow, use the booking webhook URL generated inside the Bizinga FareHarbor application. In FareHarbor, select the booking-data webhook configuration and choose Bookings only, not payment or optimized-payment options. Include booking-created, booking-modified, booking-cancelled, and booking-rebooked events. Create one production webhook with the production URL and a separate test webhook with the Bizinga test URL.
Use the FareHarbor booking UUID as the unique reservation identifier. FareHarbor may send multiple webhook events for the same booking, so Bizinga should deduplicate by booking UUID and event state. A modified booking updates the existing journey; it should not create a second customer journey. A cancellation stops pending reminders. A rebooking updates the activity date and reschedules the pending reminder.
How to Set Up Booking Text Reminders in Birdeye
1. Connect the booking platform
ConvertLocal configures the FareHarbor 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.
Anonymized setup screenshots
These redacted screenshots show the kinds of screens operators review when planning FareHarbor, Bizinga, and Birdeye workflows. Credentials, booking IDs, guest names, phone numbers, and private account details are removed or replaced before publishing.
Confirm FareHarbor is connected to the right location
The location settings should show the correct FareHarbor connection before customer messages are enabled. This keeps booking activity, inbox routing, and review workflows tied to the right operation.
Connected apps confirm that FareHarbor booking activity and Birdeye communication workflows are tied to the right location.
Confirm the live webhook
The webhook confirmation is the operational green light that booking changes are reaching the workflow layer. Test this before sending confirmations, reminders, or review requests.
A live webhook confirmation tells the team that FareHarbor booking activity is reaching the workflow layer.
Review the active automation
The automation list shows the trigger app, trigger event, action app, and workflow status. Keep the workflow in monitoring mode until booking events are flowing correctly.
Operators can monitor the automation that listens for FareHarbor booking changes and routes the next step into Birdeye.
Inspect booking activity before sending
A line-of-sight feed helps confirm each booking record, status, activity thread, and queued step. This is especially useful for preventing duplicate texts after booking updates or rebookings.
Line-of-sight views help confirm which records were received, what status they are in, and whether confirmation, reminder, and review steps are queued.
Build confirmation messages with booking fields
Use mapped fields such as first name, activity name, activity date, and activity time so the text feels specific to the guest and does not require manual rewriting.
The automation builder turns booking fields like first name, activity name, date, and time into guest-ready SMS messages.
FareHarbor API and webhook settings
Webhook and API screens should be handled carefully. Public documentation should never expose live webhook URLs, API keys, authentication tokens, or business IDs.
API keys and webhook settings should be handled carefully during setup; credentials should never be exposed in public documentation.
Confirmation and reminder workflow fields
The message workflow should use mapped fields such as first name, guest count, activity name, activity date, and activity time rather than generic one-size-fits-all reminders.
Automation planning turns booking, reminder, arrival, and post-tour moments into consistent guest communication.
Guest messages stay in a shared inbox
After reminders start, guests may reply with questions about parking, weather, late arrivals, or accessibility. A shared inbox keeps those conversations visible.
A shared inbox keeps webchat, text, and social conversations organized so guest questions do not sit unanswered.
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 FareHarbor send automatic text reminders?
FareHarbor manages reservations. Automated SMS reminders can be built by sending FareHarbor booking events through a webhook into Bizinga, then mapping the booking data into Birdeye for the messaging workflow.
How do FareHarbor webhook text reminders work?
FareHarbor sends booking-created, booking-modified, booking-cancelled, and booking-rebooked events to a Bizinga webhook. Bizinga validates the booking UUID and status, updates Birdeye fields, and triggers or reschedules the appropriate SMS workflow.
Can I send a text immediately after a FareHarbor booking?
Yes, if the reservation is active, a valid mobile number exists, and the workflow is enabled. The confirmation should be sent once per active reservation unless a meaningful update requires a new confirmation.
Can I send a reminder two days before a FareHarbor tour?
Yes. A common workflow schedules a reminder about 48 hours before the activity start time, as long as the booking is still confirmed, the guest has not opted out, and the activity has not been cancelled or moved.
What happens if a FareHarbor booking is cancelled?
The cancellation event should mark the booking as cancelled, stop pending reminders, prevent post-trip review requests, and optionally notify the business team. Customer cancellation texts should only send if the operator has approved that workflow.
What happens when a FareHarbor reservation is rebooked?
The integration should find the reservation by the FareHarbor booking UUID, update the activity date and time, cancel the old reminder, and schedule a new reminder relative to the new activity time.
Will customers receive duplicate messages?
They should not when deduplication is configured correctly. FareHarbor may send multiple events for the same booking, so the integration should use the booking UUID, event state, and send history to prevent duplicates.
Can the message include the activity name and start time?
Yes, when those fields are available in the payload and mapped into Birdeye. Common fields include customer name, mobile number, activity name, activity date, activity time, booking status, and location.
Can FareHarbor booking data trigger a Birdeye review request?
Yes, but review requests should only send after the activity has been completed. They should not send for cancelled bookings, unresolved statuses, or reservations moved to a future date.
Do I need Zapier to connect FareHarbor and Birdeye?
Not necessarily. ConvertLocal can use the Bizinga webhook workflow to receive booking events and update Birdeye without making Zapier the center of the reminder workflow.
What is the difference between the FareHarbor API and a webhook?
A webhook pushes events when something changes, such as a booking being created or cancelled. An API is typically used to request data. Reminder workflows usually depend on webhooks so changes can be handled quickly.
Can this work for multiple FareHarbor locations?
Yes, if locations are mapped correctly. The workflow should route each booking to the correct Birdeye location so messages, reviews, and inbox conversations stay organized.
Can existing future bookings be added to the reminder workflow?
Yes, with care. Historical bookings should not receive new-booking confirmations unless approved. Active future bookings may be enrolled into upcoming reminder workflows after launch rules are tested.
Want ConvertLocal to build this workflow?
We can help connect FareHarbor booking events, map fields into Birdeye, configure SMS reminders, handle cancellations and reschedules, and test the workflow before launch.