ConversaLabs Help Center
en
Language
pt_BR Portuguese (Brazil) en English es Spanish

Paid scheduling

Open in
View as Markdown Open in ChatGPT Open in Claude
Conversa Labs

Conversa Labs

Last updated on Jun 27, 2026

Overview

Paid scheduling connects the Calendar to the Payments module: the customer only confirms a booking after paying. When someone books an event type marked as paid, the platform creates a charge automatically (a PIX, for example), holds the slot while the payment is pending, and confirms the booking on its own when the gateway reports it as paid.

It's ideal for consultations, sessions and services where you want to secure the customer's commitment with a prepayment — reducing missed appointments and no-shows.

Prerequisites

  • Calendar and Payments modules enabled.
  • A connected, valid gateway.
  • An event type (in the Calendar) configured to charge — with an amount and a payment mode.

Step by step

  1. In the Calendar, open the event type that should require payment.
  2. Set the event type's payment mode (for example, a one-off payment to release the booking).
  3. Enter the amount for the booking and the method (PIX, boleto or card, depending on the gateway).
  4. Save the event type.
  5. When a customer books that event type, the platform creates the charge and leaves the booking awaiting payment.
  6. The customer pays; the gateway notifies and the booking becomes confirmed automatically.
  7. Track both the charge (in Payments) and the booking (in the Calendar).

Settings & options

  • Payment mode per event type: set in the Calendar (for example, mandatory prepayment).
  • Booking awaiting payment: the slot is reserved/held until confirmation; unpaid bookings may expire according to the configured rule.
  • Automatic confirmation: the booking turns confirmed when the gateway's payment event arrives — no manual action.
  • Charge method: PIX, boleto or card, depending on the connected gateway.

Use cases

  • A clinic that requires upfront payment for appointments.
  • A professional charging a deposit to reserve a slot.
  • High-demand services where prepayment secures the commitment.

Tips, limits & best practices

  • Use PIX to release the booking faster (near-immediate confirmation).
  • Make it clear in the event type description that the slot is only confirmed after payment.
  • Set a reasonable deadline for the pending booking, so slots aren't held for too long.
  • Confirmation depends on the gateway's webhook; keep it configured correctly.

Troubleshooting

  • The booking doesn't confirm after payment: check the gateway's webhook (see Refunds, webhooks and reports).
  • No charge option on the event type: confirm the Calendar and Payments modules are enabled and a gateway is connected.
  • The slot was released without payment: review the event type's payment mode (it should require prepayment).

See also