Example prompts & recipes
You're here because
you’re connected and want ideas - real prompts, from a morning sales brief to designing a ticket, and what happens behind each one.
You don’t address tools – you just talk. The assistant reads your site’s tool catalog and picks the right calls. These prompts all map to real tools on a live site; adjust names and dates to your own events.
Sales & reporting
- “How did we do this weekend? Revenue and tickets per event.”
- “How many tickets have we sold for Saturday’s concert, and how many are left per ticket type?”
- “Compare check-in rates across this month’s events.”
- “Export the attendee list for Jazz Night as CSV.” – you get a download link, valid for 24 hours.
Event day, phone in hand
- “How many people are in so far?” – live sold / checked-in / remaining.
- “Has Marko Petrović arrived?”
- “Who from tonight’s guest list hasn’t arrived yet?”
- “Check in ticket TWP-1A2B3C4D.” – same rules engine as the door app; the assistant reports the exact result (entry allowed, already used, wrong event…).
Creating things from a sentence
- “Create a stand-up night on 15 August at 8pm at Club Amadeus, capacity 120, tickets at 15.” – the event and its ticket type are created as drafts; you get the edit link, review, and publish.
- “Make this event weekly, every Tuesday and Thursday at 20:00, until the end of December – show me the dates first.” – the assistant previews the schedule before saving the rule.
- “Upload this poster and set it as the event image.”
Seats
- “Which seats are still free in the VIP zone for tomorrow?”
- “Block seats A1 to A4 for the press.” – operator blocks, reversible with “unblock” anytime; sold seats are never touched.
- “Build me a seating chart: 10 curved rows of 12, a standing area at the back for 200, stage at the top.”
Attendee data
- “How many vegetarian menus do we need for the gala?” – aggregated from the meal-choice attendee field.
- “Add a t-shirt size field (S/M/L/XL, required) to the workshop ticket.”
Ticket design
- “Design a dark jazz-night ticket with the QR code bottom right and the venue name in gold.” – the assistant reads the design vocabulary, builds the template, and returns a preview link.
- “Send me the PDF for order #2041.” – a secure link that works without logging in and expires after 24 hours.
Point of Sale
- “Z-report for yesterday’s shift.”
- “POS sales this week, grouped by cashier.”
- “Refund order #1234, cash.” – money always moves in two steps: the assistant shows you the prepared summary first, and nothing happens until you say “confirm”. The confirmation expires after 10 minutes.
Getting better answers
- Name the event or the date range – “for Jazz Night” beats “for the concert”.
- Dates are your site’s timezone, so “tonight” and “this weekend” mean what you expect.
- Say “preview first” when changing schedules or layouts – preview tools exist precisely for that.
- Draft-first is your safety net – anything the AI creates waits for your publish click in wp-admin.
Was this article helpful?
No or only partly? Tell us what was missing