Restaurant and café owners
Useful when the public QR experience needs stronger branding, cleaner action wording, and venue-specific button behavior.
Noesia Smart Waiter / Module Documentation
Free Event-Driven IoC Isolated/X-Core Micro-Frontend Customer QR Experience Surface
DESIGN / LIVE REQUESTS
Design / Live Requests is the customer-facing configuration surface of Noesia Smart Waiter. It controls brand setup, shop logo, action button labels and icons, menu visibility, optional custom actions, review CTA, color palette, sound alerts, and the live request preview that supports the real-time service experience on the QR page.
See more about how Live Command works
Open the dedicated presentation and discover the real-time service flow, customer request logic, and how Live Command operates inside the Noesia Smart Waiter ecosystem.
Open Full Presentation Who is it for
Built for venues that want a stronger customer QR screen without touching code
Managers and operations teams
Useful when the team wants to control the customer-facing screen, live request signals, and optional CTAs without developer work.
Brands with a visual standard
Useful for venues that care about logo, text, color palette, and button language consistency across every customer interaction surface.
Main Features
What Design / Live Requests actually controls
Brand setup
- Shop name shown on the customer QR page.
- Logo URL for the public-facing header area.
- Safe default fallback values when fields are empty.
Primary action buttons
- Menu button label and icon.
- Order button label and icon.
- Waiter button label and icon.
- Bill button label and icon.
Menu visibility & destination
- Show or hide the menu button.
- Attach a PDF or public page URL for the menu action.
- Control customer flow without editing templates.
Custom quick actions
- Two optional custom buttons for venue-specific needs.
- Editable labels and icons for each action.
- Useful for hotel, pool, urgent, or venue-specific calls.
Review CTA and live request preview
- Optional review button label and review URL.
- Compact live request preview inside the admin surface.
- Real-time awareness of current request activity.
Color palette and sound alerts
- Background, title, and text colors.
- Enable or disable sound alerts.
- Restore Texts & Icons reset action for fast recovery.
How to Access It
Where Design / Live Requests lives inside the platform
Admin path: open the Noesia Smart Waiter shell and select Design / Live Requests from the free module navigation.
Tier: this module belongs to the Free layer.
Public impact: the values configured here flow into the customer QR experience, button labels, optional review CTA, and visual identity of the customer screen.
Setup / Configuration
Recommended setup before you publish the customer-facing QR experience
Set brand identity first
Start with the shop name and logo URL so the customer screen reflects the actual venue identity from the beginning.
Define the primary customer actions
Review menu, order, waiter, and bill labels and icons so the public QR screen matches the real service flow of the venue.
Configure optional CTAs
Set custom buttons and review CTA only when they add real value to the guest flow instead of creating button clutter.
Finalize palette and alerts
Apply background, title, and text colors, then confirm whether sound alerts should stay enabled for the live request workflow.
How to Use It
Typical operator flow from setup to customer-ready screen
Open Design / Live Requests
Enter the module from the shell and start from the brand setup block before changing any action buttons.
Configure the main customer actions
Set labels, icons, menu visibility, and the menu destination so the QR screen matches the real venue journey.
Adjust optional CTAs and color palette
Add custom actions only where useful, set the review URL if needed, and tune the public-facing palette to the venue style.
Save and preview the result
Save changes, review the live request preview, and validate that the customer QR screen now reflects the intended experience.
Screens / Interface Guide
The interface areas that matter most in Design / Live Requests
Brand setup block
This is where the shop name and logo URL are defined for the customer QR screen.
Live requests preview
The compact preview shows the current request state from the live monitor so operators can understand what the customer layer is producing.
Primary action controls
The menu, order, waiter, and bill groups control the main buttons customers will actually tap.
Custom and review blocks
Custom Button 1, Custom Button 2, and Review CTA let the venue extend the public experience without editing templates.
Common Workflows
Real examples of how teams use Design / Live Requests
Brand a new venue QR screen
Set the shop name, upload the logo URL, pick the public palette, and save a customer-facing screen that already feels specific to the venue instead of generic.
Hide the menu button and push guests to direct service actions
Use menu visibility controls when the venue wants customers to focus on waiter, bill, order, or custom service requests instead of a menu destination.
Add venue-specific actions like pool, urgent, or room service
Configure the custom buttons with the exact labels and icons that reflect how the venue actually operates beyond the default restaurant actions.
Turn the QR page into a review and service touchpoint
Activate the optional review CTA and keep live requests visible so the same customer screen can support both service flow and feedback growth.
Troubleshooting
Common problems, likely causes, and the first fix path
The menu button does not appear on the customer page
Issue: customers cannot see the menu action.
Why it happens: menu visibility may be disabled or the public screen is still showing stale output.
What to do: confirm that Show Menu Button is enabled, save changes again, and clear any page cache involved in the public QR view.
The logo or brand image does not render correctly
Issue: the logo is missing or broken on the customer-facing screen.
Why it happens: the logo URL may be invalid, blocked, or pointing to an image that is no longer available.
What to do: paste a valid full image URL, save the module again, and reload the public page after cache is cleared.
Live requests preview shows nothing
Issue: the compact preview says there are no active requests.
Why it happens: there may truly be no active requests, or the request cycle has already been cleared or completed.
What to do: create a real test request from the customer side and confirm the live monitor is receiving it before rechecking the preview.
Restore Texts & Icons does not give the expected result
Issue: the button runs but the public screen still looks wrong.
Why it happens: old browser cache or cached public output can keep showing the previous version even after restore.
What to do: use the restore button, save changes, then clear cache and reload the public QR page in a fresh browser session.
FAQ
Fast answers before opening support
Is Design / Live Requests a free module?
Yes. It belongs to the free tier.
Does this module affect the customer QR page?
Yes. This is the main configuration surface for the customer-facing QR experience.
Can I change the button labels and icons?
Yes. Menu, Order, Waiter, Bill, and custom button labels and icons are editable from this module.
Can I hide the menu button?
Yes. Menu visibility can be switched on or off depending on the venue flow you want.
Can I add my own quick actions?
Yes. Two custom quick action slots are provided for venue-specific use cases.
Can I add a review button?
Yes. The module includes a review CTA with editable label and destination URL.
Can I change the colors?
Yes. Background, title, and text colors can all be configured from the palette controls.
Are sound alerts optional?
Yes. Sound alerts can be enabled or disabled depending on the venue setup.
What does Restore Texts & Icons do?
It resets key labels and icons back to their intended default values for a clean restart.
Does this module include a live requests preview?
Yes. A compact preview helps the team see current request activity from the live monitor layer.
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 Design / Live Requests.
- Check whether the issue is about branding, buttons, colors, live requests, or the public QR screen.
- Review the troubleshooting section above first.
Collect before opening a ticket
- One clear screenshot of the issue.
- The exact visible error text or wrong public-state behavior.
- Short steps to reproduce.
- Whether the issue happens always or only after certain settings are changed.
Open support only after the fast checks above
When you open a ticket, include one clean screenshot, the exact visible error text or wrong result state, 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.
