Skip to main content
Your assistant works out which storekit tools to call from what you ask. These prompts are a starting point; adapt the stores, dates and amounts to your own.
Three habits make answers more reliable:
  • Name the store when you have more than one (“at Soho”, “for the Brighton kiosk”). Without it, sales figures are added up across the account, which is refused when your stores use different currencies.
  • Say the period (“yesterday”, “last week”, “1 to 15 March”). Feedback, Google reviews and their summary default to the last 30 local dates; other tools have their own defaults. The longest single period is 90 local dates.
  • Ask for one thing at a time for the first few questions, then chain (“now compare that with the week before”).

​
Yesterday’s Numbers

Totals exclude rejected and cancelled orders (cash and pay-later orders are included). They are gross of refunds — ask for refunds separately (below) if you want a net figure. Figures for one store use that store’s local time; account-wide figures use UTC unless you specify a timezone.

​
What Sold

Prices shown alongside are the current menu prices, not what each unit sold for at the time.

​
Orders

By default orders are listed by when they are due (their scheduled time, or creation time if there is no slot). Say “placed on” or “created” if you mean when the customer ordered. Rejected and cancelled orders only appear when you ask for them.

​
Refunds

Refunds are shown by the date the refund was issued unless you ask by the order date.

​
Pay at Table

​
Feedback and Reviews

Feedback lists hide bare five-star ratings with no overall comment, item comment or item reason by default. Ask for ratings without written detail when you want to include them. There is no tool to reply to a Google review; reply from the dashboard instead (see Reply to Reviews).

​
Customers

Customer searches match email, first or last name, or phone. A customer profile needs an email address; ask the assistant to search first if you do not have one.

​
Snoozing

Snooze reports cover the whole period you ask for. If you want the individual on/off events for an item, ask for them and keep the period short — a busy week can exceed the 100-event cap per item.
This section includes writes that change customer-visible availability. Most clients ask before running a write, but only if you have not auto-allowed the tool — see permissions. Check the store, items and end time before you approve; for a store snooze, check the reason too. Item snoozes hide items from ordering until the end time, and a POS may overwrite a manual snooze on a POS-synced menu. A store snooze stops new orders, though pre-orders may continue if enabled. Review item snoozes under Reports → Products & Categories → Item Snooze, and store snoozes under Reports → Operations → Store Snooze.

​
Discount Codes

This section includes a write. Most clients ask before creating the code, but only if you have not auto-allowed the tool — see permissions. Check the code, amount, stores and dates before you approve, then confirm under Marketing → Discounts.
Types the assistant can create are: a fixed amount off, a percentage off, buy one get one free, and free delivery. It can set a minimum spend, a total or per-customer usage cap, a start and end date, and restrict the code to delivery, pickup or in-store. It cannot edit or archive a code once created — do that in the dashboard.
This section includes a write. Most clients ask before creating the link, but only if you have not auto-allowed the tool. Check the store, amount and expiry before you approve. A created link is live immediately and can take money.
A one-off link becomes Completed after one payment; a reusable link stays active (optionally up to a maximum number of payments). A fixed link has a set amount; a variable link lets the payer choose within optional bounds. The assistant can also set a description, an internal reference, an image, a thank-you message or a redirect after payment, and whether to collect the payer’s name, email, phone or business name. See Payment Links for how they behave once created.

​
When the Assistant Says No

Some answers are refusals by design: Anything else that looks wrong is covered in Troubleshooting.