I am forwarding an email where a prospect mentions they are also talking to a competitor.

Analyze the specific features or pricing models they mentioned regarding the competitor. Compare this against our known strengths (speed, service, ease of use). Identify if the prospect has a misconception about our product compared to theirs.

Output a set of "Talking Points" for my next call. Do not trash the competitor; instead, provide 3 "Trap-Setting Questions" I can ask the prospect that will highlight the competitor's weakness without me saying it directly.

I am forwarding the final email where the client said "Yes" to the deal, including the agreed-upon terms.

I need to hand this account over to the Onboarding/CS team. Summarize the "Promises Made" during the sales cycle so the CS team isn't blind. Highlight any special expectations the client has regarding timeline or custom features.

Format this as an internal memo using the headings: "Client Success Goals," "Promised Go-Live Date," and "Potential Friction Points." Keep it professional and strictly internal-facing.

I will forward an email where a prospect is pushing back on our quote or asking for a discount.

Your goal is to draft a reply that acknowledges their budget constraint without immediately caving on price. Use the "Feel, Felt, Found" method: validate their concern, mention other clients felt the same, but found that the ROI justified the cost. Pivot the conversation back to value and long-term savings.

Draft a response of about 150 words. Keep the tone empathetic but firm. End with a question that invites them to discuss scope reduction rather than price reduction.

I am forwarding an email with a specific, complex security question from a Request for Proposal (RFP) document we received.

Reference our internal "Security Standard Knowledge Base" (which I attached) and draft a standard "safe" response regarding SOC2 compliance and data encryption. If the question asks for something we likely don't do, draft a polite deferral explaining it's on the roadmap.

Provide a clear, formal paragraph suitable for copy-pasting. No slang, strictly business technical writing.

I will forward you an initial inquiry email from a potential customer that just came through our website form.
 
Analyze the text to determine the prospect's company size and urgency. Look for keywords like "enterprise," "immediate," or "budget." If they seem small/low-budget, suggest our self-serve path. If they seem large, stratify them as a "Key Account" and focus on our premium support value proposition.

Output a draft response based on that classification. Keep the tone helpful but concise. Do not include placeholder brackets; instead, write the email so it is 90% ready to send, requiring only a quick signature check.

I am forwarding you a previous email thread where the prospect stopped responding after our demo weeks ago.

Read the context of our last conversation to understand what feature they were most excited about. Use that specific feature as a "hook" to check in. Do not use generic "just checking in" language. Instead, share a "relevant resource" or "new update" related to their interest.

Output a short, casual email (under 75 words). It should feel like a quick ping from a friend, not a formal sales letter. End with words like "thought this might help.”

I am forwarding a chain of emails exchanged with a client, along with a PDF of their original RFP.

I have a renewal meeting with them tomorrow. Please synthesize the key pain points they have mentioned recently and any outstanding support tickets referenced in the thread. Identify the main decision-maker involved in the conversation.

Produce a bulleted "Pre-Meeting Cheat Sheet." Group points under: "Current Sentiment," "Unresolved Issues," and "Upsell Opportunities." Keep the whole summary under one page.

I am forwarding a long email thread or a raw text block containing a messy email signature.

Scan the text and identify the sender's full name, job title, direct phone number, and physical mailing address. You need to ignore generic support lines and focus on the specific individual's direct contact methods.

Present the output as a clean JSON snippet.

I will send you a CSV file or a text list containing a prospect's LinkedIn bio and their company's latest news headline.

Connect their personal professional interest (from the bio) with how our solution can help their company's new initiative (from the news headline). The connection needs to be logical, not forced. Avoid buzzwords like "synergy" or "disrupt."

Draft a 3-sentence "hook" email. Sentence 1: Context/Observation. Sentence 2: The Problem/Insight. Sentence 3: Soft Call to Action (e.g., "Worth a chat?").

I am forwarding an email where a client just gave us a huge compliment or expressed high satisfaction.

This is the perfect moment to ask for a referral. Acknowledge their praise warmly. Then, pivot to a "small ask": inquire if they know anyone else in their network (specifically in their industry) who might face similar challenges.

Draft a response that feels humble, not greedy. Keep it short. "I'm so glad we could help... by the way, if you know anyone else...”

I am pasting my raw, messy shorthand notes from a discovery call into this email.

Organize these fragments into a coherent follow-up email to the client. Group the points into "What We Heard," "Our Proposed Solution," and "Next Steps." Ensure you capture the dates and times I scribbled down for the next meeting.

Output a polished client-facing email. Use bullet points for readability. The tone should be "consultative and organized." Ensure the subject line is "Recap: [Company Name] + [Our Company] Discussion.”

I am pasting a list of different deals I'm working on, with random notes about their status.

My manager needs a clean "End of Week Pipeline Update." Organize these deals into three buckets: "Commit" (Closing this week), "Best Case" (Might close), and "Pipeline" (Early stage). Flag any deal that has stalled for more than 14 days.

Format this as a clean, bulleted email summary for my VP of Sales. Use bold text for the Deal Name and Dollar Amount. Keep the commentary for each deal to one sentence maximum.

I am attaching a messy CSV file containing leads exported from a trade show scanner.

The names are often in all-caps or all-lowercase, and the phone numbers have inconsistent formatting (some have dots, some dashes). Please normalize the text: Title Case for names (e.g., "John Doe") and a standard (XXX) XXX-XXXX format for phone numbers. Remove any rows where the email address is missing.

Return the cleaned data as a downloadable CSV file. Do not include any conversational text, just the data.

I am forwarding the last three monthly reports sent to this client.

I need to present a Quarterly Business Review (QBR). Look at the trends in the reports—is usage going up or down? Identify the biggest win we achieved for them in the last 3 months and one area where they are underutilizing the tool.

Output a 5-slide presentation outline. For each slide, write the Headline and 3 bullet points of talking track. Focus on "ROI Delivered" and "Future Roadmap.”

I am sending you the raw offer details: Candidate Name, Title, Salary, Stock Options, and Start Date.

Populate these details into our standard "Tech Offer Letter" template that I attached below. If the start date is less than 2 weeks away, add a "Signing Bonus" clause of $5,000 automatically.

Output the final result as a downloadable PDF file. Ensure the formatting is formal, with placeholders for signatures at the bottom.

I am forwarding the job description for our new role.

I need an image to post on LinkedIn / Instagram to promote this role. Analyze the job description to find the 3 most exciting keywords (e.g., "Remote," "Leadership," "Innovation"). Conceptualize a visual that is modern, vibrant, and not a boring stock photo of people shaking hands.

Output an Image in PNG, 1800 by 1800 pixel. Also, write the caption text for the social post including hashtags.

I am sharing a LinkedIn profile of a "Perfect Match" candidate we want to poach from a competitor.

Analyze their "About" section and their recent "Activity/Posts." Find a specific project or interest they mentioned to use as an icebreaker. The goal is to get them on a coffee call, not to sell them a job immediately. Avoid generic recruiter jargon like "impressive background."

Draft a short LinkedIn InMail message (under 300 characters) that feels bespoke and intriguing. End with a low-friction question like "Open to a virtual coffee?"

I am auto-forwarding all LinkedIn and Indeed notification email of new message with the subject line "New Message from [Name]."

Parse the body of the emails to extract the name who sent the message, The JD page they messaged from, and the Link to their profile. Research their profile extensively for information of their employment and education background. Compare the research results with the JD to decide if they could be a potential fit for that role.

Output your conclusion as a rating in three tier: Strong Yes, Yes, Maybe, No

I am forwarding this email to you with the details of a new hire: Name, Department, Start Date, and Manager Name.

Based on the Department provided (Sales, Engineering, or Admin), generate a specific onboarding checklist. If Engineering, include "GitHub Access" and "Laptop Config"; if Sales, include "Salesforce License" and "Shadow Call Schedule." Ensure the dates are calculated relative to their Start Date (e.g., "Day 1," "Week 1").

Output this as a clean PDF document that I can attach and send to the hiring manager.

I am sending a file containing current employee salaries in a specific department, along with the latest market rate data I found online.

Compare our current pay against the market median. Identify which employees are significantly underpaid (more than 10% below market) and which are at the top of the band. Calculate the total budget impact if we brought everyone up to the market median.

Output a Summary Report highlighting the "At Risk" employees for retention. Include a small table showing the cost calculation.

I am forwarding emails from candidates regarding to benefits.

Read the employee's question and reference the Employee Handbook I attached. If the answer is clearly in the handbook, draft a reply quoting the page number. If it involves a "qualifying life event" like marriage or birth, list the documents they need to submit.

Output a draft email reply. It must contain a disclaimer at the bottom: "Please consult the official plan documents for full details."

I am attaching a messy timesheet export from our legacy clock-in system. It has weird spacing and "clock in/out" text mixed with numbers.

Clean this data. I need to calculate the total hours worked per employee per week. Round to the nearest 0.25 hour. Flag any day where the hours exceed 12 (potential labor law violation).

Output a clean CSV file with columns: Employee ID, Week Ending, Total Regular Hours, Total Overtime Hours. This must be ready for import into ADP.

I am attaching an Excel file containing raw text responses from our recent "Employee Satisfaction Pulse Survey."

Analyze the sentiment of the open-ended comments. Categorize them into "Compensation," "Work-Life Balance," and "Management." Calculate the percentage of positive vs. negative sentiment for each category.

Output a Python code block using the Matplotlib library that, when run, would generate a bar chart visualizing these sentiment percentages. I want to copy this code to generate a chart for my slide deck.

I am attaching the transcript file from an exit interview with a departing employee.

Read through the conversation to identify the root cause of their departure. Look beyond the polite "better opportunity" excuse—did they mention burnout, bad management, or lack of growth? Quote the specific sentence where they revealed the truth.

Output a "Flight Risk" Alert email addressed to the VPs of related department. Summarize the key reason for leaving and suggest three immediate changes to prevent others from following them.

I am sending you a batch of PDF resumes (or a zipped folder) for our Senior Product Manager role.

Scan these documents against the following "Must-Have" criteria: 7+ years of experience, PMP or Agile certification, and specific mention of "budget management" over $50k. Disregard layout or design; focus strictly on the text data. Flag any employment gaps longer than 9 months without explanation.

Output your findings as a downloadable CSV file. The columns should be: Candidate Name, Years Experience, Has Certification (Y/N), Budget Experience (Y/N), and Fit Score (1-10).

I am forwarding an email with the hiring manager's notes included on the candidate we interviewed and decided NOT to move forward.

Draft a rejection email that feels personal and kind, not robotic. Reference one specific positive thing the manager noted (e.g., "we loved your portfolio" or "great energy") to soften the blow. Do not promise a future role unless I explicitly said so in the notes.

Output the text as a draft email body. Keep it professional but warm. Subject line should be "Update on your application with [Company Name]."

I am attaching a draft job description that a hiring manager just wrote.

First audit based on the company culture guideline PDF attached for non-inclusive or potentially conflicting, off brand language (e.g., "ninja," "rockstar," "work hard play hard"), then based on the JD template attached, generate the final version of the job description.

Output the text that I can copy-paste into a word document.

I am forwarding a messy email from a customer asking about the status of their order. They usually bury the details in a paragraph of text.

Scan the email text to extract the unique Order Number (usually starts with # or OR-), the SKU or Product Name mentioned, and the Customer's Shipping Address if present. If any of these are missing, note them as "Not Provided."

Output a JSON code snippet containing these fields. I want to use this to query our logistics database automatically without manually copying and pasting numbers.

I am forwarding a long, complex email thread containing a technical issue that I cannot solve and need to escalate to Tier 2 Engineering.

Review the entire history of the conversation. Summarize the troubleshooting steps I have already attempted so the engineer doesn't ask the customer to do them again. Clearly define the "Steps to Reproduce" the bug based on the customer's description.

Output a structured internal note titled "Escalation Ticket." Use bold headers for Current Behavior, Expected Behavior, and Attempted Fixes. Keep it concise so the engineer can start working immediately.

I am forwarding an email thread where we successfully resolved a new issue for a customer.

Transform this specific solution into a general Help Center article. Remove all personal details (names, specific account IDs) and greetings. Generalize the problem description so it applies to any user facing this error. Break the solution down into numbered, imperative steps (e.g., "1. Go to Settings...").

Output the result in Markdown format. Include a catchy, search-optimized title (e.g., "How to fix...") and a short "Symptoms" section at the top.

I am auto forwarding a customer's request for a refund.

I attached a PDF attachment of our official "Terms of Service" and use it to: 1. check the customer's request date against the purchase date mentioned in their email, and compare this to the "Refund Window" clause in the attached PDF; 2. Also check if their reason for return matches the "Valid Exceptions" list in the policy.

Output a Decision Memo. State "Eligible" or "Ineligible." If ineligible, quote the specific clause from the PDF that justifies the denial so I can include it in my reply.

I am sending an image file (screenshot) that a user sent showing an error message on their screen.

Perform OCR (Optical Character Recognition) to extract the exact text of the error code and the description message in the popup box. Ignore the background UI elements.

Output the extracted text as a plain string. Then, underneath it, provide a search query link (e.g., "Search Knowledge Base for [Error Code]") that I can click to find the solution.

I am forwarding an email from a highly frustrated customer who is expressing significant dissatisfaction with our service or product.

Read through the emotional language to identify the core technical or service failure. Do not get defensive. Apply the "HEARD" framework (Hear, Empathize, Apologize, Resolve, Diagnose). Draft a response that validates their feelings immediately ("I can see why this is frustrating") before pivoting to the solution. Avoid generic apologies; be specific about what went wrong.

Output a draft email response. The tone should be calm, professional, and reassuring. End with a clear next step that puts the ball in our court, not theirs.

I am auto-forwarding emails that are sent to our Feature Request address.

Read the user's request to understand the problem they are trying to solve, not just the feature they are asking for. Compare this to our known core capabilities (refer to this url of our current updated product documentation). Summarize what is missing in our product that forced them to ask for this.

Output a User Story in the format: "As a [User Type], I want to [Action], so that [Benefit]." Add this to a weekly digest for the Product Team.

I am forwarding an inquiry email written in a foreign language (non-English).

First, detect the language and provide a 2-sentence English summary of what the customer is asking so I understand the context. Then, draft a polite, helpful response in their native language answering their question. Use simple, standard phrasing to avoid translation errors. Refer to the FAQ document I attached.

Output the English summary first, followed by a separator line, and then the localized response text ready to send.

I am forwarding an internal technical status update from our engineering team that will have impact on our product.

Translate this technical jargon (e.g., "server latency," "database rollback") into plain English for our customers. The goal is to inform them about the seriousness of the issue, impact to them, and that we are aware of the issue and working on it, without causing panic. This is information will be displayed in our website and sent out to email groups. Do not promise a specific "fixed by" time unless the engineers explicitly stated one.

Output in two formats: First, draft email with the subject line "Service Update: [Product Name] Performance." Keep it under 100 words; Second, short message to display on the website.

I am attaching a CSV export of our help desk volume for the last month.

Analyze the data to find trends. Group the ticket volume by "Day of Week" and "Category." Identify which day had the highest spike in volume and what the top category was during that spike.

Output a Python script using the Pandas and Seaborn libraries. When run, this script should generate a Heatmap visualization showing ticket density by day and hour. I need to put this chart in my weekly report.

I am forwarding a raw text file exported from our live chat widget. It contains timestamps, system messages (e.g., "User joined chat"), and messy spacing.

Clean up this text to create a readable conversation history for the customer's file. Remove all timestamps, system notifications, and IP addresses. Keep only the dialogue between "Agent" and "Customer." Fix any broken line breaks.

Output the cleaned conversation as a PDF-ready text block. It should look like a script: Agent: Text... Customer: Text...

I am forwarding a finalized blog post or newsletter draft that we are about to publish.

Read the content to identify the three most "quote-worthy" insights or statistics. Repurpose these points into social media captions: one for LinkedIn (professional, storytelling focus, line breaks for readability) and one for X/Twitter (punchy, thread style, under 280 chars per tweet).

Output a structured text block separated by platform headers. Include 5 relevant hashtags for each platform based on the content keywords.

I am forwarding a "How-to" help article or a product feature announcement.

Adapt this text content into a script for a 60-second TikTok or Instagram Reel. It needs a "Hook" in the first 3 seconds (visual or audio). Break the explanation down into 3 fast cuts. Keep the tone high-energy and conversational, using "You" instead of "Users."

Output a 2-column script table: Column 1 for "Visual/Action" (what the camera sees) and Column 2 for "Audio/Dialogue" (what the speaker says).

I am forwarding a marketing email received from one of our direct competitors.

Deconstruct their strategy. Identify the primary "Call to Action" (CTA) and the psychological trigger they are using (e.g., FOMO, Social Proof, Greed). Analyze their subject line—why did it work (or fail)? Note any personalization tokens they used.

Output a Strategic Breakdown listing: "Subject Line Score," "Core Offer," and "One Takeaway We Should Steal/Avoid."

I am auto-forwarding my daily industry newsletters (e.g., TechCrunch, AdAge) to you.

Filter through the noise. Identify the top 3 stories that are most relevant to our specific industry (B2B SaaS / Fintech). Ignore general world news or competitor stock prices. Synthesize the key takeaway of each story and why it matters to our strategy, attached below

Output a daily Curated Digest in bullet points. Include the original link for each story. I will use this for our Morning Standup.

I am forwarding a copy document for a new ad campaign. It describes the product benefits and target audience.

Based on the emotional tone of the copy (e.g., "exciting," "trustworthy," "futuristic"), conceptualize 3 distinct visual ideas for the campaign imagery. Describe the lighting, composition, and subject matter in detail. Avoid text-heavy descriptions; focus on the visual scene.

Output 3 separate Image Generation Prompts (optimized for the most updated Nano Banana) that I can copy-paste to generate concept art.

I am forwarding a product spec sheet for a feature launching on [Date].

Work backward from the launch date to create a 4-week content promotion calendar. Week 1: Tease/Problem Awareness. Week 2: Solution/Education. Week 3: Launch/Hype. Week 4: Social Proof/Case Studies. Suggest one asset type (Blog, Email, Webinar, Tweet) for each major beat.

Output the result as a CSV file with columns: Date, Topic, Asset Type, and Channel. I will import this into Asana/Notion.

I am forwarding a draft article in html along with a list of target keywords (e.g., "Primary: AI Tools," "Secondary: Productivity").

Review the draft. Naturally weave the primary keyword into the first 100 words and at least one H2 header. Check if the secondary keywords are present; if not, suggest a sentence where they can be added without sounding forced. Ensure the reading level remains at "Grade 8" simplicity.

Output the revised text with the inserted keywords highlighted in bold so I can see the changes immediately.

I am forwarding the work of campaign copy written by a new freelancer.

Review the text against our "Brand Voice Guidelines" (attached below). Flag any words that sound too corporate (e.g., "synergy," "leverage") or too slangy. Check that we are using active voice.

Output a "Red Pen" Report in PDF. Quote the problematic sentence, explain why it's off-brand, and offer a "Rewritten Version" that fits our tone perfectly.

I am sharing a media kit or a link to an influencer's Instagram profile.

Analyze their recent content. Do they align with our brand values (Sustainability, Tech-forward)? Look at their engagement—are the comments real conversations or just emojis/bots? Check if they have worked with our competitors recently.

Output a "Fit Assessment" Scorecard. Rate them on: "Audience Match," "Content Quality," and "Brand safety." Conclude with a "GO / NO-GO" recommendation.

I am uploading a raw text file from an automated video transcription service (like Otter.ai). It has no punctuation and lots of "um," "ah," and repeated words.

Clean the text into a readable blog post format. Add proper punctuation and paragraph breaks. Remove the filler words. Insert H2 subheaders where the topic shifts. Do not change the speaker's meaning, just make it readable prose.

Output the formatted text ready to be pasted into Webflow CMS.

I am forwarding a destination URL (e.g., our new blog post) and a list of channels where we plan to share it (LinkedIn, Facebook, Email Newsletter, Partner Co-marketing).

Construct proper UTM tracking links for each channel. Use standard parameters: utm_source (channel), utm_medium (social/email), and utm_campaign (use the blog post slug). Ensure the syntax is correct with no spaces.

Output a clean table with the Channel Name on the left and the ready-to-use Long URL on the right.

I am forwarding two versions of a contract: the original draft we sent and the "markup" version the client just sent back.

Compare the text of the two documents. Identify exactly what they changed. Ignore formatting changes (font size, spacing). Focus on material changes to numbers (price, liability caps) and deleted clauses. Determine if they removed our "Indemnification" protection.

Output a "Change Log" Summary. List the Section Number and a brief description of the change (e.g., "Section 4.2: Liability cap reduced from $1M to $500k").

I am auto-forwarding emails that contain PDF invoice attachments from our vendors.

Perform OCR on the attached PDF to extract the key financial data points. Specifically, look for: Vendor Name, Invoice Number, Invoice Date, Total Amount, and Tax Amount. Ignore any marketing text or footer disclaimers. If the "Due Date" is missing, calculate it as 30 days from the Invoice Date.

Output the result as a CSV line with headers. Ensure the date format is standardized to YYYY-MM-DD.

I am forwarding a statement for a client who is overdue on their payment.

Draft a polite but firm reminder email. The tone should be "professional partnership," assuming it was just an oversight. Reference the specific Invoice Number and the Total Due amount found in the attachment. Offer to resend the original invoice if they lost it.

Output a ready-to-send email body. Subject line should be "Friendly Reminder: Invoice [Number] - [Company Name]."

I am forwarding a file of credit card transactions from this month's statement.

Analyze the "Merchant Name" for each row and assign the correct "General Ledger (GL) Category" based on common sense. For example, "Starbucks" = "Meals & Entertainment"; "AWS" = "Software Subscription"; "Delta" = "Travel." If you are unsure, label it "Uncategorized."

Output a Table with two columns: Merchant Name and Proposed GL Category.

I am forwarding a standard Non-Disclosure Agreement (NDA) sent by a potential partner.

Review the legal terms. Verify if it is "Mutual" (protects both sides) or "One-way." Check the governing law/jurisdiction—flag it if it is not in our home state/country. Look for any "Non-Solicitation" clauses that would prevent us from hiring their staff.

Output a Risk Summary. If it is a standard mutual NDA, state "Low Risk / Standard." If there are odd clauses, list them in bullet points under "Red Flags."

I am forwarding an email with a photo of a receipt for a travel expense reimbursement.

Check the receipt against our "T&E Policy" which I attached in this email. Verify if the expense date is within the last 60 days. Check if there is alcohol listed (look for keywords like "wine," "beer," "cocktail"). If the total is over $50, ensure the merchant name and date are clearly visible.

Output a Validation Status. If it passes, say "Approved." If it fails, list the specific policy violation (e.g., "Alcohol detected," "Receipt illegible").

I am forwarding an email chain showing the approval process for a large purchase.

Consolidate this thread into a single, clean "Proof of Approval" document for the auditors. Remove the "Re:" and "Fwd:" clutter. Clearly label who requested it, the timestamp of the request, and the timestamp/name of the person who replied "Approved."

Output a Compliance Memo. It should clearly state: "Transaction #12345 was authorized by [Name] on [Date]."

I am sharing evidence (screenshots/links) that a competitor is using our copyrighted images/logo without permission.

Draft a formal "Cease and Desist" letter. The tone should be stern and legal. State that we are the copyright owner, demand the immediate removal of the infringing content within 48 hours, and reserve the right to pursue legal action.

Output the Letter Text. Include placeholders for [Date] and [Offender Name]. Ensure it sounds like it came from a legal department.

I am forwarding a spreadsheet of closed deals for the month and the specific "Commission Plan" PDF for this sales rep.

Apply the logic from the plan to the deal list. Calculate the payout for each deal. Note if there are "Accelerators" (higher % after hitting quota). If a deal is marked "Pending Payment," exclude it from the calculation.

Output a Commission Statement. Show the math: Deal Amount x Rate = Commission. Provide a Grand Total at the bottom.

I am forwarding a W-9 (or W-8BEN) tax form received from a new freelancer.

Check the form for completeness. Is the "Name" field filled out? Is the "SSN/EIN" box not empty? Most importantly, is there a signature and date at the bottom? If the date is older than 12 months, flag it as "Expired."

Output a Verification Note. State "Valid" or "Invalid." If invalid, draft a one-sentence email I can send back to them explaining exactly what is missing.

I am sharing the URL to a new local tax regulation or compliance update that was just released.

Summarize this legal text into a "What this means for us" memo. Avoid the legalese. Focus on the operational impact: Do we need to change how we charge tax? Do we need to file a new form? Is there a deadline?

Output a Plain English Summary for the management team. Use bullet points for "Key Changes" and "Action Items."

I am auto-forwarding emails with the subject "Data Subject Access Request" or "Delete My Data."

Review the email to identify the user's email address and the specific right they are exercising (Right to be Forgotten vs. Right to Access). Check if they provided proof of identity (attachment). If not, flag that we need to ask for ID.

Output a Process Ticket. "Action Required: [Delete/Export]. User: [Email]. Deadline: [30 days from Email Date]."

I am forwarding a complex commercial office lease agreement.

Extract the critical dates and financial obligations. Specifically, find: The Lease Commencement Date, the Expiration Date, the Monthly Base Rent, and the Rent Escalation clause (how much it goes up per year). Also, check who is responsible for HVAC repairs (Landlord or Tenant).

Output a Lease Abstract document. Use a bold header for each data point so I can quickly enter it into our property management system.

I am auto-forwarding the weekly update emails from our external marketing agency.

They usually send long, fluffy emails. Cut through the noise. Tell me: What did they actually deliver this week? What do they need from me (approvals/assets)? Are they on track with the budget we set?

Output a "glanceable" summary. Use bullet points. If there are no action items for me, simply state "Status: Cruising."

I am forwarding a list of project tasks in random order.

Analyze the logic to determine dependencies. For example, "Write Code" must happen before "Test Code." "Design UI" must happen before "Build Frontend." Identify the "Critical Path"—the sequence of tasks that dictates the minimum project duration.

Output a Dependency List. Format: "Task A -> blocks -> Task B." Highlight the Critical Path tasks in bold.

I am forwarding an email from a client asking for "just a small tweak" or "one more feature" mid-project.

Compare this request against the original "Scope of Work" (SOW) document attached. specific specifically why this is not a small tweak. Analyze the downstream impact: Will this require design changes? Will it delay the dev sprint? Explain the consequences in business terms (time/cost).

Output a Impact Assessment email draft. "We can do this, but it will push the launch date by [X] days and incur an overage fee of [X]."

I am forwarding an invoice from a contractor along with the project code (e.g., PROJ-101).

Extract the invoice amount. I will also paste the "Total Budget" and "Spent to Date" for this project. Subtract the new invoice amount from the remaining budget. Calculate the percentage of the budget consumed.

Output a Budget Alert. If we have used more than 80% of the budget but the project is only half done, add a "WARNING" label.

I am attaching a spreadsheet containing anonymous feedback from our Sprint Retrospective.

Analyze the text comments. Group them into the standard Agile categories: "Start Doing," "Stop Doing," and "Continue Doing." Look for patterns—if 3 people mention "long meetings," group those into a single "Theme: Meeting Fatigue."

Output a Thematic Summary. List the top 3 themes that need attention and suggest one actionable experiment we could try next sprint to fix the biggest issue.