scenario map
Your scenario map
Pick your business, answer two questions, see what your customers and your team could do in an AI chat.
1. Pick your business
Clinics and medical practicesOnline shops and e-commerceLocal and on-site servicesPrivate education and tutoringProfessional services and agenciesRestaurants, cafés and barsSaaS products and customer supportSalons and beauty studiosSomething close to theseNot on the list? Pick the nearest one, and on the call we map that playbook onto your actual business.
2. Answer two questions
Your map
Or browse all 8 maps
Every map is on this page already, no answers required.
→Clinics and medical practices
Clinics and medical practices
Your customers
- Find and book the right appointment. "I need a check-up with a hygienist in the next two weeks, mornings only" — the assistant matches practitioner, appointment type and your real availability.
- Get practical answers before coming in: what to bring, how long the visit takes, how preparation works, which insurers you work with — from your own practice information.
- Reschedule or cancel a booked visit, within your notice rules.
- Ask what a procedure involves in plain language, from text your practitioners approved.
- Handle the paperwork trail — request a referral, ask for a receipt or a document — routed to the right person at your practice.
Your team
- Open the day in one question. Tomorrow's list per practitioner and per room, read from your scheduling system.
- See what needs chasing: unconfirmed appointments, overnight cancellations, reschedule requests waiting for an answer.
- Pull the administrative context before a call — visit history, documents requested, insurer on file.
- Adjust the schedule from the chat: move an appointment, block a slot, mark a no-show — each change confirmed before it fires.
→Online shops and e-commerce
Online shops and e-commerce
Your customers
- Find a product by describing it, not by guessing your search keywords: "a waterproof jacket for cycling, under a hundred, in stock in medium".
- Check real stock and delivery dates for a specific variant, instead of a generic shipping page.
- Ask the questions that block a purchase — sizing, materials, care, compatibility — answered from your product data and policies.
- Track an order: "where is my parcel?" answered from your fulfilment system rather than from imagination.
- Start a return or exchange and get told exactly what your policy allows.
- Reorder a consumable they have bought before.
Your team
- See what needs attention: orders unfulfilled past your own threshold, deliveries running late, returns waiting for a decision.
- Answer a support message with the facts open — the customer's orders, delivery state and return history in one question, before typing a reply.
- Check stock the way you actually think about it: "what is running low in the winter line", across variants, from the same catalog API.
- Get the day in one digest: what sold, what came back, what got stuck — numbers read from your systems, not estimated.
→Local and on-site services
Local and on-site services
Your customers
- Describe the problem and get a real next step. "My boiler is making a knocking noise, can someone come this week?" — the assistant asks the qualifying questions your intake form asks, then offers genuine visit slots.
- Check whether you cover their address and what the callout terms are for it, before anyone's time is spent.
- Book a visit window that matches your dispatch reality — the crew, the travel time, the equipment.
- Ask for an indicative estimate from your own price list, framed exactly as your business frames it — a range and its conditions, never a number the model made up.
- Track a job: when is the technician coming, what happened on the last visit, is the part in.
Your team
- Open the morning in one question. Today's jobs, who is assigned where, which visit windows are tight.
- See what is unassigned — jobs without a crew, gaps in this week's schedule worth filling.
- Pull the job context before knocking: what the customer reported, what happened on the last visit, whether the part arrived.
- Update a job from the road: move a visit window, log an outcome, flag a follow-up — each change confirmed before it fires.
→Private education and tutoring
Private education and tutoring
Your customers
- Book a trial lesson in one sentence. "My daughter is 9, we want to try English on weekday evenings" — the assistant matches level, group and your real schedule, and confirms a trial.
- Move a lesson without the guilt call. A sick child at 7am becomes a reschedule inside the chat, within your notice rules.
- Ask what a program actually involves — levels, group sizes, how long until results, what the difference between two courses is — answered from your own program descriptions, not from the model's imagination.
- Keep the money side clear: what is paid, how many lessons are left on the package, when the next payment is due, with payment by a secure link.
- Enroll the second child or renew a package as a confirmed action, not a form hunt.
Your team
- Open the day in one question. Today's groups, rooms and teachers, read from your schedule, not from a whiteboard photo.
- See what needs a call: trials that did not convert, packages ending this month, absences piling up for one student.
- Pull the context before talking to a parent — attendance, progress notes, payment state — instead of asking a colleague who remembers.
- Adjust the schedule from the chat: move a lesson, mark an absence, block a room — each change confirmed before it fires.
→Professional services and agencies
Professional services and agencies
Your customers
- Ask "where are we?" and get a real answer. Project status, what shipped this week, what is waiting on their side — read from your project tracker, not from a manager's memory.
- Book a call with the right person — their account manager, not a generic inbox — against the team's real availability.
- Check the money side without an awkward email: what the retainer covers, which invoices are open, when the next one lands.
- Hand over what you are waiting for. The assistant tells them exactly which access, file or approval is blocking work, and confirms when it is in.
- Ask what a service involves — timelines, what is in scope and what is not — answered from your own service descriptions, framed the way you frame them.
Your team
- Open the week in one question. Active projects, deadlines this week, which clients have not heard from you lately.
- See what needs attention across tools — stale proposals in the CRM, unbilled work in the tracker, invoices overdue in the books — in one answer instead of three tabs.
- Pull the client context before a call: history, open items, last invoices, who promised what — instead of scrolling three threads.
- Log the outcome from the chat: a follow-up task, a note on the account, a nudge to billing — each change confirmed before it fires.
→Restaurants, cafés and bars
Restaurants, cafés and bars
Your customers
- Reserve a table by describing the occasion: "a table for four on Friday around eight, somewhere quiet" — the assistant reads your real availability and confirms.
- Ask the menu real questions. What is gluten-free tonight, what changed on the seasonal menu, what goes with a dish — answered from your actual menu data, with allergens straight from your source of truth rather than guessed.
- Order for pickup or delivery, where your ordering system supports it, without leaving the conversation.
- Handle the group logistics: change the party size, note a birthday, add a high chair — the details that usually cost a phone call.
- Find out what is on — set menus, tastings, live music — from your events data.
Your team
- Open the service in one question. Tonight's covers, the large parties, the notes that matter — birthdays, high chairs, allergies guests flagged.
- See the load per seating: which slots are full, which tables are still free, where a walk-in could fit.
- Catch the overnight changes: cancellations, shrunk parties, no-shows worth a follow-up.
- Adjust the book from the chat: hold a table, move a reservation, close a slot — each change confirmed before it fires.
→SaaS products and customer support
SaaS products and customer support
Your customers
- Get answers grounded in your documentation, with the source attached, so a user can check what they were told instead of trusting a paraphrase.
- Ask about their own account: which plan, what usage this month, when the renewal falls, why an invoice looks the way it does.
- Do the routine account jobs — invite a teammate, rotate a key, change a notification setting — as explicit, confirmed actions.
- Open a support ticket with the context of the conversation already attached, so your team does not start from "hi, what happened?".
- Follow a setup path step by step, with the assistant checking your API for whether each step actually took effect.
Your team
- Walk into a call prepared. One question pulls the account's plan, usage, renewal date and open tickets — instead of four dashboard tabs.
- Triage the queue with the facts attached: each new ticket next to the account's actual state, so priority calls are made on data.
- Watch the edges: which accounts hit their limits this week, whose renewal is coming, who went quiet after an incident.
- Do the routine account jobs for a customer — resend an invoice, adjust a setting — as explicit, confirmed actions logged to the account.
→Salons and beauty studios
Salons and beauty studios
Your customers
- Book an appointment in one sentence. "Book me a haircut with Marina on Saturday afternoon" — the assistant checks who is free, offers the real open times, and confirms one.
- Pick by person, service or time. A specific stylist, a specific treatment, or simply "the first slot after work this week".
- Reschedule or cancel without a phone call, inside the same conversation.
- Ask what a service involves — how long it takes, what to come prepared with, what the difference is between two treatments — answered from your own service descriptions, not from the model's imagination.
- Rebook what they had last time, once the connector can see their history.
Your team
- Open the day in one question. "Who is booked with whom today?" — the schedule, read out from your booking system, not from a printout.
- Spot the money leaks: which slots are still empty tomorrow, who cancelled overnight, which regulars have not rebooked.
- Check a client before they sit down — last visit, usual treatment, notes your team left.
- Move the schedule from the chat: block a slot, shift a booking, mark a no-show — each change confirmed before it fires.
Talk your map through
The same diagnostic runs inside our own connector, live in Claude. Bring your map to us and we will tell you what the first build would actually cover.
green
yellow