Ir al contenido
Start free

Reservations

Esta página aún no está disponible en tu idioma.

Wabery Reservations gives one project its own availability, booking rules, and operator calendar. Use it when the business wants Wabery to manage reservations without depending on a separate booking service.

Choose the model that matches the business:

  • Tables reserve one table, or an explicitly configured combination of tables, for a party and its cleanup buffer.
  • Classes reserve places in scheduled group sessions. A class can also claim named rooms or equipment so overlapping sessions cannot use the same resource.
  • Private appointments reserve a service with an available staff member and any required room or named resource.

Appointment requests are different. A request records the customer’s preferred time for a person to review; it does not hold availability or confirm a booking.

  1. Open Agent, then find Agent modules.
  2. Choose Set up bookings or open Bookings → Booking settings.
  3. Select Tables, Classes, or Private appointments.
  4. Add the venue timezone, bookable hours, closures, inventory, people, resources, and customer policies.
  5. Save the draft and inspect the availability preview.
  6. Turn on the Bookings module when the saved setup is ready.

One project has one venue and one reservation model. After the first successful save, the reservation model is fixed for that project. Create another project if the business needs a separate venue or a different model.

Business opening hours and bookable hours are not necessarily the same. Review suggested hours before publishing, especially when they were prepared from a website or business description.

Publish rules separately from customer chat actions

Section titled “Publish rules separately from customer chat actions”

Bookings has two related controls:

  1. Publish booking changes makes the current rules available to authorized people using Wabery, including manual bookings. It does not let the agent make bookings in customer chats.
  2. Launch agent booking actions lets the published agent check availability and create, change, or cancel reservations after the required customer confirmation.

You can turn on Bookings and publish rules before connecting WhatsApp. This is useful when the team needs to prepare the calendar or record phone and walk-in bookings first.

Agent booking actions have their own readiness checks. For WhatsApp, connect the project’s business number and prepare it for the current booking actions. An unpublished booking draft does not block unrelated channels or agent features.

The agent first proposes the exact time, party size or service, and relevant details. Wabery allocates inventory only after the customer confirms that proposal. Availability is checked again during confirmation, so two customers cannot take the same final place.

If a change is no longer available, the existing reservation stays in place. Repeated delivery of the same confirmed action returns the existing result instead of creating another reservation.

Open Bookings → Calendar to see reservations, class occurrences, and blocked time. The calendar uses the venue timezone. On smaller screens, the agenda view keeps the same booking details and actions in a compact layout.

Authorized operators can:

  • record phone bookings and walk-ins;
  • inspect a reservation and its delivery status;
  • move or cancel a reservation;
  • mark table guests seated or class guests checked in;
  • complete a reservation or mark it as a no-show;
  • close availability with a reason; and
  • cancel a class occurrence and review customer notification results.

Record offline commitments in Wabery if the agent relies on Wabery availability. An appointment written only in another calendar is not automatically blocked.

When the requested place is unavailable, an eligible WhatsApp customer can join the waitlist. Joining does not create a reservation, hold inventory, or spend a customer pass.

When capacity returns, Wabery can offer it to the oldest compatible request. The offer lasts 15 minutes. Availability and any requested customer pass are checked again when the same verified sender claims the offer.

Open Bookings → Waitlist to review waiting, offered, expired, cancelled, and claimed requests. You can also advance eligible offers manually. Turning off agent booking actions stops new automatic offers and claims while keeping the saved waitlist and reservations available.

Open Bookings → Customer passes to create a pass type and assign units to an existing customer. A pass can apply to an eligible service and spend a fixed whole number of units per reservation or participant.

The reservation and pass claim are recorded together. If the balance expired or changed before confirmation, Wabery does not create the reservation. An eligible cancellation returns the held units according to the booking policy.

Customer passes are business-issued records. Wabery does not sell the pass, collect its payment, store its price, or prove that the customer paid. They are separate from the Wabery Wallet.

In Booking settings → Team & sharing, create a read-only iCalendar link for a calendar app. The feed includes reservation times, references, and cancellation updates. It excludes customer names, phone numbers, and notes.

The link is shown once. Anyone who receives it can read the limited feed until you revoke it, so treat it like a private sharing link.

Calendar sharing is one-way. It does not import busy time and does not let Google Calendar, Outlook, or another calendar change Wabery reservations.

Use Settings → Project access to invite the business without adding them to your organization. A View-only person can inspect the calendar. An Editor can also be granted Manage bookings access.

You can enable email activity alerts for booking changes. WhatsApp staff alerts are a separate optional setup under Settings → Alerts and may create Meta message charges on the connected business account.

Turning off agent booking actions stops new customer-chat bookings while keeping the calendar and existing reservations. Turning off the Bookings module also hides its normal project navigation and pauses new agent booking actions; it does not delete existing records.

Actions already accepted may finish. Review the calendar and delivery status before assuming a pause reversed work that was already underway.

  • Payments and deposits are not collected by Reservations.
  • External calendars are read-only exports; two-way synchronization is not available.
  • Table combinations must be configured explicitly. Wabery does not invent a seating layout.
  • Customer passes are not money, memberships, or shared family balances.
  • A failed customer notification does not undo a saved reservation. Review the delivery result and follow up manually when needed.