Overview
In the Conversa Labs Calendar, an event type can require payment to confirm the time slot. You choose between two modes:
- Full amount — the customer pays the whole service to confirm.
- Deposit — the customer pays only a part now to secure the spot, and the remaining balance is arranged for later (for example, "deposit now, remainder on site").
While payment isn't completed, the slot stays reserved (not confirmed) and expires if payment doesn't arrive within the deadline — freeing the spot for someone else. The booking only triggers the side-effects (conversation, task, deal, confirmation) once the required payment is confirmed.
Prerequisites
- The Calendar module enabled and the Payments module active, with a gateway connected (Asaas or Mercado Pago).
- An event type configured to require payment (full or deposit).
- A profile allowed to configure the Calendar and Payments.
Step by step
Configure (you):
- Open the event type and enable Require payment.
- Choose full amount or deposit and enter the deposit amount when applicable.
- (Optional) Set the reservation expiry deadline while payment isn't completed.
- Save and publish the link.
Book and pay (customer):
- The customer picks a time on the public page and fills in their details.
- At the payment step, they see the charge — PIX, boleto or link/card, per the gateway.
- The slot stays reserved while payment isn't completed.
- On payment confirmation, the booking becomes confirmed and triggers the side-effects.
- For a deposit, the customer sees the remaining balance to pay later.
Settings & options
- Charge mode: full amount or deposit with a partial amount.
- Remaining balance: in deposit mode, the difference between the total and the deposit is recorded (e.g. pay on site).
- Payment methods: PIX, boleto or link/card, per the connected gateway.
- Payment status: pending/reserved → paid/confirmed (or expired, if the deadline passes).
- Reservation expiry: the deadline for payment to arrive; without payment, the slot is freed.
Use cases
- Charge a whole consultation or mentoring session before confirming the slot.
- Charge only a deposit to reduce no-shows, leaving the remainder for the appointment day.
- Hold the spot for a limited time while the customer completes the PIX.
- Auto-confirm the booking as soon as the payment is approved, with no manual checking.
Tips, limits & best practices
- Make it clear in the event type's name/description whether it's full amount or deposit, so the customer isn't surprised.
- A short expiry deadline frees spots faster; a longer one gives room for PIX/boleto to clear.
- In deposit mode, communicate the remaining balance well and where/how it will be paid.
- The booking only confirms and triggers side-effects after the required payment — a reserved slot isn't yet a guaranteed appointment.
- Gateway, method and refund details live in the Payments module (see "See also").
Troubleshooting
- Payment didn't confirm the slot: confirm the Payments module is active, the gateway connected, and the payment was completed — the slot stays reserved until confirmation.
- The reservation expired: payment didn't arrive within the deadline; the customer needs to book again.
- The customer didn't see a way to pay: check that the event type has Require payment on and a gateway connected.
- The remaining balance didn't show: confirm the event type is in deposit mode, not full amount.