Title: Qaiyo Smart Appointment
Author: qaiyo
Published: <strong>17 agosto, 2026</strong>
Last modified: 31 outubro, 2026

---

Pesquisar plugins

![](https://ps.w.org/qaiyo-smart-appointment/assets/icon-256x256.png?rev=3656630)

# Qaiyo Smart Appointment

 Por [qaiyo](https://profiles.wordpress.org/qaiyo/)

[Baixar](https://downloads.wordpress.org/plugin/qaiyo-smart-appointment.1.4.0.zip)

 * [Detalhes](https://br.wordpress.org/plugins/qaiyo-smart-appointment/#description)
 * [Avaliações](https://br.wordpress.org/plugins/qaiyo-smart-appointment/#reviews)
 *  [Instalação](https://br.wordpress.org/plugins/qaiyo-smart-appointment/#installation)
 * [Desenvolvimento](https://br.wordpress.org/plugins/qaiyo-smart-appointment/#developers)

 [Suporte](https://wordpress.org/support/plugin/qaiyo-smart-appointment/)

## Descrição

Qaiyo Smart Appointment is a clean, fast scheduling plugin for service businesses—
salons, clinics, coaches, consultants, studios and freelancers.

Its standout feature is **fluid slot allocation**. Most booking plugins slice the
day into a fixed grid for one chosen duration. Qaiyo instead works on the _open 
gaps_ around existing appointments and fits each requested service into whatever
space is left. Book a 2-hour service, then a 1-hour one, and the remaining time 
stays fully bookable for any mix of shorter or longer services that still fit — 
packed dynamically, never wasted.

#### Free features

 * Fluid, gap-based slot engine (mixed durations in the same day)
 * Unlimited services, staff members and bookings — no caps of any kind
 * Step-by-step booking wizard, placed with a shortcode `[qsab_booking]`, a Gutenberg
   block, or a native widget in Elementor, Bricks, Breakdance or Oxygen — the same
   settings in every one
 * “Anyone available” or specific staff selection
 * Per-service duration, price, colour and buffer times
 * Fixed mode too — classic back-to-back time bands, if you prefer them, set globally
   or per service
 * Quote requests — a booking mode that reserves no time at all: the customer names
   a preferred day and part of day and asks for a price, so an enquiry never takes
   a slot away from a real booking and two enquiries never clash
 * Online payments — require payment before confirming a service, and the customer
   pays on a hosted checkout before the booking is confirmed. WooCommerce is the
   built-in provider, so you keep whatever gateways your shop already has (card,
   PayPal, bank transfer, cash on arrival)
 * Working hours per staff member, with split shifts (e.g. a lunch break), falling
   back to your global opening hours
 * Days off / vacation blocking — each range can carry a name (“Vacation”, “Public
   holiday”) that your visitors see
 * Staff details on a page — `[qsab_staff id="3" field="phone"]` prints a staff 
   member’s name, email address (spam-protected) or phone number, always as set 
   under Staff
 * Opening hours widget — `[qsab_hours]` shortcode, block and page-builder widget:
   your weekly hours with today highlighted, whether you are open right now and 
   until when, and a notice for coming days off. It stays correct on cached pages
 * Soft hold — a request can leave the time open until you approve it, so an enquiry
   never locks a resource; first approval wins
 * One-click Approve / Decline buttons right inside the admin notification email
 * Editable emails — five messages (request received, confirmed, cancelled, completed,
   reminder) plus the admin alert, each with its own on/off switch and its own wording,
   written with merge tags like `{customer_name}` and `{when}`
 * Appointment reminders — an automatic email a set number of hours before a confirmed
   booking, sent once and only once
 * Add to calendar — the confirmation and the reminder carry a calendar file (.ics)
   for Apple Calendar, Outlook and the rest, plus an “Add to Google Calendar” link;
   the booking form offers both the moment a booking is confirmed. The entry shows
   the service and its time, never the customer
 * Public availability calendar — `[qsab_availability]` shortcode and block showing
   free and fully-booked days at a glance, with no customer details on the page
 * “Upcoming” agenda card — `[qsab_upcoming]` shortcode and page-builder widget:
   today’s date, how many bookings today has, and the next few bookings with their
   service colour and time. It shows what runs and when, never who booked, so it
   is safe on a public page; it can also be kept to logged-in users for a team page
 * Two customers cannot take the same time — a booking is re-checked the moment 
   it is stored, so simultaneous submissions for one slot never both succeed
 * Customers always see the time their service starts, not the buffer reserved around
   it
 * Personal data tools — bookings appear in WordPress’s own Export / Erase Personal
   Data screens, and the suggested privacy-policy text lists what is stored
 * Spam trap and a per-connection limit on the booking form, so bots cannot fill
   your calendar with junk requests
 * One-click confirm / cancel / complete in the admin, and permanent delete (single
   or in bulk) for clearing out test data
 * Customer self-cancellation links
 * Settings export / import (JSON)
 * FluentCRM integration — add booking customers to your lists & tags automatically
 * Qaiyo ecosystem dashboard card — if you also run Qaiyo Admin Booster, a “Today’s
   appointments” card on your WordPress dashboard shows today’s booking count and
   the next appointment’s time
 * Live status in your email signature — a small image (“Open now · until 17:00”)
   for an HTML signature, drawn at the moment the email is opened. Off until you
   switch it on
 * Accessible to WCAG 2.2 AA (keyboard, screen readers, focus, contrast, reduced
   motion) and ready for right-to-left languages
 * Translated into Hungarian, German, French, Spanish, Japanese, Portuguese, Italian,
   Russian, Turkish and Polish

#### Pro features

The Pro add-on is a separate plugin. Everything above keeps working without it.

 * Stripe and PayPal connected directly, for sites with no shop — the customer pays
   on the provider’s own hosted page, and the booking confirms from the webhook,
   from the customer’s return, or from an hourly check, whichever comes first
 * Deposits — collect a percentage or a fixed amount up front instead of the full
   price
 * Five more booking modes: group sessions for classes, hourly and multi-day rentals
   where the customer picks the length, an arrival-order queue, and recurring series
   booked (and paid for) in one go
 * Customer booking portal — customers look up and cancel their upcoming bookings
   through a short-lived emailed link, with no account to create
 * Waiting list — customers join a full day and are emailed, one at a time, when
   a slot frees up
 * Multiple locations, each with its own opening hours; the customer picks one on
   the form
 * Staff days off — take one person out for a holiday or a sick day while the rest
   of the team stays bookable
 * Daily breaks and per-service booking windows
 * Custom branding (colour, font, logo) and three more booking-form layouts
 * A richer “Today’s appointments” dashboard card (with Admin Booster)

Learn more at [qaiyo-plugins.com](https://qaiyo-plugins.com/qaiyo-smart-appointment/).

### External services

This plugin makes one outbound request, and only from the WordPress admin.

**WordPress.org plugin directory API** — used by the “Discover Qaiyo” screen
 (Smart
Booking  Discover Qaiyo) to list the plugin author’s other free plugins so you can
install one without leaving your site.

 * What it is used for: fetching the public plugin listings (name, description,
   
   icon, ratings, install count) for author “qaiyo”.
 * When the request happens: only when a logged-in administrator opens that screen,
   
   and at most once every 12 hours — the response is cached in a transient.
 * What is sent: the query itself (the author name and the fields requested). This
   
   goes through WordPress’s own `plugins_api()` function, which is the same call
   the built-in Plugins  Add New screen makes. No personal data, no site data and
   nothing about your visitors or bookings is transmitted.
 * Endpoint: https://api.wordpress.org/plugins/info/1.2/

This service is provided by WordPress.org: [terms of service](https://wordpress.org/about/privacy/),

[privacy policy](https://wordpress.org/about/privacy/).

**Google Calendar — a link, not a connection.** With “Add to calendar” on (Settings
Emails, on by default), confirmation and reminder emails and the booking form’s 
success screen contain an “Add to Google Calendar” link. The plugin itself never
contacts Google.

 * What it is used for: letting a customer add their own booking to their own Google
   Calendar.
 * When anything is sent: only if the customer follows the link. Their browser then
   opens Google Calendar’s new-event page.
 * What is sent: what the link itself holds — the service name, your site’s name,
   the staff member’s name, the start and end time and, with the Pro add-on, the
   location. Nothing about the customer is in it.
 * Endpoint: https://calendar.google.com/calendar/render

This service is provided by Google: [terms of service](https://policies.google.com/terms),
[privacy policy](https://policies.google.com/privacy).

The calendar file (.ics) involves no service at all: it is attached to the email
and generated in the booking response.

The booking form itself makes no external requests. Booking data stays in your
 
database, and notification emails are sent with `wp_mail()` through whatever your
site is already configured to use.

## Instalação

 1. Upload the plugin to `/wp-content/plugins/` and activate it.
 2. Go to **Smart Booking  Services** and add your services.
 3. (Optional) Add staff under **Smart Booking  Staff**.
 4. Set your opening hours under **Smart Booking  Settings**.
 5. Add the booking form to any page with the `[qsab_booking]` shortcode or the block.

## Perguntas frequentes

### What makes the slot engine “fluid”?

It computes availability from the real free gaps around existing bookings, then 
fits the chosen service duration into them on a configurable step grid — instead
of pre-dividing the day into fixed equal slots. Mixed-length services share the 
same day efficiently.

### Does it work without staff?

Yes. With no staff defined, bookings run on the global working hours automatically.

### Does it require WooCommerce?

No, the plugin works standalone without it. A payment provider is only needed if
you turn on “Require payment” for a service, and WooCommerce is the one this plugin
ships with — activate it and the option appears. (Pro adds Stripe and PayPal as 
direct alternatives, for sites that do not want a shop.) Nothing changes for services
that don’t require payment.

### Can customers ask for a price without booking a time?

Yes. Set the service’s booking mode to quote request. The customer picks a day and
whether morning, afternoon or evening suits them, and nothing is reserved — the 
enquiry never blocks a real booking, and two enquiries for the same morning never
clash. Answer it, then book the agreed time normally.

### Can I change what the emails say, or switch some of them off?

Yes. Under Smart Booking  Settings  Emails every message has its own on/off switch
and its own editable subject and wording. Write them with merge tags — `{customer_name}`,`{
service}`, `{when}`, `{start_time}`, `{duration}`, `{price}`, `{total}`, `{staff}`,`{
staff_email}`, `{staff_phone}`, `{booking_id}`, `{status}`, `{cancel_link}` and 
more; the editor lists them all — and clear a field to go back to the built-in text.

### How do customers get a booking into their calendar?

Two ways, both automatic once a booking is confirmed. The confirmation and reminder
emails have a calendar file attached (`appointment.ics`) — opening it adds the appointment
to Apple Calendar, Outlook or any other calendar app — and an “Add to Google Calendar”
link. The booking form shows the same two options on its success screen when a booking
is confirmed on the spot.

The calendar entry holds the service, its time and the staff member. It never names
the customer and never contains the cancel link, because calendar entries get shared
and synced. A request that is still waiting for your approval gets neither, and 
nor does a quote request. If you rewrote an email, add the `{calendar_link}` tag
where the link should go; the file is attached either way. Switch the whole thing
off under Settings  Emails  Add to calendar.

### How do reminders work?

Turn the reminder email on under Settings  Emails and set how many hours before 
the booking it should go out. A background sweep runs hourly and sends the reminder
to every confirmed booking that has entered the window, marking each one so it can
never be sent twice. Pending bookings are skipped, because there is nothing confirmed
to remind anyone about yet.

### Can I show my availability on a page without the booking form?

Yes, with the `[qsab_availability]` shortcode or the matching block. It shows which
days and times are still open and which are fully booked or closed. It never shows
who booked what — only free and busy, exactly what the booking form itself would
reveal.

Attributes: `service` (a service id, defaults to your first active service), `staff`(
a staff id, defaults to anyone) and `days` (how many days to show, default 7).

### Can I show today’s schedule on a page, like a reception screen?

Yes, with the `[qsab_upcoming]` shortcode or the “Qaiyo Upcoming” widget in your
page builder. It shows today’s date and how many bookings today has, then the next
confirmed bookings — the service, its colour and its time. It never shows who booked,
so it is safe on a public page.

Attributes: `title` (defaults to “Upcoming” in the visitor’s language), `count` (
1–10, default 3), `service` and `staff` (ids, to show one of them only), `show_date`(`
0` hides the date tile), `theme` (`auto`, `light` or `dark`) and `audience` (`logged_in`
shows it to logged-in users only).

### Can I show my opening hours and whether I am open right now?

Yes, with the `[qsab_hours]` shortcode or the “Qaiyo Opening Hours” widget. It shows
your weekly hours (from Settings  Working hours, lunch breaks included) with today
highlighted, a line saying whether you are open at this moment and when you open
next, and a notice for any day off coming up — give a range a name under Days off/
vacation, such as “Vacation”, and that is what your visitors read.

Pages are often cached, and “open now” is only true for a moment, so the widget 
carries the next two weeks with it and keeps itself current in the visitor’s browser.

Attributes: `title`, `show_title` (`0` hides the heading), `staff` (one person’s
hours), `layout` (`box`, the default, or `full` for the full width of the column—
in a page builder the width you give the element wins), `show_status`, `show_week`(`
0` hides either part), `notice_days` (how many days ahead to announce a day off,
default 14; `0` only while it lasts) and `theme` (`auto`, `light` or `dark`).

### Can my email signature show whether I am available?

Yes. Switch on the status image under Smart Booking  **Email signature** and copy
the HTML it gives you into your signature. It is a small image — “Open now · until
17:00”, “Vacation · Opens Monday at 09:00” — that your site draws at the moment 
a reader’s mail program loads it, from the same hours and days off as the opening
hours widget, and it links to the page you choose.

Gmail, Outlook and most mail programs load it every time the email is opened. Apple
Mail with Mail Privacy Protection loads images in advance, so there it can show 
the status of when the message arrived; and some programs only show images after
the reader allows them. The address is public (anyone who receives your email can
open it) and shows nothing your opening hours do not already show. Drawing it needs
PHP’s GD extension with FreeType, which most hosts have; the settings card tells
you if yours does not.

### Can I change “Open now” on the status image?

Yes: under Email signature, **Text while open** and **Text while closed** — “Available”
and “Away”, say. The time after it stays, and a day off still shows its own name.

### Can I call the break “Lunch break”?

With the Pro add-on, yes: each weekday’s daily break under Availability has a name
field, and the opening hours widget shows “Lunch break: 12:00 – 13:00”. Without 
a name it reads “Break”.

### Does the plugin put a link to Qaiyo on my site?

Not unless you ask it to. A small “Booking by Qaiyo” line under the booking form
is off by default; you can switch it on under Settings  Booking rules.

### Can I use this with my page builder?

Yes. The booking form, the availability calendar, the “Upcoming” card and the opening
hours are available as native widgets in Gutenberg, Elementor, Bricks, Breakdance
and Oxygen, alongside the shortcodes. Each one offers the same settings, and each
renders exactly what the front end renders — no separate preview to drift out of
date.

### What is the “Today’s appointments” card on my dashboard?

If you also run the free [Qaiyo Admin Booster](https://qaiyo-plugins.com/qaiyo-admin-booster/)
plugin, it collects a summary card from every installed Qaiyo plugin into one “Qaiyo
ecosystem” widget on your WordPress dashboard. This plugin’s card shows today’s 
booking count and the time of the next one. It costs nothing extra and needs no 
setup — it simply appears once Admin Booster is active. Without Admin Booster, nothing
changes; this plugin does not add a card of its own to the dashboard.

### Someone is spamming my booking form. What can I do?

Two things, both built in. The form already carries a hidden spam trap that silently
refuses automated submissions. And under Settings  Booking rules, turning off auto-
confirm and turning on **Requests do not reserve the time (soft hold)** means a 
pending request no longer blocks the slot for anyone else — so even a flood of junk
requests cannot take your calendar out of action. You approve the real ones, and
the first approval wins.

### How does the plugin handle personal data?

A booking stores the name, email address and phone number the customer gives, the
service and time, and any note. Nothing is sent anywhere else. Bookings are included
in WordPress’s own Tools  Export Personal Data and Erase Personal Data screens —
erasing anonymises a booking rather than deleting it, so the calendar still knows
the time was taken — and a suggested paragraph for your privacy policy is added 
under Settings  Privacy.

### What happens to my data if I delete the plugin?

Nothing is removed by default. Deactivating never touches your data, and deleting
the plugin from the Plugins screen keeps every service, staff member, booking and
setting in place — so reinstalling, moving hosts or troubleshooting costs you nothing.

If you would rather leave no trace, tick **Delete all plugin data when the plugin
is deleted** under Smart Booking  Settings  Data on uninstall. With that armed, 
deleting the plugin drops its database tables and options for good. There is no 
undo, so export your settings and back up the database first.

### Can customers rent something by the hour or by the day, or book a class?

Those are Pro booking modes. Hourly and multi-day rentals let the customer choose
the length; group sessions let several people share one fixed time.

## Avaliações

Não há avaliações para este plugin.

## Colaboradores e desenvolvedores

“Qaiyo Smart Appointment” é um programa de código aberto. As seguintes pessoas contribuíram
para este plugin.

Colaboradores

 *   [ qaiyo ](https://profiles.wordpress.org/qaiyo/)

Qaiyo Smart Appointment” foi traduzido para 2 localidades. Agradecemos aos [tradutores](https://translate.wordpress.org/projects/wp-plugins/qaiyo-smart-appointment/contributors)
por suas contribuições.

[Traduzir o “Qaiyo Smart Appointment” para seu idioma.](https://translate.wordpress.org/projects/wp-plugins/qaiyo-smart-appointment)

### Interessado no desenvolvimento?

[Navegue pelo código](https://plugins.trac.wordpress.org/browser/qaiyo-smart-appointment/),
consulte o [repositório SVN](https://plugins.svn.wordpress.org/qaiyo-smart-appointment/)
ou assine o [registro de desenvolvimento](https://plugins.trac.wordpress.org/log/qaiyo-smart-appointment/)
por [RSS](https://plugins.trac.wordpress.org/log/qaiyo-smart-appointment/?limit=100&mode=stop_on_copy&format=rss).

## Registro de alterações

#### 1.4.0

 * New: one booking can hold several places in a session — a party of three takes
   three — for booking modes that let a customer book for friends too (the Pro add-
   on’s group and queue sessions). The session counts places rather than bookings,
   the price is charged once for every place, and emails show the number of places
   and offer a `{seats}` merge tag.
 * Fixed: a cancelled or completed booking could be set back to pending or confirmed
   even when its time — or the last place in its session — had been taken meanwhile.
   Now that only works while there is room.
 * New: more merge tags for the emails — `{start_time}`, `{end_time}`, `{duration}`,`{
   total}` (the price for every place booked), `{staff_email}`, `{staff_phone}`,`{
   booking_id}` and `{status}`. The email editor lists them with the others.
 * New: the `[qsab_staff id="3" field="phone"]` shortcode puts a staff member’s 
   name, email address or phone number on any page — kept in step with Staff instead
   of typed twice. The email address is spam-protected, and email and phone become
   links unless `link="no"`.
 * New: Log screen. Every booking made, status changed and booking deleted, and 
   every email sent — or refused by the mail system — on one list, filterable by
   event and address. Lines are kept 90 days by default (0 keeps them), the log 
   can be emptied by hand, and the privacy eraser removes a person’s lines with 
   their bookings.
 * New: the hourly task (reminders, log clean-up) is watched. When it has not run
   for over two hours — a quiet site, or WordPress’s scheduler switched off — the
   plugin’s screens say so, and a secret address lets a server cron or an online
   cron service run it on time.
 * The booking form’s last step lists what an add-on adds to the summary — the places
   of a party, a rental’s length.
 * The booking form shows sessions that are full among the free times, each with
   a way onto its own waiting list, when an add-on offers one.
 * For developers: `qsab_status_badge_profiles`, `qsab_status_badge_screen`, `qsab_save_badge_profile`
   and `qsab_status_badge_setting` let an add-on keep the signature settings per
   staff member; the `qsab_slots_response` filter (the whole slots response, with
   or without slots), the `qsab_email_sent` action, `seats` on appointments, `max_seats`
   on services, `Qsab_Payments::full_price()`; `qsab_payment_label` now also receives
   the appointment, and `qsab_appointment_deleted` the row as it was.

#### 1.3.3.1

 * Fixed: the email-signature status image could keep showing an old status — yesterday
   evening’s “Closed” in the morning — in Apple Mail and in browsers. A CDN in front
   of some sites (Cloudflare, for one) told mail programs to keep anything ending
   in .png for a year. The image now has to be asked for again every time it is 
   shown (an unchanged one costs a bodiless “not modified” answer), and CDNs are
   told not to store it.
 * The signature HTML carries a new image address, so copies kept under the old 
   one are left behind: copy the HTML from the Email signature screen again and 
   paste it into your signature.
 * The preview on the Email signature screen always shows the current status.

#### 1.3.3

 * New: live status in your email signature. Switch it on under the new Email signature
   screen and paste the HTML it gives you into an HTML signature: a small image —“
   Open now · until 17:00”, “Vacation · Opens Monday at 09:00” — drawn at the moment
   the email is opened, linking to the page you choose. Light or dark, the default
   hours or one person’s. Off until you switch it on.
 * New: your own wording on the status image — “Available” / “Away” instead of “
   Open now” / “Closed now”. Translatable with WPML and Polylang.
 * New: every part of the status line can be reworded — the time after it too (“{
   time}-ig”, “Back {day} at {time}”) — and the image comes as a pill or as plain
   text on a clear background, light, dark or automatic (follows light / dark mode
   where the mail program can, as Apple Mail does). The link, layout, colours and
   person are saved with the screen.
 * The image address ends in `qsab-status.png`, which Apple Mail needs before it
   shows an image at all; where a server does not pass such addresses to WordPress,
   the screen says so and the address falls back to the site’s main one.
 * Changed: Days off / vacation, Booking layout (when there is more than one) and
   Email signature have screens and tabs of their own instead of living inside Settings.
 * For add-ons: the opening hours ask `qsab_hours_break_label` for each date’s name
   of the break (the Pro add-on names its daily breaks per weekday).
 * The status image is drawn in Inter (SIL Open Font License), bundled in `assets/
   fonts` and limited to Latin and Cyrillic; the `qsab_status_badge_font` filter
   supplies a font for other scripts.
 * For developers: `qsab_status_badge_font`.

#### 1.3.2

 * New: the opening hours widget — `[qsab_hours]` shortcode and a widget in Gutenberg,
   Elementor, Bricks, Breakdance and Oxygen. Weekly hours with today highlighted
   and breaks shown — in a compact box or at full width, “Open now · until 17:00”/“
   Opens tomorrow at 09:00”, and a notice for coming days off. It carries the next
   two weeks with it, so a page served from a cache still shows the right status.
 * The table names a day off only within the current week; one coming next week 
   is announced by the notice above it, so a passed weekday never looks as if its
   day off were already over.
 * New: a days-off range can have a name visitors see (“Vacation”), and the Days
   off card shows where each range stands (going on now, in 5 days, over) with one
   click to clear the ones that are over. Names and reworded emails are translatable
   with WPML and Polylang.
 * Accessibility (WCAG 2.2 AA): the booking form moves focus to each new step, announces
   loading and results, ties errors to their fields, marks the selected service,
   day and time for screen readers, names the calendar’s buttons with the full date,
   and shows a clear focus ring whatever the theme does. Required fields say so 
   in words. Text, field outlines and status labels meet contrast minimums, and 
   motion follows the reduced-motion setting. In the admin, every schedule field
   has a name, and choosing whose hours to edit no longer reloads the page by itself.
 * Right-to-left languages: the booking form, the widgets and the admin screens 
   mirror correctly, and emails are written in the site’s direction.
 * The calendar starts the week on the day set under Settings  General.
 * Fixed: two booking forms on one page shared their field ids, so a label could
   point into the other form and a preselected service applied to the wrong one.
 * Fixed: on a page served from a cache for more than a day, the booking form failed
   with a bare “Error”. It now fetches a fresh security token and tries again.
 * Fixed: a cancellation form left open too long sent the customer to the home page;
   it now simply asks again.
 * Fixed: theme styles (upper-case buttons, list bullets, field heights) leaked 
   into the booking form.
 * Changed: the “Booking by Qaiyo” link under the booking form is now off unless
   you switch it on.
 * Security: a customer’s note is capped at 2,000 characters, and an email address
   longer than the database holds is refused instead of being cut.
 * For developers: the `qsab_hours_windows` filter, and the Settings screen is built
   from small templates in `templates/admin/`.

#### 1.3.1

 * New: Add to calendar. Confirmation and reminder emails carry a calendar file (.
   ics) and an “Add to Google Calendar” link, and the booking form offers both on
   its success screen when a booking is confirmed there and then. The entry shows
   the service, its time and the staff member — never the customer, and never the
   cancel link. On by default; switch it off under Settings  Emails.
 * New: the `{calendar_link}` email tag, already in the built-in confirmation and
   reminder wording.
 * Fixed: saving the Emails settings stored every untouched built-in message as 
   if it had been rewritten, so those sites stopped receiving wording improvements
   and translations. Built-in wording is recognised again, including on sites that
   already saved it.
 * For developers: `qsab_calendar_enabled`, `qsab_calendar_event` (add a location),`
   qsab_calendar_rows`, `qsab_calendar_uid`, `qsab_calendar_google_args` and `qsab_calendar_emails`.

#### 1.3.0

 * New: the “Upcoming” agenda card — `[qsab_upcoming]` shortcode and a widget in
   Gutenberg, Elementor, Bricks, Breakdance and Oxygen. Today’s date and booking
   count, then the next bookings with their service colour and time; never who booked.
 * Fixed: two customers submitting the same slot at the same moment could both get
   it. A booking is now re-checked the moment it is stored, and approvals, status
   changes and reminders are all compare-and-set, so a double click or two overlapping
   requests act exactly once.
 * Fixed: following an Approve or Decline link from the admin email acted on the
   booking straight away — mail scanners that open every link could approve and 
   then decline a request before anyone read it. The link now shows a confirmation
   screen, like the customer cancel link.
 * Fixed: saving one Settings form (booking rules, say) switched off the options
   of the others, such as FluentCRM sync. Each form now only changes its own settings.
 * Fixed: emails, the admin list and the customer screens showed the buffer around
   a booking as part of its time. They now show when the service itself runs.
 * Fixed: an unpaid WooCommerce order held its time slot forever. It is now cancelled
   by the store’s own “hold stock” timeout, which releases the slot; and a paid 
   booking is re-checked against the calendar before it is confirmed.
 * Fixed: FluentCRM re-subscribed customers who had unsubscribed when they booked
   again. An existing contact keeps its status.
 * Fixed: the appointments list stopped at 200 bookings. It is now paged.
 * Fixed: the availability calendar showed a day off as “Fully booked”; it now reads“
   Closed”.
 * Changed: the widgets sit in their own “Qaiyo Smart Appointment” group in Gutenberg,
   Elementor, Bricks, Breakdance and Oxygen (it used to read just “Qaiyo”, and the
   blocks sat under Widgets).
 * New: a per-connection limit on the booking form, on top of the spam trap.
 * New: bookings are included in WordPress’s Export / Erase Personal Data tools,
   with suggested privacy-policy text.
 * Security: stricter output filtering for everything the page-builder widgets print,
   and error messages are no longer passed through the URL.
 * Requires WordPress 6.2 or later.

#### 1.2.0

 * New: a “Today’s appointments” card for the Qaiyo ecosystem dashboard widget, 
   shown when the free Qaiyo Admin Booster plugin is also active. Shows today’s 
   booking count and the time of the next one; nothing appears if Admin Booster 
   is not installed.
 * New extension point: `qsab_ecosystem_card_body`, which the Pro add-on uses to
   replace that card’s body with the next three bookings and a link to the calendar—
   see the Pro changelog.

#### 1.1.0

 * Native page-builder widgets: the booking form and the availability calendar are
   now available as widgets in Elementor, Bricks, Breakdance and Oxygen (6.x), on
   top of the existing shortcodes. One shared definition feeds every builder, so
   a setting behaves identically everywhere and an add-on can contribute a control
   to all of them at once through the new `qsab_widget_fields` filter.
 * Fixed: the Gutenberg block never actually worked — it was registered on the PHP
   side only, with no editor script, so it never appeared in the block inserter 
   despite being documented. It now registers properly, with real inspector controls(
   built from the same shared definition as the other builders) and a live preview.
 * A booking form can now be given its own layout per placement, overriding the 
   site-wide default set in Settings.
 * Hardened CSS output: branding values (accent colour, font) and per-service colour
   swatches are now validated for the CSS context specifically, rather than relying
   on HTML escaping, which cannot stop a value from breaking out of a stylesheet
   declaration.
 * Tested up to WordPress 7.1.

#### 1.0.0

 * Initial release.
 * Fluid, gap-based slot engine, plus a fixed mode with classic back-to-back bands.
 * Booking wizard (shortcode `[qsab_booking]` + block), with unlimited services,
   staff members and bookings.
 * Working hours per staff member, including split shifts — a second block on a 
   day makes the gap between them unbookable. Anyone without their own hours works
   the site-wide default.
 * Soft hold: pending requests can leave the time slot open for everyone else until
   you approve one — first approval wins. Built for rental and enquiry-style bookings.
 * One-click Approve / Decline buttons in the admin notification email, signed so
   no login is needed and nobody else can use them.
 * Quote requests: a booking mode that reserves nothing. The customer names a preferred
   day and part of day, so an enquiry never blocks a real booking and two enquiries
   never collide.
 * Per-service booking mode: any service can override the site-wide fluid/fixed 
   setting, so a consultation and an enquiry can behave differently on the same 
   site.
 * Editable emails: six messages (request received, confirmed, cancelled, completed,
   reminder, plus the admin alert), each with its own on/off switch and its own 
   subject and wording, written with merge tags. Blank fields fall back to the built-
   in text, so clearing a field restores it rather than sending an empty email.
 * Appointment reminders: an hourly sweep emails every confirmed booking a configurable
   number of hours before it starts, flagging each row so a reminder can never go
   out twice however often WP-Cron fires.
 * Public availability calendar: the `[qsab_availability]` shortcode and matching
   block show free, fully-booked and closed days without putting any customer detail
   on the page.
 * Spam trap on the booking form — an off-screen field that only an automated submission
   would fill in.
 * Customer cancellation links ask before they act: following one shows the booking
   and a confirm button, so a mail client or scanner prefetching the URL cannot 
   cancel anything.
 * Permanent delete for bookings, one at a time or in bulk, for clearing test data
   out before handing a site over.
 * Online payments: a service can require payment before it is confirmed. The built-
   in provider is WooCommerce, which creates an order for the price and sends the
   customer to your checkout; paying it confirms the booking, and a cancelled or
   failed order releases the time slot.
 * Uninstall keeps your data by default. Deleting the plugin only drops its tables
   and options when “Delete all plugin data” has been ticked under Settings first.
 * Configurable currency symbol and position for displayed prices.
 * Days off / vacation blocking, and settings export / import.
 * FluentCRM sync, and 11 built-in languages.
 * Native page-builder widgets: the booking form and the availability calendar are
   available as Gutenberg blocks and as native widgets in Elementor, Bricks, Breakdance
   and Oxygen, each with the same settings — which service to preselect, which staff
   member, how many days to show. One shared definition feeds every builder, so 
   they cannot drift apart, and an add-on can contribute a setting to all of them
   at once through the `qsab_widget_fields` filter.
 * A booking form can be given its own layout per placement rather than following
   the site-wide setting.
 * Values reaching a stylesheet are validated for the CSS context rather than HTML-
   escaped, so a branding token from the `qsab_branding` filter cannot inject CSS.
 * Extension points for add-ons: `qsab_booking_modes` / `qsab_mode_slots` register
   a booking mode, `qsab_service_form_fields` / `qsab_service_save_data` add its
   per-service settings, `qsab_booking_slot` finishes the booking off, `qsab_payment_providers`/`
   qsab_payment_url` register a payment provider, `qsab_email_types` registers a
   notification, and `qsab_appointment_deleted` lets an add-on clean up after a 
   deletion. The booking form dispatches `qsab:slots-rendered`, `qsab:slot-selected`,`
   qsab:summary` and `qsab:collect` so an add-on can extend it without replacing
   any markup.

## Meta

 *  Versão **1.4.0**
 *  Última atualização **6 dias atrás**
 *  Instalações ativas **Menos de 10**
 *  Versão do WordPress ** 6.2 ou superior **
 *  Testado até **7.1.4**
 *  Versão do PHP ** 7.4 ou superior **
 *  Idiomas
 * [English (US)](https://wordpress.org/plugins/qaiyo-smart-appointment/), [Russian](https://ru.wordpress.org/plugins/qaiyo-smart-appointment/)
   e [Spanish (Spain)](https://es.wordpress.org/plugins/qaiyo-smart-appointment/).
 *  [Traduzir para seu idioma](https://translate.wordpress.org/projects/wp-plugins/qaiyo-smart-appointment)
 * Tags
 * [appointments](https://br.wordpress.org/plugins/tags/appointments/)[booking](https://br.wordpress.org/plugins/tags/booking/)
   [calendar](https://br.wordpress.org/plugins/tags/calendar/)[fluentcrm](https://br.wordpress.org/plugins/tags/fluentcrm/)
   [scheduling](https://br.wordpress.org/plugins/tags/scheduling/)
 *  [Visualização avançada](https://br.wordpress.org/plugins/qaiyo-smart-appointment/advanced/)

## Classificações

Ainda não foi enviada nenhuma avaliação.

[Sua avaliação](https://wordpress.org/support/plugin/qaiyo-smart-appointment/reviews/#new-post)

[Ver todas avaliações](https://wordpress.org/support/plugin/qaiyo-smart-appointment/reviews/)

## Colaboradores

 *   [ qaiyo ](https://profiles.wordpress.org/qaiyo/)

## Suporte

Tem algo a dizer? Precisa de ajuda?

 [Ver fórum de suporte](https://wordpress.org/support/plugin/qaiyo-smart-appointment/)