Chrome Extension
When I first set up my Dot, Jamie, the hardest part wasn't the setup. It was deciding what job to hand it.
So I wrote down 72 workflows I'd try, each with a starter prompt you can copy, fill in and paste. They're grouped by marketing, SEO, sales, admin, meetings, research, coding, data, documents, travel and home.
If you're new to Dots, read my OpenAI Dots guide first. It covers setup, plans, and my real outreach case where Jamie got our first backlink.
Before you paste a prompt
These are workflows I would try with a dot, followed by prompts you can adapt. They are proposed uses based on documented research, document preparation, connected-tool work, computer use, delegation and recurring tasks. I have not tested all 72, and this list does not describe work Jamie has already completed.
Connected work requires access to the relevant sources and permission to use them.
A named app, folder or website in a prompt is an input you provide, rather than a promise that a particular integration is available. If access is missing, ask the dot to explain the gap and work from files you provide.
Replace the bracketed inputs before pasting a prompt. Start with one small batch and inspect the result. For recurring work, include your time zone and an end date, ask the dot to confirm the saved instruction, and inspect Scheduled.
I wrote these examples to keep messages, purchases and changes to live systems for your review.
Marketing and content
1. Turn one interview into a content pack
I would give my dot one transcript so I can review a coordinated set of content instead of starting each draft separately.
Use [TRANSCRIPT FILE], [THREE WRITING SAMPLES] and [AUDIENCE BRIEF] to prepare one content pack: show notes, a newsletter section and five social drafts. Preserve the speaker's meaning and attach timestamps to proposed clip moments. Flag unsupported claims. Save editable drafts in [APPROVED FOLDER] with a source checklist. Finish when every draft is ready for my review. Do not publish or message anyone.
2. Build a useful interview brief
I would use a dot to find the questions my audience needs answered before I record an interview.
Research [GUEST] using [APPROVED PUBLIC SOURCES] and the background files in [FOLDER]. Prepare a two-page interview brief for [AUDIENCE], with ten questions, three follow-up angles and links supporting the factual introductions. Avoid private or speculative personal details. Save the brief in [DESTINATION]. Finish with the five questions I should prioritize in a [DURATION]-minute interview. Do not contact the guest.
3. Draft a focused newsletter issue
I would ask for one issue built around a clear reader problem, with evidence I can check.
Use [TOPIC], [AUDIENCE], [NEWSLETTER SAMPLES] and [APPROVED SOURCES] to draft one newsletter issue. Include a useful opening, three practical lessons, one example and a relevant next step. Link facts to their sources and label my opinions separately. Save the draft in [DESTINATION] with three subject-line options. Finish with a short editorial checklist. Do not send the newsletter or add subscribers.
4. Create a working voice guide
I would turn my own edits into a short guide that helps the dot produce more consistent drafts.
Read [FIVE APPROVED ARTICLES] and [BEFORE AND AFTER EDITS]. Identify my sentence style, preferred examples, claims I avoid and phrases I remove. Create a two-page voice guide with positive examples and a short review checklist. Save it in [DESTINATION], then apply it to one [SAMPLE DRAFT] for comparison. Mark uncertain preferences for my decision. Do not change published content.
5. Plan a campaign around real capacity
I would use a dot to connect campaign goals with the time, people and assets I actually have.
Use [CAMPAIGN BRIEF], [ASSET INVENTORY], [TEAM CAPACITY] and [DATES] to propose a four-week campaign calendar. Give every item an audience, purpose, owner, required input and review date. Include only channels listed in the brief. Save the calendar and missing-assets list in [DESTINATION]. Finish by identifying the three decisions blocking launch. Do not schedule posts or assign work to other people.
6. Prepare a customer email sequence
I would ask for an email sequence that reflects the product's real behavior and gives me clear review points.
Use [PRODUCT DOCUMENTATION], [CUSTOMER SEGMENT] and [APPROVED EMAIL EXAMPLES] to draft a three-message [ONBOARDING OR RETENTION] sequence. Explain the purpose and trigger of each message. Check claims against current product documentation and flag missing details. Save subject lines, bodies and a review checklist in [DESTINATION]. Finish when all three drafts are complete. Do not configure automation, send messages or modify customer records.
SEO, AI search and digital PR
7. Find gaps in a defined content set
I would compare a small set of my pages with the questions I want to answer for readers.
Compare [TEN SITE URLS OR PAGE EXPORTS] with [AUDIENCE QUESTIONS] and [THREE APPROVED COMPETITOR PAGES]. Build a content-gap table covering missing questions, weak explanations and duplicate coverage. Link evidence and separate observations from hypotheses about search performance. Save five prioritized briefs in [DESTINATION]. Finish with one recommended first article. Do not edit pages or promise ranking improvements.
8. Refresh an article's facts
I would have the dot check an aging article before I update it in my publishing system.
Check [ARTICLE URL OR FILE] against current primary sources for [TOPIC]. Create a table of outdated facts, dead source links and unsupported statements, with replacement wording and dated citations. Then produce a revised draft that keeps my voice and useful examples. Save both files in [DESTINATION]. Finish with a list of claims needing my judgment. Do not publish changes or invent statistics.
9. Review page basics from supplied material
I would use a dot to catch obvious page problems without pretending that a quick review is a full technical audit.
Review [FIVE PAGE URLS OR HTML EXPORTS] for title clarity, descriptions, heading order, visible broken links and inconsistent product facts. Record what you can directly inspect and what requires site logs or crawling tools. Save a prioritized issue table with proposed fixes in [DESTINATION]. Finish after those five pages. Do not change the website, run an unrestricted crawl or claim complete technical SEO coverage.
10. Propose useful internal links
I would ask the dot to find links that help a reader take the next sensible step.
Use [SITE CONTENT INVENTORY] and [ARTICLE DRAFT] to suggest up to ten internal links. For each, explain the reader benefit, propose natural anchor text and identify the exact paragraph where it fits. Exclude irrelevant pages and verify destinations where access permits. Save an annotated draft in [DESTINATION]. Finish with a short link map. Do not insert links into the live website.
11. Check coverage of buyer questions
I would review whether my content answers real questions clearly before discussing visibility in AI search.
Use [TEN VERIFIED BUYER QUESTIONS], [PRODUCT DOCUMENTATION] and [CURRENT PAGE EXPORTS] to audit answer coverage. Mark each question as answered, incomplete or absent. Draft concise answers with supporting links and clear limits. Save a coverage table and proposed page updates in [DESTINATION]. Finish with the five most useful additions. Do not claim AI-search rankings or cite visibility data I have not supplied.
12. Prepare a digital PR evidence pack
I would ask a dot to organize my evidence before I approach a journalist or publisher.
Use [ORIGINAL DATASET], [METHODOLOGY NOTES] and [APPROVED BRAND FACTS] to prepare a digital PR brief on [ANGLE]. Include three defensible findings, calculation notes, limitations and a chart outline. Research five relevant public publication pages and explain the fit. Save the brief and draft pitch in [DESTINATION]. Finish with a claim-check table. Do not contact publications or manufacture newsworthiness, quotes or results.
Sales research and customer-support preparation
13. Research a small prospect shortlist
I would start outreach with a few qualified companies and evidence I can inspect.
Research up to ten companies from [APPROVED LIST] using their public websites and [APPROVED SOURCES]. Apply [QUALIFICATION CRITERIA] and exclude [SUPPRESSION LIST]. Return a table with fit, relevant evidence, source dates and unknowns. Save it in [DESTINATION]. Finish when each company has a justified include or exclude decision. Do not guess contact details, send outreach or update the CRM.
14. Draft evidence-based prospect messages
I would use a dot to prepare messages that connect a real prospect need with an offer I can substantiate.
Use [APPROVED PROSPECT TABLE], [OFFER FACTS] and [THREE MESSAGE SAMPLES] to draft five outreach emails. Give each one a source-backed relevance statement, a clear reason to talk and a low-pressure next step. Show the evidence beside the draft. Save the review queue in [DESTINATION]. Finish with checks for accuracy, duplicates and suppression rules. Do not send messages or invent personalization.
15. Create a meeting-ready account brief
I would let the dot summarize the account history so I can focus on the conversation.
Use the authorized account records in [SOURCE], [RECENT EMAIL THREADS] and [COMPANY WEBSITE] to prepare a one-page brief for my meeting with [ACCOUNT] on [DATE]. Cover stated priorities, previous commitments, unresolved questions and three useful discussion points. Link evidence and label assumptions. Save it in [DESTINATION]. Finish with a suggested agenda. Do not contact the account or change records.
16. Triage replies for my decision
I would ask my dot to organize a small reply batch and draft responses I can approve.
Read up to [NUMBER] replies in [AUTHORIZED INBOX OR EXPORT] from [DATE RANGE]. Classify interest, questions, objections, opt-outs and unrelated messages using [RULES]. Draft a suitable response only where appropriate, and flag opt-outs for my review without sending another sales message. Save a decision queue in [DESTINATION]. Finish with urgent items first. Do not send replies or alter account records.
17. Build a proposal evidence matrix
I would use a dot to find where my proposal needs proof before I make a commitment.
Compare [CUSTOMER REQUIREMENTS] with [CURRENT PRODUCT DOCUMENTATION], [APPROVED CASE STUDIES] and [TEST RESULTS]. Create a requirement-by-requirement matrix showing supported, partly supported and unverified items. Draft the proposal sections we can substantiate and list questions for [OWNER]. Save everything in [DESTINATION]. Finish with unresolved commitments highlighted. Do not promise untested capabilities, change prices or send the proposal.
18. Prepare support answers from approved knowledge
I would have the dot turn recurring support questions into draft answers for my team to review.
Review [TWENTY ANONYMIZED SUPPORT TICKETS] and [APPROVED HELP ARTICLES]. Group repeated problems, identify missing guidance and draft five reply templates with source links. Flag issues requiring account-specific investigation or a person with product authority. Save the templates and documentation gaps in [DESTINATION]. Finish with a priority order based on the supplied tickets. Do not reply to customers or change their accounts.
Business and personal administration
19. Prepare a missing invoice
I would ask the dot to assemble an invoice draft from records I already trust.
Compare [COMPLETED WORK RECORD] with [INVOICE REGISTER] and the authorized email thread for [CLIENT]. If an invoice is missing, prepare a draft using [APPROVED TEMPLATE] and show the source for every amount and billing detail. Save the draft in [DESTINATION]. Finish with questions about any discrepancy. Do not guess charges, send the invoice, take payment or change accounting records.
20. Organize one batch of receipts
I would use a dot to reduce receipt sorting before I review the numbers myself.
Read the receipt files in [FOLDER] for [MONTH]. Create a table with date, merchant, amount, currency, source filename and the categories in [APPROVED CATEGORY LIST]. Flag unreadable fields, duplicate receipts and possible mismatches. Save the table and exception list in [DESTINATION]. Finish when every supplied receipt is accounted for. Do not infer tax treatment, submit expenses or modify financial systems.
21. Review recurring subscriptions
I would let the dot show me recurring charges and the evidence behind possible cancellations.
Use [SUBSCRIPTION REGISTER], [BILLING EXPORT] and authorized renewal emails for [DATE RANGE]. List recurring services, renewal dates, known usage and discrepancies. Identify subscriptions I may want to review, without treating missing usage data as proof they are unnecessary. Save a decision table in [DESTINATION]. Finish with the next three renewal deadlines. Do not cancel services, contact vendors or access payment credentials.
22. Draft overdue-invoice reminders
I would prepare a clear review queue before following up on unpaid invoices.
Use [INVOICE REGISTER], [PAYMENT STATUS EXPORT] and [APPROVED FOLLOW-UP POLICY] to identify overdue invoices as of [DATE]. Verify that payments and previous replies do not contradict the status. Draft one reminder per eligible invoice and include the evidence beside it. Save the queue in [DESTINATION]. Finish with disputed or uncertain items separated. Do not send reminders, add fees or edit the ledger.
23. Prepare a vendor renewal decision
I would compare the renewal notice with the work I need the vendor to support.
Use [VENDOR AGREEMENT], [RENEWAL NOTICE], [USAGE SUMMARY] and [BUSINESS REQUIREMENTS] to prepare a renewal brief. Compare documented price changes, relevant features and unresolved questions. Draft a list of questions for the vendor, with source references. Save the brief in [DESTINATION]. Finish with options I can review. Do not interpret legal enforceability, negotiate, accept terms or renew the service.
24. Sort a weekly admin backlog
I would ask my dot to turn a messy admin list into a realistic set of next actions.
Use [ADMIN TASK LIST], [AUTHORIZED EMAIL FOLDER] and [MY AVAILABLE HOURS] to prepare this week's admin plan. Separate tasks I can complete quickly, tasks needing a decision and tasks missing information. Give each item a source, deadline and proposed next action. Save the plan in [DESTINATION]. Finish with a manageable top five. Do not send messages, move appointments or change external records.
Meetings and project coordination
25. Prepare an agenda from the actual work
I would build a meeting around decisions rather than a generic status list.
Use [PROJECT NOTES], [LAST MEETING SUMMARY] and [OPEN ISSUE LIST] to draft an agenda for [MEETING] lasting [DURATION]. Prioritize decisions, include required background and suggest a time allocation. State what I should prepare before the meeting. Save the agenda in [DESTINATION]. Finish with the three most important decisions. Do not send invitations, contact attendees or change anyone's calendar.
26. Extract decisions and action items
I would let a dot turn a meeting transcript into a record I can correct and share.
Read [MEETING TRANSCRIPT] and extract explicit decisions, action items, owners and stated deadlines. Separate confirmed commitments from proposals and unresolved discussion. Attach timestamps where available and do not infer owners. Save a decision log and draft recap in [DESTINATION]. Finish with a list of ambiguities for my review. Do not distribute the recap or create tasks in other people's systems.
27. Map launch dependencies
I would use a dot to find the dependencies that could make my launch plan slip.
Use [LAUNCH PLAN], [DELIVERABLE LIST] and [TEAM CAPACITY] to map dependencies for [LAUNCH DATE]. Identify the sequence, missing inputs and tasks with no assigned owner. Build a table with evidence, consequence and a suggested next decision for each risk. Save it in [DESTINATION]. Finish with the critical path based on supplied dates. Do not assign work, change deadlines or notify stakeholders.
28. Prepare a weekly project update
I would ask for a short update that helps people understand progress and the decisions I need to make.
Read authorized updates from [PROJECT SOURCE] covering [DATE RANGE]. Prepare a weekly summary with completed work, current blockers, changed dates and decisions needed from me. Link each material statement to its source and flag contradictory updates. Save a shareable draft in [DESTINATION]. Finish with a three-item action list. Do not post the update, message teammates or change the project board.
29. Assess a proposed scope change
I would ask the dot to make the effect of a scope change concrete before I approve it.
Compare [CURRENT PROJECT SCOPE] with [PROPOSED CHANGE]. Use [DEPENDENCIES], [CAPACITY] and [ACCEPTANCE CRITERIA] to show affected deliverables, assumptions and information we need before estimating effort. Prepare three options with clear tradeoffs, then save a decision brief in [DESTINATION]. Finish with the questions I must resolve. Do not approve the change, promise dates or modify the official plan.
30. Build a stakeholder review pack
I would give reviewers the material they need to make a specific decision.
Use [PROJECT BRIEF], [CURRENT DRAFTS] and [REVIEW REQUIREMENTS] to assemble a review pack for [DECISION]. Include a one-page overview, links to the relevant drafts, the alternatives and a short list of questions for reviewers. Identify missing evidence. Save the pack in [DESTINATION]. Finish when every review question points to supporting material. Do not share files or request approval from other people.
Research and learning
31. Create a source-checked research brief
I would use a dot to collect evidence around one question before I form an opinion.
Research [QUESTION] using [APPROVED PRIMARY SOURCES] within [DATE RANGE]. Prepare a brief with five evidence-backed findings, disagreements, source dates and unanswered questions. Separate documented facts from your interpretation. Save the brief and a source table in [DESTINATION]. Finish when each factual claim has a link. Do not fill evidence gaps with guesses or present a conclusion stronger than the sources support.
32. Critique a research paper
I would ask a dot to help me understand a paper's claim, method and limits.
Read [PAPER FILE OR URL] and [SUPPLEMENTARY MATERIAL]. Explain the research question, method, main results and limitations for [MY EXPERIENCE LEVEL]. Check whether the conclusions follow from the presented evidence. Save a two-page critique with page references and five questions for further reading in [DESTINATION]. Finish with a plain-language explanation I can repeat accurately. Do not invent experiments or cite papers you have not read.
33. Watch a small research topic
I would ask the dot to alert me when a new source changes what I need to know.
Every [DAY] at [TIME] [TIME ZONE] until [END DATE], check [THREE APPROVED RESEARCH SOURCES] for new work on [QUESTION]. Save a dated digest in [DESTINATION]. Notify me only about a relevant new paper, correction or material change in evidence. Label preprints and uncertainty. Confirm the saved schedule and accessible sources. Do not subscribe me to services or contact authors.
34. Build a study plan around my time
I would use a dot to turn a learning goal into sessions I can complete.
Use [LEARNING GOAL], [CURRENT KNOWLEDGE], [APPROVED MATERIALS] and [HOURS PER WEEK] to create a four-week study plan. Give each session a resource, practice task and completion check. Keep the plan within my available time. Save it in [DESTINATION]. Finish with a ten-minute first task I can start today. Do not enroll me in courses, buy materials or change my calendar.
35. Practice from material I provide
I would ask the dot to help me test my understanding and focus on my weak spots.
Use [NOTES OR COURSE MATERIAL] to create ten practice questions at [LEVEL]. Ask me one question at a time, wait for my answer and explain the reasoning with references to the material. Record concepts I need to revisit. Finish with a short study checklist saved in [DESTINATION]. Do not claim these are official exam questions or introduce facts that contradict the supplied source.
36. Compare options against explicit needs
I would research a purchase decision using criteria that matter to me rather than a generic ranking.
Compare [THREE PRODUCTS OR SERVICES] for [MY REQUIREMENTS] using current official pages and [APPROVED INDEPENDENT SOURCES]. Check prices, restrictions and the features relevant to my use. Save a dated comparison table with unknowns in [DESTINATION]. Finish with a recommendation tied to my stated criteria and one low-cost way to test it. Do not purchase, start trials or contact sellers.
Coding, product design and quality checks
37. Investigate one reproducible bug
I would give the dot a specific bug and ask it to show me what actually fails.
Use [REPOSITORY OR APPROVED CLOUD ENVIRONMENT], [BUG REPORT] and [REPRODUCTION STEPS] to investigate one issue. Follow the project's instructions and available test setup. Record the failing behavior, likely cause and evidence. Save a reproduction note and proposed fix in [DESTINATION]. Finish with a clear pass or fail result for the reproduction. Do not deploy changes or modify production data.
38. Prepare a small tested patch
I would ask my dot to complete a bounded code change that I can review before merging.
In [AUTHORIZED REPOSITORY], implement [SMALL CHANGE] using [ACCEPTANCE CRITERIA]. Follow the repository instructions, inspect related code and run relevant checks available in the environment. Save the patch and draft review description in [DESTINATION]. Finish with changed behavior, verification results and unresolved limitations. Ask me if the change requires broader scope. Do not merge, deploy or open an external pull request.
39. Check a screen for accessibility issues
I would review one interface before I repeat the same pattern across my product.
Inspect [SCREEN URL, DESIGN OR LOCAL APP] using the access I have granted. Review visible labels, keyboard behavior where testable, focus order and contrast evidence. Save an issue table with affected elements, reproduction steps and proposed fixes in [DESTINATION]. Finish with the five highest-priority findings. Distinguish observed issues from checks you could not perform. Do not claim complete accessibility certification or change the live app.
40. Prototype one product flow
I would use a dot to make a small idea concrete enough for people to react to.
Use [PRODUCT BRIEF], [USER NEED] and [DESIGN REFERENCES] to prototype one flow for [TASK] in [AUTHORIZED WORKSPACE]. Include the main screen, empty state and one error state. Save an editable prototype, screenshots where supported and notes in [DESTINATION]. Finish with a walkthrough and three questions for user feedback. Use sample data. Do not publish the prototype or collect real customer information.
41. Check a defined regression path
I would ask my dot to verify the actions a change could affect, using a clear test environment.
Use [TEST BUILD], [CHANGE SUMMARY] and [FIVE TEST SCENARIOS] to check the affected product flow. Work only in [AUTHORIZED TEST ENVIRONMENT] with sample accounts. Record expected and observed results, evidence and any blocked step. Save a regression report in [DESTINATION]. Finish when all five scenarios have a pass, fail or blocked status. Do not test production accounts or alter real customer data.
42. Align documentation with a shipped feature
I would have a dot identify documentation that no longer matches the product.
Compare [VERIFIED FEATURE CHANGE], [CURRENT PRODUCT DOCUMENTATION] and [RELEASE NOTES]. Identify affected instructions, screenshots and examples. Draft the minimum documentation updates with a source reference for each behavior claim. Save the proposed edits in [DESTINATION]. Finish with an inconsistency checklist and questions about unverified behavior. Do not infer unavailable features, edit published documentation or announce the release.
Spreadsheets and data reporting
43. Inspect a dataset before analysis
I would check the data first so I do not build a convincing report around bad inputs.
Inspect [DATA FILE] for [BUSINESS QUESTION]. Check field definitions, missing values, duplicate records, date ranges and inconsistent units. Save a quality report and an exception table in [DESTINATION]. Propose fixes without overwriting the source. Finish by stating which analyses the data can support and which remain uncertain. Use only the supplied dataset and authorized reference files. Do not manufacture missing values.
44. Explain a small set of KPIs
I would ask the dot to connect the numbers with the decisions I need to make.
Use [DATA EXPORT], [METRIC DEFINITIONS] and [COMPARISON PERIOD] to prepare a report on [THREE KPIS]. Show calculations, changes and relevant breakdowns. Separate demonstrated findings from possible explanations. Save an editable report and calculation table in [DESTINATION]. Finish with three practical questions or actions for my review. Flag incomplete coverage. Do not claim causation or connect to analytics accounts I have not authorized.
45. Review budget variance
I would use a dot to show me where actual spending differs from the plan.
Compare [BUDGET FILE] with [ACTUAL SPENDING EXPORT] for [PERIOD]. Reconcile categories using [APPROVED MAPPING] and calculate absolute and percentage variances. Link each explanation to a transaction or note, and leave unexplained differences open. Save a variance table and short review memo in [DESTINATION]. Finish with the largest items needing my decision. Do not change accounting entries or provide tax advice.
46. Build a simple scenario model
I would ask the dot to show how a decision changes when my assumptions change.
Use [CURRENT MODEL] and [EXPLICIT ASSUMPTIONS] to create three scenarios for [BUSINESS DECISION]. Keep formulas visible and separate inputs from calculated outputs. Include a sensitivity table for [TWO VARIABLES] and explain limitations. Save an editable spreadsheet in [DESTINATION]. Finish by identifying the assumption with the greatest effect. Do not present forecasts as guarantees or invent inputs I have not supplied.
47. Compare customer cohorts
I would use a dot to find differences between groups while keeping the definitions clear.
Use [ANONYMIZED CUSTOMER DATA] and [COHORT DEFINITION] to compare [OUTCOME] across [PERIOD]. Check whether records support the comparison, then calculate group sizes, missingness and the stated metrics. Save a reproducible calculation table and chart in [DESTINATION]. Finish with observations, plausible explanations and data gaps. Do not infer individual identities, claim causal effects or combine datasets without my authorization.
48. Summarize a survey with traceable evidence
I would ask the dot to show both the numbers and the comments behind the main themes.
Use [ANONYMIZED SURVEY EXPORT], [QUESTION DEFINITIONS] and [RESEARCH GOAL] to summarize responses. Count repeated themes with a stated coding method, separate response counts from percentages and show short anonymized examples. Save a findings table and limitations note in [DESTINATION]. Finish with three follow-up questions. Do not treat a small or self-selected sample as representative of all customers.
Documents and knowledge organization
49. Build an index I can actually use
I would ask a dot to show what is in a folder before I reorganize it.
Read the authorized files in [FOLDER] and create an index with title, subject, date, owner if stated and a short description. Flag duplicates, outdated versions and files you cannot read. Suggest a folder structure without moving the originals. Save the index in [DESTINATION]. Finish when every supplied file is listed or marked inaccessible. Do not change permissions, delete files or share their contents.
50. Draft a procedure from real examples
I would turn a repeated task into instructions that another person can follow.
Use [PROCESS NOTES], [THREE COMPLETED EXAMPLES] and [EXISTING RULES] to draft a procedure for [TASK]. Include required inputs, steps, decision points, exceptions and a completion checklist. Mark missing information instead of inventing policy. Save an editable document in [DESTINATION]. Finish with a walkthrough against one example and a list of corrections needed. Do not modify company policy or publish the procedure.
51. Prepare an internal FAQ from policy documents
I would make existing rules easier to find without giving the dot authority to create new ones.
Use [APPROVED INTERNAL POLICY DOCUMENTS] and [REPEATED EMPLOYEE QUESTIONS] to draft an internal FAQ. Answer only what the documents support, cite the relevant section and flag conflicting versions. Save the FAQ and unresolved questions in [DESTINATION]. Finish with a list for [POLICY OWNER] to review. Do not interpret legal obligations, create exceptions, change policy or send answers to employees.
52. Create an onboarding reading path
I would help a new teammate understand the job without dropping a pile of documents on them.
Use [ROLE DESCRIPTION], [APPROVED DOCUMENTS] and [FIRST-WEEK GOALS] to create a five-day onboarding reading path. Give each day a purpose, a small set of resources and one practice task. Identify missing access or instructions. Save the plan in [DESTINATION]. Finish with a manager review checklist. Do not invite users, grant access or assign tasks to the new teammate.
53. Plan a document migration
I would use a dot to plan where files belong before making changes that affect other people.
Use [CURRENT DOCUMENT INVENTORY], [TARGET STRUCTURE] and [RETENTION RULES PROVIDED BY ME] to draft a migration plan. Map each file to a proposed destination and flag broken references, duplicates and permission questions. Save the mapping and a small pilot checklist in [DESTINATION]. Finish with the files suitable for a first test. Do not move, delete or change access to any original file.
54. Preserve the reasoning behind a decision
I would ask my dot to record why I chose an option so I can revisit it later.
Use [DECISION NOTES], [OPTIONS CONSIDERED] and [SUPPORTING EVIDENCE] to draft a decision record for [TOPIC]. State the decision, constraints, alternatives, tradeoffs and conditions that would justify reviewing it. Link each factual basis and mark unresolved assumptions. Save the record in [DESTINATION]. Finish with a concise version I can approve. Do not invent consensus or replace the official decision log.
Travel and event planning
55. Draft a trip itinerary with current sources
I would plan a trip around my actual dates, budget and preferences, then make the bookings myself.
Use [DATES], [DESTINATION], [BUDGET], [PREFERENCES] and current official travel or venue pages to draft a [NUMBER]-day itinerary. Show travel time assumptions, opening hours and source dates. Include alternatives for weather or closures. Save the plan in [DESTINATION]. Finish with a booking checklist and facts to recheck before departure. Do not book, pay, submit passport details or promise live availability.
56. Compare venues for one event
I would ask a dot to narrow the venue search before I make enquiries.
Research up to five venues from [APPROVED LIST] for [EVENT DATE], [GUEST COUNT] and [BUDGET]. Use public venue pages and [MY REQUIREMENTS]. Compare stated capacity, location, facilities and published prices, marking availability or fees that need confirmation. Save a shortlist and draft enquiry questions in [DESTINATION]. Finish with two best-fit options. Do not contact venues, reserve space or negotiate terms.
57. Build an event running order
I would use a dot to turn the event plan into a schedule my team can review.
Use [EVENT BRIEF], [CONFIRMED SESSIONS], [VENUE CONSTRAINTS] and [STAFF ROLES] to draft the running order for [DATE]. Include setup, transitions, breaks, ownership and a fallback for delayed sessions. Save an editable schedule and missing-details list in [DESTINATION]. Finish with checks for timing conflicts. Do not send instructions to staff, change bookings or treat unconfirmed sessions as agreed.
58. Prepare a speaker briefing pack
I would make the event's expectations clear before I send anything to a speaker.
Use [CONFIRMED SPEAKER INFORMATION], [SESSION GOAL], [AUDIENCE PROFILE] and [EVENT LOGISTICS] to draft a speaker brief. Include timing, format, audience context, slide requirements and questions we still need answered. Save the brief and an accompanying draft message in [DESTINATION]. Finish with a checklist against confirmed details. Do not email the speaker, reveal attendee information or invent commitments.
59. Check the paperwork for an upcoming trip
I would ask a dot to organize the documents I already have and flag missing information.
Use [ITINERARY], [BOOKING CONFIRMATIONS] and [CHECKLIST FROM OFFICIAL SOURCES] to prepare a trip document checklist. Match names, dates and destinations across the supplied documents, and flag mismatches or missing items. Save a private summary in [DESTINATION]. Finish with tasks I must confirm personally. Do not interpret immigration law, guarantee entry, submit applications or copy identity documents into a shareable report.
60. Plan event access and guest needs
I would check practical arrangements before guests arrive and discover a problem I could have caught.
Use [VENUE INFORMATION], [GUEST REQUIREMENTS THEY HAVE AGREED TO SHARE] and [EVENT PLAN] to draft an access checklist. Cover routes, seating, quiet space, communication and stated dietary requests. Identify details the venue must confirm. Save the checklist in [PRIVATE DESTINATION]. Finish with a draft question list for me. Do not contact guests, disclose private needs or make medical recommendations.
Household and everyday planning
61. Build a grocery list from what I have
I would start meal planning with my pantry instead of asking for another expensive shopping list.
Use [PANTRY INVENTORY], [HOUSEHOLD PREFERENCES], [BUDGET] and [MEALS NEEDED] to suggest five simple meals and a grocery list. Prioritize ingredients I already have and show quantities for [NUMBER] people. Respect restrictions I provide without offering medical guidance. Save the plan in [DESTINATION]. Finish with substitutions for missing ingredients. Do not order groceries, spend money or assume prices you cannot verify.
62. Organize routine home maintenance
I would give my dot the manuals and dates so I can keep track of routine upkeep.
Use [APPLIANCE MANUALS], [LAST SERVICE DATES] and [MY MAINTENANCE NOTES] to create a six-month maintenance checklist. Cite the manufacturer guidance for intervals and separate simple reminders from work needing a qualified professional. Save the checklist in [DESTINATION]. Finish with the tasks due this month. Do not provide hazardous repair instructions, book appointments or change connected-device settings.
63. Find a thoughtful gift shortlist
I would use a dot to compare a few ideas against what I know about the person.
Use [INTERESTS THE RECIPIENT HAS SHARED], [OCCASION], [BUDGET] and [DELIVERY REGION] to research five gift ideas from current public product pages. Explain the fit and check stated price, delivery information and return conditions. Save a dated shortlist in [DESTINATION]. Finish with one low-cost option and questions to confirm before ordering. Do not purchase, contact the recipient or use private information I have not supplied.
64. Plan a manageable house move
I would turn a move into a small set of weekly actions I can complete.
Use [MOVE DATE], [CURRENT INVENTORY], [DESTINATION DETAILS] and [AVAILABLE HELP] to create a four-week moving plan. Include packing groups, documents to update, provider questions and a first-day essentials list. Save the plan and a room-by-room checklist in [DESTINATION]. Finish with this week's top five tasks. Do not change addresses, cancel services, contact movers or share my location.
65. Draft a fair household task plan
I would use a dot to make routine work visible before discussing how we divide it.
Use [HOUSEHOLD TASK LIST], [FREQUENCY], [TIME ESTIMATES] and [AVAILABILITY PEOPLE HAVE SHARED] to draft a weekly task plan. Show workload assumptions, unassigned work and options for sharing it. Save the plan in [DESTINATION]. Finish with three discussion points for the household. Do not assign duties as agreed, message other people or infer preferences they have not provided.
66. Prepare my weekly personal review
I would ask my dot to help me see what needs attention without turning every detail into a notification.
Use [MY TASK LIST], [AUTHORIZED CALENDAR] and [GOALS I HAVE SHARED] to prepare a weekly review for [DATE RANGE]. Summarize completed commitments, unfinished work and schedule conflicts. Suggest three priorities that fit [AVAILABLE TIME]. Save the review in [PRIVATE DESTINATION]. Finish with one decision I can make today. Do not move appointments, message people or make health, legal or financial judgments.
Recurring monitors with clear notification rules
67. Watch a few competitor pricing pages
I would ask for changes I can verify, with alerts only when something relevant moves.
Every [DAY] at [TIME] [TIME ZONE] until [END DATE], compare [THREE PUBLIC PRICING URLS] with the saved baseline in [DESTINATION]. Record dated changes to prices, plan limits and included features with source links. Notify me only about a material change or failed check. Confirm the saved schedule and first baseline. Do not infer private pricing, subscribe to plans or treat unreadable pages as unchanged.
68. Monitor important website pages
I would keep an eye on a small set of pages so a visible error does not sit unnoticed.
Every [DAY] at [TIME] [TIME ZONE] until [END DATE], check [FIVE IMPORTANT PUBLIC URLS] for accessibility, visible error messages and the expected information in [CHECKLIST]. Save a dated result in [DESTINATION]. Notify me only about a new failure, material content mismatch or recovery. Confirm the schedule and supported checks. Do not edit the website or claim this replaces uptime, security or full-site monitoring.
69. Watch defined project blockers
I would let a dot monitor a few known dependencies while I concentrate on other work.
Every [WEEKDAY] at [TIME] [TIME ZONE] until [END DATE], read [AUTHORIZED PROJECT SOURCE] for the blockers listed in [REGISTER]. Update a separate review log in [DESTINATION] with source links. Notify me only when a blocker changes, a deadline is at risk or access fails. Confirm the schedule. Do not change the project board, chase teammates or create new commitments.
70. Flag a repeated support problem
I would ask my dot to notice when the same problem starts appearing more often in the data I provide.
Every [DAY] at [TIME] [TIME ZONE] until [END DATE], review new anonymized tickets in [AUTHORIZED SOURCE]. Apply [ISSUE LABELS] and flag a topic only when it reaches [EXPLICIT THRESHOLD] within [TIME WINDOW]. Save counts, examples and coverage gaps in [DESTINATION]. Notify me about a new threshold breach or failed check. Confirm the schedule. Do not reply to customers or claim complete ticket coverage.
71. Watch dates that need my decision
I would ask for a reminder when a deadline needs action, rather than another daily recap.
Every [WEEKDAY] at [TIME] [TIME ZONE] until [END DATE], review [APPROVED DEADLINE REGISTER] and [AUTHORIZED CALENDAR]. Notify me when an unresolved item enters [NOTICE WINDOW], its date changes or two commitments conflict. Save evidence and a proposed next step in [DESTINATION]. Confirm the saved schedule and deduplication rule. Do not change dates, accept invitations or send reminders to other people.
72. Check my outreach review queue
I would use my dot to keep a small outreach queue ready for review while I control the sending decision.
Every [WEEKDAY] at [TIME] [TIME ZONE] until [END DATE], inspect [APPROVED OUTREACH QUEUE], [SUPPRESSION LIST] and [AUTHORIZED REPLY EXPORT]. Flag duplicate prospects, missing evidence, opt-outs and drafts awaiting my decision. Save a dated health report in [DESTINATION]. Notify me only about a new issue or ready review batch. Confirm the schedule. Do not send messages, add contacts or update the live CRM.
How I would choose the first one
I would choose a job with clear inputs, a visible output and a quick way to judge the result. A five-company research table, one invoice draft or one transcript content pack gives you a better first test than an open-ended instruction to run your business.
You can expand the responsibility after reviewing the first batch. Add specific approval rules only when you understand the actions, recipients and limits involved.
Connections, permissions, and built-in safeguards still apply.
Frequently Asked Questions (FAQs)
What can I use OpenAI Dots for?
Ongoing jobs with clear inputs: research briefs, content packs, invoice prep, meeting notes, reports and recurring checks. The list above gives you 72 starting points.
Have you tested all 72 use cases?
No. They're proposed workflows based on what OpenAI documents Dots can do. My tested case is the outreach work in my Dots guide.
Which use case should I start with?
Pick one small job you can check fast, like a five-company research table or one invoice draft. Review that before you give your Dot anything bigger.
Will these prompts let my Dot send emails or buy things?
I wrote them to keep messages, purchases and live-system changes for your review. You decide what your Dot can do on its own, and OpenAI's built-in safeguards still apply.
