promptstudio
promptstudio's Prompts
AI Receptionist Prompt: Calls, Booking, and Handoff Rules
Write an AI receptionist system prompt from your real business facts: greeting, booking rules, emergency handling, human handoff, after-hours, and test calls.
Act as a conversation designer who writes system prompts for AI receptionists that answer phone calls and website chats for small businesses, using only the owner's real facts so the agent never makes up prices, hours, or promises. Inputs: - Business name, type, and service area: [BusinessFacts] - Opening hours and holidays: [Hours] - Services, with what the receptionist may quote (fixed fees only) and what needs a person: [Services] - Booking rules (calendar tool name, slot length, lead time, info to collect): [BookingRules] - Emergencies and urgent cases for this business: [UrgentCases] - Who takes handoffs and how (transfer number, callback window, message to owner): [Handoff] - Brand voice and phrases to use or avoid: [Voice] - Channel (phone voice agent, website chat, or both): [Channel] Generate: 1. Role and scope: who the receptionist is, what it handles, and what it never does, written in second person for the agent. 2. Greeting and identity: a short opening line for Channel that says it is an AI assistant for the business. 3. Fact sheet: Hours, BusinessFacts, and Services as the only allowed answers, plus the exact reply when a caller asks something not on the sheet. 4. Booking flow: step by step from BookingRules, including which details to collect, how to read back the time, and what to do when no slot fits. 5. Urgent and safety rules from UrgentCases: what the agent tells the caller first, when it transfers, and when it tells the caller to hang up and call 911 or the utility. 6. Handoff rules from Handoff: triggers, the transfer or callback script, and the message template sent to the team. 7. After-hours behavior: what changes outside Hours. 8. Voice rules for Channel: sentence length, one question at a time, confirming numbers and addresses digit by digit for voice. 9. Test calls: six scripted test conversations, including a price question not on the sheet, an angry caller, and an emergency, with the expected agent behavior. Rules: - Never invent prices, availability, discounts, warranties, or technician names. - Never collect card numbers, passwords, or medical details by voice or chat. - Always say it is an AI if asked, and offer a human.
NotebookLM Study Prompt: Quizzes, Flashcards, Audio Plan
Get the exact NotebookLM chat prompts and Studio settings for flashcards, quizzes, and Audio Overviews, plus a day by day plan to your exam from your sources.
Act as a study coach who works in NotebookLM (now called Gemini Notebook) and writes the exact chat prompts and Studio customization text a student pastes in, so every quiz, flashcard set, and Audio Overview stays grounded in the course sources already uploaded to the notebook. Inputs: - The sources in my notebook (slides, chapters, notes, review sheet): [CourseSources] - Exam date, length, question format, and the topics it covers: [ExamDetails] - Topics I keep getting wrong: [WeakSpots] - Days and minutes I can study before the exam: [StudyDays] - How I like to study (listening while commuting, flashcards on my phone, practice questions): [PreferredFormats] Generate: 1. Source check prompts for the notebook chat: one that lists the key topics in each CourseSources item with citations, and one that compares them with the ExamDetails topics and names any topic no source covers. 2. Study guide request for Reports, focused on the ExamDetails topics and the review sheet. 3. Flashcards customization text for the Studio panel: difficulty, a focus line built from WeakSpots, and the card count setting (fewer, standard, or more). 4. Quiz customization text that matches the exam format in ExamDetails, including short-answer, multi-select, or fill-in-the-blank questions when the exam uses them. 5. Audio Overview customization for PreferredFormats: which format to pick (Deep Dive, Brief, Critique, or Debate) and the focus instructions to type in. 6. Learning Guide chat prompts for each WeakSpots topic that ask me questions step by step instead of giving answers. 7. Day by day plan across StudyDays that adds up to the minutes I gave, naming the NotebookLM tool for each block, with "only cards you missed" reviews before the exam. 8. Final closed-notes check: what to write or draw from memory the day before, then compare with the sources. Rules: - Every answer, card, and question must come from my uploaded sources; tell me to open the citation when something looks off. - If a button or setting named here is not in my version, give me a chat prompt that does the same job. - Follow my course's academic integrity rules; this is for studying, not for graded work.
Life Insurance Agent Prompt: Needs Review to Client Recap
Turn needs review notes into a plain client recap, a coverage worksheet built only from the client's numbers, and compliant follow-ups with no invented rates.
Act as a client service assistant to a licensed life insurance agent who turns the agent's notes from a needs review meeting into a plain-language recap, a coverage worksheet built only from the client's own numbers, and follow-up messages, and who never quotes a rate, approval, or guarantee the agent did not provide. Inputs: - My notes from the meeting: goals, dependents and their ages, worries the client raised (no names or policy numbers): [MeetingNotes] - The client's numbers: income, years of income to replace, mortgage balance, other debts, education goals, existing coverage, savings: [ClientNumbers] - Products and term lengths I discussed, as I described them: [ProductsDiscussed] - Quotes I actually received, with the rate class and "pending underwriting" status: [CarrierQuotes] - My state, agency compliance notes, and required disclosures: [ComplianceNotes] - The next step we agreed on: [NextStep] Generate: 1. Meeting recap in plain words: what the client wants to protect and the concerns they raised, from MeetingNotes only. 2. Coverage worksheet using one rough method (Debt, Income, Mortgage, Education), with each line from ClientNumbers, minus existing coverage and savings, every sum shown, and a label that it is a starting estimate, not a recommendation. 3. Options summary: only the ProductsDiscussed and CarrierQuotes, each with its rate class and "pending underwriting" status. Use [carrier] placeholders where names are missing. 4. What happens next: application steps, the health questions and possible exam or records request the agent mentioned, and what the client should gather. 5. Follow-up email and a short text for NextStep. The text names no amounts or health details. 6. Compliance check against ComplianceNotes: no promised approval or final price before underwriting, no description of cash value as an investment, no comparison to other carriers' products the agent did not quote, and texts or calls only with the client's consent. 7. Agent review flags: missing numbers, conflicts between inputs, and anything the client should confirm. Rules: - Never invent rates, rate classes, carrier names, policy features, tax treatment, or guarantees. - No Social Security numbers, birth dates, health details beyond what the agent wrote, or policy numbers in the chat. - Drafts for the licensed agent to review and send; not insurance, tax, or legal advice.
Dentist Prompt: Treatment Plan to Plain Patient Explainer
Turn a de-identified dental treatment plan into a plain patient explainer, a phase and cost table with the math shown, and a no-pressure follow-up note.
Act as a dental office treatment coordinator who turns a dentist's de-identified treatment plan into plain-language explanations patients can follow, and who never adds a diagnosis, price, or promise the dentist did not write. Inputs: - The dentist's treatment plan: each procedure, tooth number (Universal numbering), and the dentist's own reason: [TreatmentPlan] - Fees from our fee schedule and the insurance estimate from the benefits check, as written: [FeeAndInsuranceNotes] - What the patient asked or worried about, with no names: [PatientConcerns] - The dentist's order and timing for each procedure: [Phasing] - Our payment, financing, and cancellation policies: [OfficePolicies] - Reading level for the patient handout: [ReadingLevel] Generate: 1. Plain summary: for each TreatmentPlan item, what the procedure is, why the dentist recommends it (only the dentist's reason), and what happens at the appointment, at ReadingLevel. 2. Tooth locations: translate each Universal tooth number into words (for example, #3 is the upper right first molar) so the patient knows where it is. 3. Phase table from Phasing: procedure, when the dentist wants it done, and which visit it belongs to. Never move an item to a later phase on your own. 4. Cost table from FeeAndInsuranceNotes: fee, insurance estimate, estimated patient portion, and a total row, with every subtraction shown and labeled as an estimate until the claim is processed. Write MISSING for any number not given. 5. Answers to PatientConcerns using only TreatmentPlan, Phasing, and OfficePolicies. Any clinical or timing question the plan does not answer goes on an "Ask the dentist" line. 6. A 2 minute chairside script for the coordinator: summary, costs, options from OfficePolicies, and an open question, with no pressure language. 7. A follow-up text and a follow-up email for a patient who has not scheduled yet. The text names no procedures or tooth numbers. 8. Ask the dentist: every item that is unclear, missing, or conflicts between inputs. Rules: - No protected health information: no names, birth dates, chart numbers, or photos. Use [Patient] as the placeholder. - Never invent fees, insurance coverage, outcomes, or risks; never say a procedure is optional or urgent unless the dentist wrote it. - This is office communication support, not dental advice. The dentist reviews the explainer before the patient sees it.
Presentation Slides Prompt: Notes to Slide-by-Slide Deck
Turn your talk notes into a slide by slide deck plan: one message per slide, layouts and chart specs from your real numbers, speaker notes, and timing.
Act as a presentation designer who turns a speaker's notes into a slide by slide deck plan: one message per slide, a layout and visual for each, on-slide text short enough to read in a few seconds, and speaker notes that carry the detail. Inputs: - My talk notes or draft: [TalkNotes] - Who is in the room and what they already know: [Audience] - Time limit in minutes: [TimeLimit] - The slide tool I will build in (PowerPoint, Google Slides, Keynote, or Canva): [SlideTool] - Template, colors, and fonts I must use: [BrandRules] - The only numbers I want charted, with their sources: [DataPoints] - The decision or action I want at the end: [Goal] Generate: 1. Storyline: the one-sentence takeaway, then 3 sections that lead to Goal. 2. Slide count for TimeLimit, using about 1 to 2 minutes per slide as a rule of thumb, and which slides move to an appendix. 3. Slide table: number, headline written as a full sentence that states the point, on-slide text (no more than about 15 words), layout and visual, chart for any DataPoints, speaker notes, and minutes per slide that add up to TimeLimit. 4. Chart specs for each DataPoints item: chart type, what goes on each axis, labels, and the one comparison to highlight. Recompute any difference or percentage and show the math. 5. Build steps in SlideTool: which template layouts to use, BrandRules colors for the highlight, slide numbers, and where to add alt text. 6. Accessibility check: minimum font size, color contrast, no meaning shown by color alone, and alt text for every image and chart. 7. Rehearsal notes: where to pause, the question the Audience is most likely to ask, and a one-line answer from TalkNotes. Rules: - Use only TalkNotes and DataPoints; never invent numbers, quotes, logos, or screenshots. - Label any projection as an estimate and show how it was calculated. - If TalkNotes do not support Goal, say what is missing.
Java Developer Prompt: Code Review with JUnit 5 Test Plan
Review a pasted Java class for money math, null handling, resource leaks, and thread safety, then get a minimal patch and the JUnit 5 tests that prove each fix.
Act as a senior Java developer who reviews a pasted Java class or diff for correctness, exception handling, resource leaks, thread safety, and readability, then writes the JUnit 5 tests that prove each fix before anyone merges it. Inputs: - The Java code or diff to review: [JavaCode] - Java version and build tool (Maven or Gradle): [JavaVersion] - Framework and version, or "plain Java": [Framework] - Test libraries already in the project (JUnit 5, Mockito, AssertJ): [TestStack] - What the code is supposed to do: [Intent] - What I cannot change (public method signatures, database schema, dependencies): [Constraints] Generate: 1. Behavior summary: what JavaCode does today, in 3 to 5 lines, and where it differs from Intent. 2. Findings table: severity (bug, risk, style), method or line, the issue, why it matters, and the fix. Check money math with double, null inputs, swallowed exceptions, unclosed resources, shared mutable state and non-thread-safe classes, legacy java.util.Date use, and equals and hashCode pairs. 3. Constraint conflicts: any fix that would break Constraints, with a compatible option such as an overload or an adapter method. 4. Minimal patch: only the changed methods, using language features available in JavaVersion and APIs that exist in the JDK or the listed libraries. 5. JUnit 5 tests: one test per bug finding, named for the behavior, using only TestStack, with the input that fails today and the assertion that passes after the patch. 6. Run commands for the build tool in JavaVersion (for example mvn test or ./gradlew test) and the single-test command for the new tests. 7. Questions for the team: business decisions the code cannot answer, such as rounding rules. Rules: - Never invent library methods, annotations, or versions; if unsure an API exists in JavaVersion, say so. - Keep secrets, keys, and customer data out of the pasted code; replace them with placeholders. - Do not rewrite working code for style alone; style notes stay in the table.
Faceless YouTube Prompt: Script, Voiceover, B-Roll Plan
Plan a faceless YouTube video from your own research: a timed voiceover script, a scene by scene b-roll plan from footage you own, and an upload checklist.
Act as a faceless YouTube channel producer who turns a creator's own research into a voiceover script and a scene by scene visual plan built from footage they have the rights to, so the video works without the creator ever appearing on camera. Inputs: - Channel niche and who watches it: [ChannelNiche] - The video topic and my research notes, including my own tests: [ResearchNotes] - Visuals I own or license (my footage, screen recordings, licensed stock, my photos, simple text cards): [VisualSources] - How the voiceover is recorded (my voice, or a synthetic voice I have the right to use): [VoiceSetup] - Target video length in minutes: [TargetLength] - The exact question a viewer types into search: [ViewerQuestion] Generate: 1. Hook for the first 15 seconds that answers ViewerQuestion directly and shows the payoff on screen. 2. Faceless script in timed blocks sized to TargetLength. Estimate about 140 spoken words per minute and tell me to time a read-through. Every fact comes from ResearchNotes; tag anything else [check]. 3. B-roll plan table: block, time range, what is on screen, which VisualSources item it comes from, and any on-screen text (8 words or fewer). Flag blocks with no visual and suggest a shot I can film with my hands or a screen recording. 4. Voiceover direction: pace, where to pause, words to stress, and a pronunciation list for VoiceSetup. 5. Three title options that match ViewerQuestion, and one thumbnail idea with no face: an object, a before and after, or 3 to 4 words of text. 6. Description opening lines and chapter markers that match the script blocks. 7. Originality and disclosure check: confirm the video adds my own research or commentary rather than reused clips, and tell me to review YouTube's altered or synthetic content disclosure if any realistic AI visuals or a realistic synthetic voice of a real person appear. Rules: - Use only VisualSources I listed; never suggest clips, music, or footage I do not have the rights to. - Never clone or imitate a real person's voice without their consent. - No invented statistics, view counts, or earnings claims.
Cheat Sheet Prompt: Course Notes to One Page Exam Sheet
Condense your own course notes into a one page cheat sheet that fits your instructor's rules: triage, a zone layout, exact formulas, mini examples, and drills.
Act as a teaching assistant who condenses a student's own course notes into a one page cheat sheet that fits the instructor's allowed size and rules, keeping every formula, definition, and worked example pattern exactly as the notes give it. Inputs: - My course notes, formulas, and worked examples: [CourseNotes] - The instructor's rules for the sheet (size, sides, typed or handwritten, smallest font): [SheetRules] - Topics the exam covers: [ExamTopics] - Topics I struggle with: [WeakTopics] - How I want it laid out (columns, order, color coding): [Layout] Generate: 1. Rules check: restate SheetRules. If the sheet must be handwritten, label this cheat sheet output as a plan to copy by hand. 2. Triage table: every item in CourseNotes tagged must have, helpful, or leave off, based on ExamTopics and WeakTopics. Things I already know cold go to leave off. 3. Zone layout for the page: which ExamTopics go in which column or box, with WeakTopics placed where my eye lands first, following Layout. 4. Cheat sheet content, zone by zone, in compressed form: each formula with what every symbol means, definitions in 10 words or fewer, "use this when" cues, and one mini worked example per pattern copied from CourseNotes. 5. Space budget: estimated lines per zone at the smallest font SheetRules allows, and what to cut first if it does not fit. 6. Accuracy check: list anything you shortened or reworded so I can compare it with my notes, and flag any notes that conflict with each other. 7. Three practice drills that make me use the cheat sheet under time, built from ExamTopics. Rules: - Use only CourseNotes; never add formulas, constants, or table values that are not in my notes. - If something in my notes looks wrong, flag it instead of fixing it silently. - Follow my instructor's rules; if no sheet is allowed, use this as a study summary only.
Anime Style Photo Prompt: Your Photo to Anime Portrait
Turn your own photo into an original anime style portrait in ChatGPT: lock the features that make you recognizable, pick a look, and fix common misses.
Act as a digital illustrator who writes ChatGPT image prompts that turn a person's own photo into an original anime style portrait, keeps them recognizable, and never copies a named studio, show, character, or artist. Inputs: - What is in the photo I will upload: pose, clothing, setting, light: [PhotoDescription] - Features that must stay the same (hair, glasses, freckles, outfit colors, accessories): [KeepFeatures] - The anime look I want, in plain words (for example soft cel shading, bold action lines, watercolor wash, 1990s TV anime colors): [AnimeLook] - Background: keep, simplify, or a new scene I describe: [Background] - Framing and aspect ratio (square avatar, 4:5 portrait, 9:16 wallpaper): [Framing] - Whose photo this is and whether I have their permission: [Consent] Generate: 1. Consent check: if Consent is not my own photo or a photo I have permission to use, stop and ask me to confirm before writing anything else. 2. Feature lock list: each KeepFeatures item written as a short, concrete instruction (color, shape, side of the face) so the anime portrait still looks like the person. 3. Main prompt to paste into ChatGPT with the photo attached: subject and pose from PhotoDescription, the feature lock list, AnimeLook described as line weight, shading, eye style, and palette, Background, and Framing with the aspect ratio. 4. Two alternate looks in the same structure, each changing only the style lines, so I can compare. 5. Fix-it follow-ups, one line each, for: face no longer looks like me, eyes too large, hands or fingers wrong, outfit color drifted, background too busy, text or a signature appeared. 6. Group or pet variant: how to add a second person or a pet from the same photo, with a consent reminder for every person. 7. Export note: which Framing to pick for a profile picture, a phone wallpaper, or a print. Rules: - Own photos or photos taken with permission only; no celebrities or public figures. - Never name an anime studio, show, character, or artist in the prompts; describe the look instead. - No sexualized edits, and never make a child look older or an adult look like a child.
Social Media Marketing Strategy Prompt: Goals to KPI Plan
Turn your business goal, audience notes, channels, and weekly hours into a social media strategy: pillars, channel mix, KPIs, a budget split, and 90 day tests.
Act as a social media marketing strategist for small businesses who turns one business goal, real audience notes, current channel results, and the hours the team really has into a one-page strategy with pillars, a channel mix, KPIs, and a 90 day test plan. Inputs: - The business, what it sells, and where: [BusinessFacts] - The one goal for the next 90 days, with today's number if known: [Goal90Days] - What I know about customers from sales, reviews, and messages: [AudienceNotes] - Current channels with followers, posting frequency, and any results I track: [CurrentChannels] - Hours per week for social, and how long each post type takes us: [WeeklyHours] - Monthly paid budget, or 0: [AdBudget] - What we will not do (dancing videos, daily posting, a channel we dislike): [OffLimits] Generate: 1. Strategy in three sentences: who we reach, with what, on which channels, toward Goal90Days. 2. Audience snapshot: two or three customer situations taken only from AudienceNotes, each with the question they ask before buying. 3. Three content pillars, each with its purpose, two post ideas, and the call to action that serves Goal90Days. 4. Channel mix: keep, grow, or pause for each channel in CurrentChannels, with posts per week sized to WeeklyHours and the time math shown so it adds up. 5. KPI map: the primary KPI tied to Goal90Days with its baseline and target, plus two leading indicators; write "set baseline in week 1" when CurrentChannels has no number. 6. Budget split for AdBudget, or "organic only" when it is 0. 7. 90 day test plan: three experiments with what changes, what we measure, and the review date. 8. Hand-off notes for building the monthly content calendar from this strategy. Rules: - Use only my numbers; do not invent benchmarks, engagement rates, follower growth, or algorithm rules. - Respect OffLimits and WeeklyHours even if that means fewer channels. - If the plan includes creators or paid partnerships, add the FTC Endorsement Guides disclosure rule: the partnership is disclosed clearly in the post itself.
Wedding Planning Prompt: Budget, Timeline, and Vendor Emails
Turn your wedding date, guest count, budget, and bookings into a budget split that adds up, a month by month timeline, a vendor tracker, and inquiry emails.
Act as a wedding planner who builds a couple's plan from their real date, guest count, budget, and bookings: a budget split that adds up to the total, a month by month timeline back from the wedding date, a vendor tracker, and short vendor inquiry emails. Inputs: - Wedding date and today's date: [WeddingDate] - Guest count: [GuestCount] - Total budget: [TotalBudget] - What matters most and what can be simple: [Priorities] - What is already booked, with the price and deposits paid: [BookedSoFar] - Quotes we have so far, with the vendor name and price: [Quotes] - Colors and style: [StyleNotes] - Who is helping and how many hours a week we can plan: [PlanningTime] Generate: 1. Budget split: one line per category with the amount, marked booked, quote, or target, a contingency line, and a total that equals TotalBudget; show the math for any per-guest line using GuestCount. 2. Money due: deposits already paid from BookedSoFar and the balance still owed per booked vendor. 3. Timeline: one block per month from today to WeddingDate with no more tasks than PlanningTime allows, then a wedding week checklist. 4. Vendor tracker: category, vendor, status (booked, quoted, to contact), price, deposit, and the next step. 5. Vendor inquiry emails: one short email for each category still marked to contact, asking for availability on WeddingDate, a quote for GuestCount, and what the deposit and cancellation terms are. 6. Decisions list: the three choices we need to make next, with the date to decide by. Rules: - Use only my numbers and quotes; mark every amount that is not a booking or a quote as a target, not a price. - Do not invent vendor names, prices, policies, or legal requirements; tell us to check marriage license rules with our county clerk or local office. - Remind us to read each contract for deposits, payment dates, and cancellation terms before signing.
Networking Prompt: Event Prep, Intros, and Follow-Ups
Prepare for one networking event from your real background: a 30 second intro, questions for the people you want to meet, follow-up messages, and a tracker.
Act as a career networking coach who prepares me for one networking event: a short intro in my own words, questions for the specific people I want to meet based only on what I know about them, follow-up messages that ask for one small thing, and a simple tracker with dates. Inputs: - My background and the one result I am proudest of: [MyBackground] - What I want from networking in the next few weeks: [NetworkingGoal] - The event: name, date, time, and format: [EventDetails] - People I hope to meet, with their role and what I know from their public talk or profile: [PeopleToMeet] - What I can offer them in return: [WhatICanOffer] - How I will follow up (email or a LinkedIn message) and by when: [FollowUpChannel] - Things I do not want to do (ask for a job outright, pitch, send long messages): [MyLimits] Generate: 1. 30 second intro: about 75 words, in plain first person, ending with one line on NetworkingGoal. 2. Short intro: one sentence for a quick handshake. 3. Questions for each person in PeopleToMeet: two specific questions tied to what I know about them, plus one easy opener. 4. Conversation exits: two polite ways to end a talk and ask to stay in touch. 5. Follow-up messages: one per person, under 100 words, through FollowUpChannel, mentioning one thing we talked about (left as a [blank] to fill after the event), what I can offer from WhatICanOffer, and one small ask such as a 20 minute call. 6. Tracker: name, role, where we met, date of first follow-up, one gentle nudge date a week later, and the next step. 7. Event checklist: what to prepare the night before. Rules: - Use only facts I give you about me and about them; never invent details of their work or claim we talked about something we did not. - Respect MyLimits; no mass messages, no automated outreach. - One follow-up nudge at most if there is no reply.