ReservKitReservKit

Getting Started with ReservKit

Follow this sequence from a new account to one tested customer booking. Finish each completion check before moving to the next task.

1. Create the organization

Open: app.reservkit.com/login -> Sign up -> Onboarding

New public organizations begin with a 14-day full-access trial, so you can configure and test the first booking flow before selecting a paid plan.

  1. 1

    Create the owner account

    Use the public signup path, verify the account when prompted, and continue to Onboarding.

  2. 2

    Enter the business basics

    Add the business name, choose the closest business type, and select the operating timezone.

  3. 3

    Finish onboarding

    Create the organization and wait for the operator dashboard to load before opening another page.

You are done when

  • The dashboard loads with the correct organization selected.
  • Settings -> Organization shows the correct business name and timezone.

2. Complete the public business profile

Open: Settings -> Organization

  1. 1

    Add customer-facing details

    Review the business name, email, phone, logo, timezone, and any customer-facing address or instructions your operation uses.

  2. 2

    Set the booking URL slug

    Choose a short, stable slug based on the business name. This becomes part of every public booking URL.

  3. 3

    Review booking rules

    Set the minimum lead time, maximum advance-booking window, cancellation policy, and other available organization rules.

  4. 4

    Save and verify

    Select Save Organization Settings, then open Settings -> Booking Widget and confirm that a Public Booking URL is available.

You are done when

  • The organization profile saves without an error.
  • The Public Booking URL contains the intended business slug.

3. Create the first activity

Open: Activities -> Add Activity

  1. 1

    Complete Details

    Enter the customer-facing activity name and description, choose the activity and slot type, then set duration, capacity, location, and the correct pricing model.

  2. 2

    Add booking fields only when needed

    Use Fields for information the operator truly needs from the customer. Avoid collecting sensitive information that is not required to deliver the activity.

  3. 3

    Create availability

    Open Availability, select Add Schedule, and define the operating day, opening window, last check-in or end time, interval, and any available capacity controls.

  4. 4

    Attach optional requirements

    Use Equipment, Waivers, and Deposit only when this activity needs them. Plan gates shown in the app control which tools are available.

  5. 5

    Save the activity

    Select Save. All activity tabs save together, so resolve any validation message before closing the editor.

You are done when

  • The activity appears on Activities with the expected price and duration.
  • At least one future opening appears for the activity.
  • The focused public booking link opens the correct activity.

4. Connect customer payments

Open: Billing -> Connect Stripe Account

ReservKit collects the plan-based booking fee on the booking subtotal where applicable. Tips, taxes, operator service fees, and refundable damage deposits are not marked up by ReservKit.

  1. 1

    Start Stripe onboarding

    Select Connect Stripe Account and complete Stripe's business and payout onboarding in the Stripe window.

  2. 2

    Return to ReservKit

    After Stripe sends you back, reopen Billing if needed and wait for the connection status to finish loading.

  3. 3

    Check payment readiness

    Confirm Billing shows Connected. Stripe controls payout timing, processing fees, and connected-account money movement.

You are done when

  • Billing shows the Stripe account as Connected.
  • The public activity can continue from guest details to Stripe Checkout.

5. Run a controlled test booking

Open: Settings -> Booking Widget -> Public Booking URL

Use the same path a customer will use. A standard organization connected to live Stripe can create a real charge.

  1. 1

    Open the public link in a private window

    Confirm the correct business and activity appear without relying on the signed-in operator session.

  2. 2

    Choose the complete booking

    Select the activity, future time, duration, and guest count. Review add-ons, fees, waiver requirements, and the displayed total.

  3. 3

    Complete checkout once

    Enter controlled customer details and continue through Stripe. Do not repeatedly submit if the first result is uncertain.

  4. 4

    Verify the customer result

    Confirm the payment-success page, booking reference, receipt, Guest Hub link, any required waiver path, and that guests receive a booking confirmation email when confirmations are enabled.

  5. 5

    Verify the operator result

    Open Bookings -> Booking Detail and compare the customer, time, guest count, amount, payment state, waivers, equipment demand, and message status with the checkout.

You are done when

  • The customer success page and operator Booking Detail refer to the same reservation.
  • Payment, waiver, equipment, and notification states match the configured activity.
  • Any real controlled charge is reconciled or refunded according to the test plan.

6. Share the booking path

Open: Settings -> Booking Widget

Settings -> Booking Widget can generate the all-activity public booking link, activity-specific booking links, and website iframe snippets. Dedicated calendar-only or activity-card-only embeds are future options, not launch features.

  1. 1

    Choose the right link

    Use the all-activity URL when customers should browse the catalog. Use an activity-specific URL when a button should open one activity directly.

  2. 2

    Add it to one customer channel

    Place the tested URL on the business website, Google Business profile, social profile, or another controlled channel.

  3. 3

    Test from the published location

    Use a phone that is not signed into the operator account and confirm the published button reaches the same tested booking flow.

You are done when

  • The published link opens the intended business and activity on mobile.
  • A customer can reach an available time and the expected checkout without operator access.

Before sending real traffic

  • Business identity, timezone, booking slug, and customer contact details are correct.
  • Activity price, duration, capacity, cutoff rules, and future availability have been checked.
  • Stripe is connected and the controlled checkout produced the expected booking record.
  • Required waiver, equipment, deposit, add-on, tax, and notification behavior has been verified.
  • At least one staff member knows where to find Bookings, Check-In, and Booking Detail.
Do not move customer traffic because setup merely saved. Move traffic after the public flow and operator record agree in a controlled booking test.