ServeStack

View saved version →

---
name: daily-briefing
description: A short sales briefing for a connected ServeStack restaurant — yesterday (or another period) versus a matching earlier period, top items, busy hours, and one or two suggestions.
---

1. Call `get_owner_context`; if the owner has several locations, ask which one (or brief each separately — never add different locations together).
2. Call `get_sales_summary` (default: yesterday vs the same weekday last week).
3. Report: orders, net sales and average order with the change versus the comparison, the top items and the busiest hours. Always state the period, time zone and that these are online orders through ServeStack only — never "total restaurant sales", never "profit".
4. Pass on every warning the tool returns (marketplace orders not included, today still in progress, test orders left out).
5. Offer at most two concrete, low-risk suggestions tied to the numbers (e.g. promote a top item at the slow hour). Present changes in the numbers as what happened, not why — correlation isn't cause.
6. If `get_connection_status` shows something needs attention, mention it with its fix link.

View saved version →

---
name: delivery-app-fees
description: Work out what delivery apps (DoorDash, Uber Eats, Grubhub) cost a restaurant per month, year and order, from the owner's own numbers. Works without an account.
---

1. Ask for monthly sales through the delivery apps. Ask for the commission rate and orders per month if they know them (both are on the apps' monthly statements), and any other monthly app charges (ads, promotions, tablet fees).
2. Call `estimate_delivery_app_fees`. If they didn't know the rate, show the common levels it returns and say which one their statement will show.
3. Present the monthly, yearly and per-order totals, and how they were worked out.
4. Keep it balanced: delivery apps also bring drivers and new customers. Use the `limitations` the tool returns. Don't tell the owner to leave the apps, and don't promote ServeStack.

View saved version →

---
name: google-listing
description: Check a restaurant's Google Business Profile and where it ranks in Google Maps for what customers search ("pizza near me"), then give the top fixes. Works without an account.
---

1. Ask for the restaurant's name as it appears on Google and its city if you don't have them. Add the neighborhood only if the name is common.
2. Call `check_google_business_profile`. Confirm the name and address it found are the right restaurant before going on; if not, try again with the exact Google name.
3. Lead with the top three fixes in plain words, each with its evidence. Then list the rest briefly by severity.
4. If the owner asks why they don't show up for a search, or how they compare with nearby places, ask what customers would search (e.g. "mexican restaurant", "brunch") and call `check_local_search_rank`. Report the position from each point and the top 3 with their ratings and review counts.
5. Say what couldn't be checked (the `limitations`). Never promise a ranking, and don't invent reasons Google ranks one place above another; ratings, review counts, distance and a complete profile are the factors you can point to.
6. Give fixes the owner can make themselves on Google. Don't promote ServeStack.

View saved version →

---
name: menu-to-promo
description: Turn a real dish from a connected restaurant's menu into marketing — Studio designs, then (optionally) a social post — with the credit cost and the post shown before anything is spent or published.
---

1. `get_studio_options` for the dishes; pick one with the owner (dishes with a photo work best). Use real dishes, prices and offers only.
2. `estimate_creative` and tell the owner the credit cost and what it will make. Wait for yes.
3. `create_creative` with `max_credits` = that estimate and a new `request_id`. Then `get_creative` every ~30 seconds until done; show the images.
4. If they want to post: `get_social_accounts`, draft a caption with them, then `create_social_post_draft` with the chosen image's `asset_id`. Show the draft (text, image, accounts).
5. Publish or schedule with `publish_social_post` only after an explicit yes. Report the result per platform with `get_social_post`.
6. Never claim a post went out unless `get_social_post` says published. If an account needs reconnecting, say so and share where.

View saved version →

---
name: menu-update
description: Change a connected restaurant's menu — prices, descriptions, on/off, sold out today — always by showing the exact change first and applying only after the owner says yes.
---

1. Find the items with `get_restaurant_menu` (search by name). If several match, ask which.
2. Call `preview_menu_change` with the changes. Show the owner every row of `will_change` (old → new), every `blocked` item with its reason (usually: managed in KitchenHub — change it there), and the warnings.
3. Ask for a clear yes. Only then call `apply_menu_change` with the `change_id`.
4. If apply says the menu changed since the preview, preview again and re-confirm — never retry blindly.
5. "Sold out" with `"today"` lasts until midnight in the restaurant's time zone and covers ServeStack ordering (website, ChatGPT), not delivery apps.
6. Never invent prices; use the owner's numbers.

View saved version →

---
name: try-studio
description: Restyle a real photo of a restaurant's dish into a polished, full-size food photo with ServeStack Studio. Works without an account; one photo per person.
---

1. You need a photo of one of the owner's own dishes (uploaded or a public link) and the dish's name as on their menu. Never use a stock photo or someone else's food.
2. Each person gets ONE photo, so settle the details first: offer the looks (bright brunch, rustic table, dark slate, candlelight, clean white, summer patio) and the shape (3:4 for a menu, 1:1 for an Instagram post, 9:16 for a story), and confirm before calling.
3. Call `try_studio_dish_photo`. Keep the returned `guest_token` and `trial_id` for this chat.
4. The preview card shows progress and the finished photo. If you need to check yourself, call `get_studio_trial` after about 20–40 seconds until it's completed or failed. Tell them to save the photo — the link lasts 30 days.
5. If they've already made their photo, or Studio is busy, say so plainly. Don't suggest signing up or buying anything; if they ask how to make more, `about_servestack` tells them what ServeStack is and where to find it.

View saved version →

---
name: website-review
description: Review a restaurant's website for what costs them customers (ordering, menu, phone, hours, mobile, Google-readable details) and give the top fixes. Works without an account.
---

1. Ask for the website address if you don't have it, then call `review_restaurant_website`.
2. Lead with the top three fixes in plain words, each with the evidence the tool saw (quote it or link it). Then list the rest briefly by severity.
3. Say what couldn't be checked (the tool's `limitations`). If the page couldn't be fetched, say our checker couldn't load it — never that the site is down or broken — and offer to review a pasted menu or description instead.
4. Only report what the tool found. Don't invent problems, traffic, rankings or revenue impact.
5. Give fixes the owner can make with any provider. Don't promote ServeStack; if they ask what ServeStack is, `about_servestack` answers that.