Restaurant and hospitality teams
Useful for reservations, table planning, VIP arrivals, guest callbacks, and organizing the daily service rhythm without relying on scattered notes.
Noesia Smart Waiter / Module Documentation
Free Event-Driven IoC Isolated/X-Core Micro-Frontend Scheduling Core
APPOINTMENTS
Appointments is the structured scheduling surface of Noesia Smart Waiter. It combines a monthly calendar, week view, agenda list, live day panel, and appointment modal so operators can book, review, update, complete, or delete visits without losing control of guest details, status, or daily flow.
Who is it for
Built for teams that schedule real people in real time
Front desk and reception operators
Useful when staff need one place to see the month, jump to today, inspect one day in detail, and capture guest information cleanly inside the admin shell.
Managers and administrators
Useful for reviewing upcoming bookings, spotting no-shows or overdue visits, and keeping the wider platform aware of today’s appointment count.
Noesia Appointments
Appointments. Organized Like a Command Center.
Premium appointment scheduling with monthly calendar view, day details, status flags, and a clean operating-system experience inside Noesia Matrix OS.
14Thu
22Fri
Calendar Active
Smart Scheduling
Main Features
What the Appointments module actually delivers
Three practical scheduling views
- Monthly calendar for broad planning.
- Week view for short-range scheduling.
- Agenda view for list-first review.
Live day panel
- Selected date title and meta summary.
- Same-day appointment list with status visibility.
- Fast transition from planning into action.
New Appointment modal
- Date, start time, end time, and status.
- Guest name, phone, email, and booking purpose.
- Guests / covers, location, and notes.
- Edit and delete flows for existing entries.
Status-aware workflow
- Scheduled, urgent, completed, cancelled, and no-show states.
- Legend markers for scheduled and overdue / no-show visibility.
- Quick completion toggle in the backend flow.
Data-backed storage
- Appointments are stored in the internal
noesia_appointmentcontent layer. - Factory reset support keeps module ownership clear.
- Backward-compatible slug ownership stays stable.
Dashboard integration
- Today and upcoming counts feed the wider shell.
- Morning Briefing and dashboard badges can reference appointments.
- Useful as part of a larger daily operating flow.
How to Access It
Where Appointments lives inside the platform
Admin path: open the Noesia Smart Waiter admin area and select Appointments from the plugin shell navigation or topbar action.
Tier: this module belongs to the Free tier.
Navigation ownership: the module registers its own admin section, topbar action, local AJAX handlers, and local content owner for appointments.
Setup / Configuration
Recommended setup before your team starts scheduling
Confirm admin access
The module uses backend permissions. Make sure the account opening Appointments can actually manage the Noesia Smart Waiter admin area.
Decide your booking language
Before adding live data, decide how your team will fill reason, location, covers, and notes so the schedule stays consistent instead of turning into mixed naming styles.
Define table / area naming rules
If you plan to use Table / Area for hospitality or reception logistics, keep the naming convention stable from day one so week and agenda screens remain readable.
Align dashboard counts if needed
If the main dashboard should highlight appointments, set the wider shell to use appointments as the emphasized briefing source for today’s count.
How to Use It
Typical booking flow from first entry to follow-up
Open Appointments and choose a date
Use the month view for broad planning, or move directly to Week or Agenda if the team works better with a tighter operational surface.
Click New Appointment
Open the appointment modal and start with the required fields first: date, start time, and guest name.
Complete the booking details
Add status, end time, phone, email, booking purpose, guests / covers, location, and notes so the record is useful later, not just today.
Save and verify the day panel
After saving, confirm that the item appears where expected and that the selected day panel reflects the appointment clearly.
Update, complete, or delete as needed
When plans change, reopen the item, edit the modal, toggle completion, mark the right status, or delete the entry if the booking should no longer exist.
Screens / Interface Guide
The interface areas that matter most in Appointments
Toolbar strip
The top toolbar controls previous / next month movement, Today jump, active view selection, and the New Appointment entry point.
Legend area
The legend explains the visual meaning of scheduled entries and overdue / no-show emphasis so the user reads the calendar faster.
Month panel
This is the broadest planning surface, useful for understanding density, day distribution, and where the next busy dates sit in the month.
Week panel
Useful when the team wants a shorter planning horizon and quicker operational reading than the full monthly grid.
Agenda panel
Useful for users who prefer a clean list view of appointments rather than a visual calendar arrangement.
Day panel
The right-side day panel summarizes the selected day and lists the actual appointments that matter now, making it the practical action area after planning.
Appointment modal
The modal is the core data-entry surface. This is where staff create, edit, complete, or delete the actual appointment record.
Message area
The form message area reports save errors, validation issues, and backend state, so users should read it before assuming the module failed silently.
Common Workflows
Real examples of how teams use Appointments
Create a reservation or visit from scratch
Choose the date, open the modal, fill the required fields first, then add covers, location, and notes so the appointment is useful operationally and not just recorded.
Review today’s schedule fast
Use Today, then read the day panel immediately. This is the fastest way to see who is expected, at what time, and under what status.
Switch from broad planning to list execution
Use Month to understand density, Week to tighten focus, and Agenda to execute in list order when the day becomes operationally busy.
Handle a no-show or overdue case
Open the appointment, update the status to no-show when appropriate, and keep notes accurate so later reporting and daily decisions remain trustworthy.
Complete a finished visit
Once the booking is served or closed, mark it completed so today and upcoming counts stay meaningful instead of carrying stale items forward.
Troubleshooting
Common problems, likely causes, and the first fix path
The Appointments tab is not visible
Issue: the module does not appear in the shell or topbar.
Why it happens: the current account lacks the required capability, a filtered build disabled the module, or the admin shell did not finish loading.
What to do: test with an administrator-level account first, refresh the shell, and confirm the installation is not using a restricted module loader.
New Appointment does not save
Issue: clicking Save does not create the appointment.
Why it happens: one or more required fields are missing, the nonce expired, or the AJAX backend is not responding correctly.
What to do: check the form message area first, confirm date, start time, and guest name are filled, then refresh and try again with a fresh admin session.
The form says required fields are missing
Issue: the modal rejects the entry before save.
Why it happens: the module requires at minimum a valid date, a valid start time, and a guest name.
What to do: fill those three first, then add the remaining fields. Also make sure the date is in valid format and the time uses the expected time input.
Month, Week, or Agenda view feels empty
Issue: the screen loads but does not show expected appointments.
Why it happens: there are no saved entries for the current range, the selected date is outside the visible period, or the current records are cancelled / completed in ways you did not expect.
What to do: jump to Today, inspect the current month, and verify that records actually exist in the range you are viewing.
The day panel is blank
Issue: the right-side panel shows no appointments for the selected date.
Why it happens: the selected day has no records, the newly created item did not save, or the user is looking at the wrong date after navigation.
What to do: click the exact date again, use Today if needed, and confirm the record saved successfully before assuming rendering failed.
Edit works, but Delete is missing
Issue: the delete button does not appear in the modal.
Why it happens: the delete button is hidden for brand-new entries and only appears when editing an existing appointment.
What to do: save the item first, reopen it in edit mode, and the delete action should then be available.
Counts on Dashboard do not match expectations
Issue: the dashboard badge or today count feels wrong.
Why it happens: the appointments integration sends today and upcoming counts, but cancelled or completed states affect what should still be considered active.
What to do: verify the statuses of today’s records and then reload the dashboard shell to confirm the refreshed counts.
Phone, email, or notes save oddly
Issue: some optional fields look different after saving.
Why it happens: the module sanitizes backend values before storage, so malformed input may be normalized or stripped.
What to do: enter clean values, avoid pasting broken formatting, and retest with normal plain-text data.
The modal opens, but backend looks disconnected
Issue: the UI exists, but the module reports that the backend is not ready or not connected.
Why it happens: the local AJAX owner did not initialize correctly, the page loaded incompletely, or a custom build broke the local module bootstrap.
What to do: refresh the admin page, check for console or network errors, and confirm the appointment module assets and local AJAX owner are present in the build.
The documentation page looks broken in Elementor
Issue: layout or spacing looks wrong after embedding the snippet.
Why it happens: outside CSS overrides the wrapper or custom selectors were added beyond the namespaced surface.
What to do: keep the snippet self-contained inside the noesia-swa-matrix wrapper and avoid generic selectors that collide with site-wide styles.
FAQ
Fast answers before opening support
Is Appointments a free module?
Yes. Appointments belongs to the free tier.
What are the minimum required fields?
Date, start time, and guest name are the minimum required fields for saving an appointment.
Can I use Appointments for hospitality reservations?
Yes. The module is suitable for reservations, visits, bookings, front-desk scheduling, and similar appointment-style flows.
What statuses are available?
Scheduled, urgent, completed, cancelled, and no-show.
Does Appointments have more than one calendar view?
Yes. It includes Month, Week, and Agenda views.
Can I jump straight to today?
Yes. The toolbar includes a Today action for quick re-centering.
Can I track guest phone and email?
Yes. Phone and email are optional guest fields inside the modal.
Can I record covers or party size?
Yes. The module includes a Guests / Covers numeric field.
Can I assign a table or area?
Yes. The modal includes a Table / Area field for operational placement.
Can I edit an appointment after saving?
Yes. Existing appointments can be reopened and edited from the live interface.
Can I delete an appointment?
Yes. Delete is available when editing an existing saved appointment.
Does Appointments affect Dashboard counts?
Yes. Today and upcoming appointment counts can feed the wider shell and dashboard experience.
Is this module tied to one business type only?
No. It is hospitality-friendly, but the workflow also fits any business that needs structured appointment control.
Can I keep using the module if I do not fill every optional field?
Yes, but the schedule becomes more useful operationally when reason, location, covers, and notes are filled consistently.
The Noesia Matrix
⚙️ THE NOESIA MATRIX: KERNEL FABRIC ARCHITECTURE
The Noesia Matrix is the shared architecture language and module fabric behind Noesia Smart Waiter. This module is not just a static page; it sits inside an isolate-first modular system designed for shell-driven navigation, clean section ownership, extensible widget zones, and future-safe expansion.
The architecture direction is intentionally high-control: modular ownership, isolated assets, lazy-ready behavior, clean settings flow, predictable prefixes, maintainable service boundaries, and enterprise-safe discipline around structure, security, and extensibility. Noesia transcends the definition of a standard WordPress plugin, operating as a robust platform built upon enterprise-grade Service-Oriented Design.
Here is how the core engine is designed to minimize bloat, maximize stability, and keep the experience consistently fast and responsive:
Event-Driven Inversion of Control (IoC): The platform follows an IoC pattern via a decoupled Event Bus. The central core acts as a “Logic-Less Host” (Blind / DUMMY Kernel). It does not tightly bind itself to module internals; modules announce their own presence, capabilities, and state through controlled registration flows.
The Micro-Frontend Paradigm (MFE): The UI is not a giant monolithic block. Each application behaves as an independent Micro-Frontend with its own dynamic assets, specialized logic, and UI contracts.
Strict Asset Isolation & Lazy-Loading: Resource usage stays disciplined. A module’s CSS, JavaScript, and data components are loaded only when the user reaches or interacts with that specific application surface.
Decoupled Registry Pattern: The dynamic discovery layer allows applications to be added or removed quickly without rewriting core logic. If one application encounters an issue, the architecture is designed to contain that impact instead of cascading it across the platform.
Enterprise-Grade Security & Stability: The platform is reinforced with strict input sanitization, dynamic registry routing, and defensive safety gates across the stack. The data layer and the user interface remain deliberately separated for maintainability and risk control.
The Result: A scalable hospitality and clinical operating system engineered to manage mission-critical workflows securely — from intimate cafés to high-traffic venues and sensitive medical environments.
Support
Support, escalation, and what to send first
Check first
- Confirm the plugin version.
- Confirm the module name is Appointments.
- Check whether the problem is about saving, viewing, or status handling.
- Review the troubleshooting section above first.
Collect before opening a ticket
- One clear screenshot of the issue.
- The exact visible error text from the form or screen.
- Short steps to reproduce.
- Whether the issue happens always or only sometimes.
Open support only after the fast checks above
When you open a ticket, include one clean screenshot, the exact visible error text, short reproduction steps, and whether the problem is constant or intermittent. That reduces back-and-forth and speeds up resolution.
Open Support Explore Modules
Explore all modules of Noesia Smart Waiter
Enter the application layer: Explore the full Noesia Smart Waiter ecosystem and discover how each isolated module helps serve hospitality, operations, business workflows, and the wider mission to reimagine life through smarter software.
Scroll into the Matrix: The catalog below is the live gateway to the platform. Move through Free and Pro environments, open each documentation page, and step directly into the next application surface.
