Settings & Migration

Use the Settings tabs as the control center for business identity, booking links, fees, messaging, integrations, and data movement.

Settings map

Organization: business identity, timezone, booking URL slug, operating rules, and customer-facing details.
Account: signed-in account details and security actions.
Booking Widget: all-activity and activity-specific links plus supported iframe snippets.
Payments: customer-facing tax and service-fee configuration where supported.
Notifications: message switches, review link, safe test sends, and the delivery log.
Integrations: optional Resend and Twilio credentials and readiness checks.
Data: exports and links to migration tools.

Booking slug and widget

The booking URL slug becomes part of the public address, so use a short stable version of the business name. After changing it, verify the all-activity link, each focused activity link, and any iframe already installed on your website.

The supported iframe embeds the full ReservKit booking flow for all activities or one activity. Calendar-only and activity-card-only embeds remain future options.

Notification and integration checks

Managed delivery can work without operator-owned provider credentials when enabled. Custom email requires both a Resend API key and verified From Email. Custom SMS requires Twilio Account SID, Auth Token, and From Number.

Settings test sends use the saved business contact and do not message customers or run live reminder jobs. The delivery log is read-only and intentionally avoids exposing message bodies, customer contact data, recovery links, verification codes, or provider secrets.

Import customers or future bookings

Step 1. Export a CSV from the previous platform and keep an untouched backup.
Step 2. Open Migration Center, choose Customers or Future Bookings, and identify the source platform.
Step 3. Upload the CSV and review every warning, duplicate match, activity name, date, start time, and slot-capacity result.
Step 4. Stage the rows first. Commit only after the preview matches the intended organization and booking slots.
Step 5. After commit, verify Customers, Bookings, Calendar, guest counts, and source references before importing another batch.

Migration is not a blind file upload. Future bookings must match an existing activity and future slot, and duplicate source records are guarded. Stop and correct the CSV or app setup when preview warnings are unclear.

Before changing live settings

Record the current value, make one logical change, save it, and verify the customer-facing result. For pricing, payment, slug, email, or SMS changes, run a controlled end-to-end check before the next live booking window.