NexaModus Agenda
Two people in the same slot is a defect, not a coincidence.
Service, professional, availability and reservation in a model that treats a scheduling conflict as a system error — not as something the front desk sorts out later.
Capabilities
What the module does
Every item below describes behavior defined in the product plan — not a wish list from a sales page.
Service with duration, buffer and location
Each service declares duration, protective buffer between appointments, capacity and location type — in person, video or phone.
Availability that accepts real life
Weekly grid per professional, exceptions, vacations, holidays, blocks, timezone and minimum/maximum notice. The calendar nobody can configure is the calendar nobody uses.
Reservation locked against double-booking
Writes are idempotent and the lock lives in the database, not on screen. Cancellation, rescheduling and no-shows are part of the model from day one.
Public page by secure reference
The public link identifies the service and the customer by an opaque reference. A public identifier never counts as authorization to access internal data.
On screen
How it looks to whoever's operating it
One day, three professionals. The block created by the AI shows up marked as such — who booked it is never ambiguous.
- 09h00Technical visitDiego SampaioConfirmed
- 10h30Initial consultationPaula RezendeConfirmed
- 13h00Block · lunchDiego SampaioBlocked
- 15h30Demo — workbenchDiego SampaioCreated by AI
- 16h45Follow-upAna MeirelesFree
Database-level lock against double booking. Two reservations at the same time fail on the second one, not at the front desk.
Model
What the calendar needs to know to not get it wrong
A calendar that's too simple breaks at the first exception: the holiday, the lunch break, the trip, the professional who works in two places. These are the pieces that prevent that.
- Service
- Duration, protective buffer between appointments, capacity and location type: in person, video or phone.
- Availability
- Weekly grid per professional, with exceptions, vacations, holidays, blocks, timezone and minimum/maximum notice.
- Reservation
- Idempotent write with a lock against double-booking. Cancellation, rescheduling and no-shows are part of the model.
- Reminder
- Fires at 24h, 2h and 15 minutes before, with idempotent execution — replaying the queue doesn't resend the message.
What the module persists
- Service
- StaffMember
- AvailabilityRule
- AvailabilityException
- Booking
- Reminder
Rotation among professionals, when enabled, is deterministic: the same input produces the same choice, and the choice gets logged.
Public booking page
The public link identifies the customer and the service by an opaque reference. That's not an implementation detail: a public identifier never works as authorization to access internal data.
Whoever has the link can book. Whoever has the link can't list anyone's calendar.
Integration
How it connects with the other modules
This is the part that separates a platform from a bundle of tools sold together. None of the connections below go through an export or an intermediate integration.
- Agenda → SupportBooking during the conversation is the normal path, not the exception.
- Agenda → AIThe agent checks slots through the search_slots tool before offering anything — it doesn't invent availability.
- Agenda → CRMThe booking enters the timeline of the contact and the opportunity.
- Agenda → AnalyticsBooking is a stage in the chain: you can see how much each scheduled slot cost.
Want to see Agenda in your operation?
Tell us how the process works today. The conversation starts there, not with a proposal.