Plan a restaurant information assistant

Build a restaurant information assistant for [restaurant name]. Use Properties for our published hours, public menu URL, address, and contact details. Create a menu with Opening hours, Menu, Booking request, and Talk to the team. Ask for the minimum details needed for a booking request and clearly say it is a request, not a confirmed reservation. Discover whether my organization can store requests in a database; if not, propose an available alternative rather than trying to bypass the plan. Include useful fallback paths and show how I can test each menu choice on a test Line.

Use the Chatigram plugin for organization [organization name]. Discover the current permissions, plan limits, triggers, node types, and compatible connections before designing the solution. For conversation workflows, check the selected Line’s Private AI mode before proposing Inbox follow-up or a human handoff. Do not promise human access to private AI conversations. Prepare and save the requested workflows disabled, after showing the draft preview and any unresolved setup. Do not activate, run, assign to a live Line, send messages, or use paid processing. If a paid capability or connection is needed, explain the service, account, transferred data, and required spending approval before adding or binding it. Do not ask me to paste credentials into chat; use protected setup links. Keep unrelated resources unchanged.

Finish with: what was prepared, what is still missing, which plan-dependent features are involved, and the next safe test. Do not claim execution or delivery from a draft preview.