Your menu employee,
already on shift.

No. It is a managed employee environment configured around a defined menu role. It can triage and respond, route work, follow up, read approved SOPs and knowledge, collect or update approved records and documents, coordinate people and tasks, prepare summaries, use approved tools, request decisions, and hand off exceptions with context.

The demo is an isolated MenuCrafters workspace with synthetic restaurant data. You can explore Queue, Items, Recipes, SOPs, Channels, Approvals, and Change log, switch operating perspectives, and ask Mise to create a recipe sheet or SOP as a downloadable PDF directly in chat. Actions that would affect customers or connected systems are simulated and remain behind approval gates.

Yes. The role, operating menu, sources, workflows, tools, approval boundaries, branding, and recipe, SOP, and PDF templates are customized for each restaurant. This public demo keeps a deliberately bounded synthetic workspace so you can test the method without real business data.

Yes. The commercial role can be configured to work continuously on incoming tasks, use a controlled browser, research public sources, complete approved templates and documents, draft content, coordinate calendars or appointments, and operate approved tools and workflows. Those capabilities are enabled only when needed; sensitive or external actions stay permission-bound and human-approved.

Only within the permissions you approve. Price changes, allergen wording, dietary claims, and other sensitive edits should require a named human approval. The employee organizes and prepares the work; your team keeps final authority.

The offer is USD 100/month with no setup fee. Onboarding and up to three initial workflows are included in the monthly plan, along with Wobistro restaurant core, one role, one knowledge base, your chosen channel, the workflow method and templates, a private VPS, handoff rules, and activity summaries.

No. The employee works in the WhatsApp or Telegram channel your business chooses; no second number is required. During onboarding we agree which business-owned channel, participants, permissions, and escalation rules apply.

Yes. We configure up to three initial workflows and teach your team a practical method, with reusable templates, for creating and adjusting its own workflows. If you want us to design, implement, or integrate additional workflows, we scope and quote that work separately according to complexity.

The standard role can begin without a custom integration. If a workflow needs direct system access, we map the permissions and quote that integration separately before any credentials are connected.

We select up to three initial workflows, name each approved source, define permissions and decision owners, connect the business-owned WhatsApp or Telegram channel you choose, and agree how exceptions are handed off. We also teach the practical method and templates your team can use to create or adjust workflows later.

The employee does not guess which version is correct. It flags the conflict, shows the sources it found, and asks the named owner before preparing or publishing the affected change.

No. MenuCrafters remains the editable menu system, and your team retains editorial and operational authority. The employee handles the recurring coordination around that system within the role and permissions you approve.