New use cases, day by day.

You are the bookings lead of a padel or tennis club. Goal: plan WhatsApp offers that help my team fill off-peak courts. My input: [last month's bookings export, with day, time, court and player], [our prices and any off-peak price], [the list of players who agreed to receive offers, with the days and times they usually play], [our cancellation rules]. Give me: 1) our 10 emptiest slots by day and hour; 2) for each slot, the 5 opted-in players most likely to play then, and why; 3) a short, friendly WhatsApp offer for each slot in the player's language, with an opt-out line; 4) what my team must check before confirming a booking. Use only the data I gave you.

You are the membership lead of a pickleball, tennis or padel club. Goal: find which programs keep our players and plan follow-ups my team can approve. My input: [player export with first activity, programs joined, visits and spend over 12 months], [our programs and prices: open play, leagues, clinics, memberships], [the last 30 player emails or texts, copied as-is]. Give me: 1) average yearly spend and retention by first program; 2) the 3 player groups most worth inviting to another program, with numbers; 3) a short invitation for each group; 4) the inbox messages grouped by topic, with a draft reply for each routine one and the ones a person must handle. Use only my data.

You are the operations lead of a golf, tennis or padel club. Goal: cut lost bookings with confirmations and a waitlist my front desk can run. My input: [last month's bookings with date, time, player and status: played, cancelled or no-show], [our cancellation and no-show rules], [when the desk is staffed], [the questions players ask most outside opening hours]. Give me: 1) when cancellations and no-shows happen most, by day and time; 2) when to send a confirmation request and a short message for it; 3) simple waitlist rules: who gets offered a freed slot first and how long they have to answer; 4) answers to the out-of-hours questions, plus the ones to leave for staff. Use only my data.

You are the communications lead of a tennis or padel club or local tournament. Goal: turn match results into short reports my team checks before posting. My input: [the match scores, set by set], [any stats we have: aces, break points, match length], [player names, ages and club, with consent to publish], [our tone: friendly, local, no jokes about players]. Give me for each match: 1) a 60-word neutral report; 2) a 40-word version told from each player's side; 3) the 2 key moments, based only on the scores and stats given; 4) a one-line social caption. Flag anything you are unsure of. Don't invent shots, quotes or facts.

You are the content lead of a tennis or padel club, academy or tournament. Goal: adapt our best short video clips for fans who speak other languages; my team reviews everything before posting. My input: [the clip descriptions: players, score and what happens, second by second], [the 2 or 3 languages our community speaks], [our tone], [player names with correct spelling]. Give me for each clip and language: 1) a 15-second voice-over script that matches the action; 2) a caption under 150 characters; 3) 3 hashtags used in that language; 4) any word or name a native speaker should check. Don't add facts that aren't in my descriptions.

You are the customer care lead of a padel or tennis club. Goal: prepare the answers for an AI assistant that handles routine player questions in our chat or WhatsApp and hands the rest to our team. My input: [the 30 most recent player messages we received, copied as-is], [our booking, cancellation and refund rules], [opening hours, prices and court types], [who on the team takes over and how to reach them]. Give me: 1) the messages grouped by topic, with a rough share for each; 2) a short, clear answer for each routine topic, written in the player's language; 3) the topics that must always go to a person (disputes, refunds outside our rules, injuries, complaints), with the summary to pass on. Don't invent rules I didn't give you.

You are a safeguarding and social media moderator for a tennis or padel club or academy. Goal: sort the comments under our posts so a staff member reviews the worrying ones first. My input: [comments copied from our club accounts, with the post each appeared under], [our community rules], [the name of our safeguarding lead]. Classify each comment as OK, rude, abusive or serious (threats, sexual content, anything targeting a minor). Give me a table: comment, category, reason, suggested action (ignore, hide, report to the platform, escalate to the safeguarding lead). Put serious ones first. You only see what I paste, so don't decide alone: a person must check every abusive or serious case before acting.

You are an operations analyst for a tennis or padel tournament or club. Goal: find the one repetitive task an assistant could take over first to free up my staff. My input: [our team and roles], [a typical week or tournament day, task by task, with time spent], [the tools we use: booking software, spreadsheets, email, WhatsApp]. Give me: 1) a table of tasks with hours per week, how repetitive each one is, and the risk if it goes wrong, 2) the top 3 candidates to hand to an assistant, and why, 3) for the first one, a step-by-step setup plan and what a person must still check. Be honest about tasks that need hardware or human judgment. Output: the table, then the plan.

You are a sports data editor for a tennis or padel club, league or tournament. Goal: turn our match results into a stats page and posts our members will actually read. My input: [results for the period: players, scores, dates, categories], [any extra data: rankings, head-to-heads, winning streaks], [our audience: members, juniors, parents, local press]. Give me: 1) 5 stat highlights worth sharing, each with the calculation shown, 2) a short stats page: leaderboard table, form of the week, one notable head-to-head, 3) 3 social posts under 280 characters. Use only my data, double-check every figure, and say when a sample is too small to mean much. Output: highlights, page, posts.

You are a customer experience manager for a tennis or padel brand. Goal: draft the answers an assistant could give to our most frequent order, return and warranty emails. My input: [30 to 50 recent customer emails, anonymised], [our return, warranty and promotion policies], [sizing guide and product FAQ, if we have them]. Give me: 1) the email types, grouped and ranked by frequency, 2) one reply template per type, in our tone, with placeholders like [order number], 3) the questions that should go to a person, 4) the gaps you found: product, sizing or policy questions our documents don't answer. Use only my policies; never invent a delivery date or a refund. Output: a table, then the templates, then the gaps.

You are a customer service lead for a racket brand or a padel shop. Goal: set up a first version of an assistant that identifies the customer's order and sends them to the right answer or the right person. My input: [our main contact reasons, with rough volumes], [what an order number looks like and where customers find it], [our teams and what each one handles], [return, delivery and warranty policies]. Give me: 1) an opening script that asks for the order number and checks its format, 2) a routing table: contact reason, what the assistant answers alone, when it transfers and to whom, 3) 5 sample exchanges. Stick to our policies; when unsure, transfer to a person. Output: script, table, examples.

You are the front-of-house manager of a padel or tennis club. Goal: write the call script and knowledge sheet for a voice assistant that answers the phone when nobody on the team can pick up. My input: [why people call us, with a rough share of calls], [opening hours, prices, court types, lessons and events], [booking and cancellation rules], [who takes over complex calls and how to reach them]. Give me: 1) a short greeting and the questions to ask the caller, 2) answers to the 10 most common questions, written to be spoken aloud, 3) transfer rules, with the summary to pass to staff, 4) what to say outside opening hours. Keep sentences short. Output: script, FAQ, transfer rules.

You are a product designer for a tennis or padel booking service. Goal: map the chat a player should have with a booking assistant, so finding a slot takes a few messages instead of several screens. My input: [our venues and their courts], [how booking works today, step by step], [the questions players ask most], [what we know about a player: level, usual times, favourite venue]. Give me: 1) the ideal 4-to-6-message conversation, from 'I want to play Thursday evening' to a confirmed booking, 2) the data the assistant needs at each step, 3) what it should do when no slot is free. Mark every step that needs a live connection to our booking system. Output: the sample dialogue, then a checklist.

You are an operations consultant for a padel or tennis club. Goal: design a first version of a WhatsApp assistant that answers the club's routine messages, with staff taking over everything else. My input: [20 to 50 real WhatsApp messages we received, anonymised], [opening hours, court prices, cancellation rules and payment methods], [the booking software we use]. Give me: 1) the main message types, ranked by how often they appear, 2) a ready-to-use reply for each, in our tone, 3) the cases the assistant must hand to a person, 4) what it would need to connect to in our booking and payment tools to book and take payment for real. Do not assume any integration already exists. Output: a table of message types and replies, then the hand-off list.

You are a retention marketer for a padel or tennis club. Goal: plan a WhatsApp win-back campaign for players who have stopped booking. My input: [export or description of lapsed players: last booking date, how often they used to play, level, preferred days and times], [off-peak slots we need to fill], [offers we can afford, e.g. a discounted session or a free guest]. Give me: 1) 3 segments of lapsed players, with the rule that defines each, 2) one short, friendly WhatsApp message per segment, under 60 words, with a [booking link] placeholder, 3) a follow-up for non-replies after 5 days, 4) 3 numbers to track to judge the campaign. Only target players who agreed to be contacted on WhatsApp. Output: a table, then the messages.

You are the digital editor of a tennis or padel tournament. Goal: give fans a quick, accurate recap and a short Q&A for every match, written from our own results. My input: [tournament name and round], [results with set-by-set scores], [any stats we have: aces, break points, match length], [notes from the desk: key moments, quotes]. For each match, write: 1) a 3-sentence recap, 2) 3 questions a fan might ask, answered only from my data, 3) one social post under 280 characters. Never invent stats, quotes or moments that are not in my input; write 'not in the data' instead. Output: one block per match, in the order I gave them.

You are a tennis performance analyst helping a club or academy coach. Goal: turn the match data I already have into a short, practical performance report for one player. My input: [player name, level and age], [stats or notes from recent matches: first-serve %, double faults, unforced errors, winners, second-serve points won...], [what the coach sees in training], [the player's next goal or tournament]. Using only what I paste, give me: 1) the 3 strengths and 3 weaknesses the data supports, 2) a 2-week practice plan with 3 drills per weakness, 3) 3 numbers to track at the next match. Flag anything the data is too thin to support. Format: headings and bullet points, one page maximum.