Skip to main content
Baza doesn’t take bookings or money itself. It sends customers to the pages you already use, or collects the details for your team. Add both links under Configure → Bookings & payments on your assistant’s page. Your assistant sends each one as a button, so put your links there, not in your instructions. Add the page where customers book. Any booking page works, whatever is booked: a table, an appointment, a room or a class. Calendly, Cal.com, Google Calendar, Microsoft Bookings, Fresha, OpenTable, a form or your own site are all fine. When someone wants to book, your assistant sends the page as a button. The customer picks a time and books there.
  • As you type the link, Baza names the booking service if it recognises it.
  • With Calendly and Cal.com, the customer’s name and email are filled in for them.
  • Baza won’t accept a link that can never work for a customer, such as your own booking dashboard or a video call link. It tells you which public link to use instead.
Without a link, your assistant collects what the customer wants: the day, the time, how many, what goes where. It passes this to your team to confirm, with everything in one summary.
It never says a booking or order is confirmed. You do, in the conversation.
Add a payment page from Paystack, Flutterwave, Stripe, PayPal or any other payment company. When someone asks how to pay, your assistant sends it as a button. Baza won’t accept a link that only you can open, like your PayPal account. It also won’t accept one that stops working after one use, like a single Stripe checkout. Other ways to pay, such as mobile money codes or bank details, go in your knowledge. Your assistant never says a payment arrived. When a customer says they’ve paid, it passes the chat to your team to check.