Get the Most Out of Ding
Use Ding as a daily operating system for your restaurant: keep the source data clean, make the agents live, review the work, and approve the highest-impact actions.
Think of Ding as an operating loop
Ding works best when it has accurate restaurant context and a regular review habit. The loop is simple: keep your menu and settings current, let the Waiter Agent answer guests from that source of truth, use the Ops Agent to spot opportunities, then approve or refine the work that matters.
- Use Settings as the source of truth for restaurant profile, branding, team access, and integrations.
- Use Menu and Settings to keep the live guest experience accurate and polished.
- Use Waiter Agent for table-side guest questions, recommendations, dietary help, and QR flows.
- Use the Operations Agent (open it from Ask Ding) for goals, campaigns, forecasts, menu work, and owner decisions.
Set the foundation first
Most weak agent output comes from weak inputs. Before judging the agents, make sure Ding knows what kind of restaurant it is running for and what guests should actually see.
- In Settings > Restaurant, confirm the name, description, address, cuisine type, restaurant type, operating hours, contact info, and live status.
- In Settings > Appearance, add the logo, hero image, mascot, and brand colors that should carry into customer-facing surfaces.
- In Menu, review item names, descriptions, prices, sections, photos, dietary notes, and availability.
- In Settings > Integrations, connect Square, Clover, or Toast when available so forecasting and business insights can use real operating data.
Make Waiter Agent useful before you print QR codes
The Waiter Agent is the guest-facing part of Ding. Treat setup like training a strong server: give it menu context, teach it the house style, then test the answers before guests rely on it.
- Turn the agent on only after the menu is accurate enough for guests.
- Choose the right waiter specialty for the whole restaurant or for each menu section.
- Upload useful Knowledge Base files such as wine notes, catering rules, allergen references, seasonal specials, or service policies.
- Customize the greeting, appearance, and QR color so the experience feels like the restaurant.
- Test real guest questions about allergies, substitutions, specials, pairings, calories, popular items, and budget before going live.
Use Home as your daily command surface
The Home tab is designed to tell an owner what needs attention without making them dig through every feature. Check it at the start of the day and again before service if the restaurant is busy.
- Finish the setup checklist: menu, Waiter Agent, POS, and team access.
- Read the daily briefing for a fast view of sales pace, weather, engagement, guest activity, ratings, and context.
- Review your goals so Ops recommendations have a target instead of drifting into generic advice.
- Use What I would do today as the action queue for high-impact work.
- Check Ops - Waiter sync to confirm the Waiter Agent, restaurant page, and POS data are current.
Give Ops Agent a business goal
The Operations Agent is strongest when the owner gives it a concrete business direction. Instead of asking broad questions, start with the outcome you care about and let Ops turn that into analysis, campaigns, forecasts, or menu actions.
- Good prompt: Help me increase Tuesday dinner traffic without discounting the whole menu.
- Good prompt: Build a campaign around our high-margin pasta dishes for next weekend.
- Good prompt: Forecast Saturday demand and tell me what to prep more carefully.
- Good prompt: Find menu items that look popular but may be hurting margin.
- Good prompt: Help me set a goal for this week and track what changes it.
Review, approve, and teach the system
Ding is not meant to hide work from the owner. It should reduce the busywork while keeping important decisions visible. Review agent work, approve what is ready, and correct anything that does not match the restaurant.
- Review generated campaign content before you post it, checking the tone, offer, and featured items.
- Record campaign outcomes so future recommendations learn what actually worked.
- Approve menu edits and operational actions only when they match the real restaurant state.
- Dismiss low-value actions so the queue stays useful.
- Use follow-up prompts to correct tone, assumptions, or missing context instead of starting over.
Bring the team in deliberately
Ding becomes more valuable when managers, operators, and service staff know which parts of the system they own. Add people when there is a clear job for them, then keep permissions aligned with responsibility.
- Invite managers or operators through Settings > Team.
- Keep billing and owner-level access limited to trusted admins.
- Have service staff test Waiter Agent questions they hear on the floor.
- Have managers review goals, action queue items, forecasts, and campaign tasks before service.
- Use Ding as the shared context layer instead of scattering updates across texts and screenshots.
Keep the source data clean
The agents stay reliable when Ding can derive answers from current database-backed restaurant records. A few minutes of cleanup each week prevents drift between what Ops recommends, what Waiter says, and what guests see.
- Mark sold-out or unavailable items quickly instead of leaving them live.
- Update prices, descriptions, and section placement when the printed or POS menu changes.
- Remove outdated specials or policy docs from the Knowledge Base.
- Check POS sync after changing locations, credentials, or menu structure.
- Open the public restaurant page after major changes and inspect it like a guest.
A simple weekly rhythm
If you want the shortest useful habit, follow this rhythm. It keeps Ding close to the restaurant without turning the dashboard into another full-time job.
- Monday: set or review your goal in the Operations Agent.
- Daily: read the briefing and clear the top action queue item.
- Before service: confirm Waiter Agent, restaurant page, and POS sync status.
- After campaign work: review the generated content, copy and post it, and note the outcome later.
- End of week: clean menu data, archive stale context, and decide what Ding should focus on next.