Diary and availability
It will show which slot is free and which is not in real time, and close the door on double bookings.
On the roadmap
Module in development
Bookings
The real-availability diary we do not have yet, on top of the customers and the invoicing we do.
Bookings is an iERP module in development: it will cover the diary, bookable spaces and resources, enrolments with places and waiting lists, and the real-time availability that prevents double bookings. It cannot be activated in any workspace yet. Today the customer who books lives in CRM, the payment in Finance and the complaint in Support.
What it does
What Bookings will cover
Written in the future tense on purpose: this is what the module will solve once it exists, not what it does today.
Spaces and resources
It will treat rooms, equipment and people as bookable resources, with their rules and their set-up times.
Enrolments
It will handle places, waiting lists and confirmation for anyone signing up to a session or a course.
From booking to invoice
It will hand the delivered session over to Finance to invoice, without keying in the customer or the amount again.
How the AI runs it
What you will be able to ask it
Once Bookings is in production you will be able to move the diary by talking to it. Today the agent already answers for the customer, the payment and the complaint.
The agent reads, proposes and asks for confirmation before writing, and every action is logged in the audit trail as an AI action. This module's own actions will ship with the module.
Which customers have sessions closed this month and which are still unpaid?
crm.cliente_listar customers in the period
Here are the customers for the period from CRM, and I have drafted the invoice with Finance for you to review. The real-availability diary and enrolments will come with this module.
- Draft the invoice for the sessions closed in June.
Works with
What Bookings will build on
Whoever books is already a CRM customer, whatever is charged is already a Finance invoice, and whatever goes wrong is already a Support ticket. All three are in production and share database, permissions and agents with the module still to come.
CRM
In production
Customers, opportunities, pipeline and one-click conversion of a won deal into a project.
View module
Finance
In production
Invoicing with your own series, partial payments, treasury forecasting and a chained invoice register.
View module
Support
In production
Tickets with SLAs in minutes, reply templates and the customer conversation over email, fully traced.
View module
On the roadmap
What exists today and what is missing
The whole module is missing: there is no diary or resource calendar in production and Bookings cannot be activated in any workspace. The customer, payment and aftercare side does exist today, spread across three working modules.
- What it will cover: a real-availability diary, bookable spaces and resources, and enrolments with waiting lists.
- What you can already do today: keep whoever books as a CRM customer, charge them with Finance and handle their complaint in Support.
- When it lands: we give no date, because we do not have one. It is prioritised by real demand, so asking for it moves the queue.
Questions about Bookings
What people ask before deciding.
Not yet with an availability diary. The customer, the quote and the invoice for a session already run on CRM and Finance, but the calendar of spaces and resources is what Bookings will bring, and it is in development.
Tell us your case and we prioritise
Half an hour with your real diary. In the meantime, the Professional plan already includes CRM, Finance and Support, which cover the customer, the payment and the aftercare.