These prompts turn your inbox into a productivity machine. Copy any prompt below, fill in the variables, paste into ChatGPT, and get professional email drafts in 30 seconds. Built for working executive assistants who need results today, not tomorrow.
These prompts pair well with Jasper AI for Exec Assistants-specific tone control, or Copy.ai for fast iteration.
Meeting Coordination & Scheduling
You are an executive assistant coordinating a high-priority meeting between multiple senior stakeholders.
Meeting purpose: {meeting_purpose} Attendees: {attendee_list_with_titles} Executive’s name: {executive_name} Proposed date/time: {proposed_datetime} Meeting duration: {duration} Location/platform: {location_or_platform} Urgency level: {urgent / standard / flexible} Key preparation items: {prep_items}
Write a 150-200 word scheduling email that confirms availability, states the agenda clearly, and includes all logistics. Use a professional but efficient tone that respects everyone’s time. Include a clear call-to-action for confirmation.
When to use it: When your executive needs to pull together department heads or external partners for a decision-making meeting within 48-72 hours.
Pro tip: Always include time zones if attendees span multiple locations. ChatGPT often forgets this detail unless you add {timezone} as a variable.
You are rescheduling a previously confirmed meeting due to an urgent conflict.
Original meeting: {original_meeting_details} Attendees: {attendee_names} Reason for change: {brief_reason} New proposed options: {two_to_three_alternative_times} Executive name: {executive_name} Meeting importance: {critical / important / routine} Lead time given: {same_day / next_day / week_ahead}
Write a 100-150 word rescheduling email that apologizes efficiently, explains briefly, and offers clear alternatives. Maintain authority while showing respect for disrupted schedules. End with a deadline for responses.
When to use it: When your executive’s calendar implodes and you need to move confirmed meetings without burning relationships.
Pro tip: Include the original meeting time in the subject line format: “Rescheduling: [Meeting Name] - Originally [Date]” for easy reference.
You are following up on a meeting invitation that hasn’t received responses from key attendees.
Meeting details: {meeting_name_date_time} Non-responders: {list_of_names_and_roles} Meeting organizer: {executive_name} Days since original invite: {number_of_days} Meeting urgency: {high / medium / standard} Alternative if no response: {backup_plan} Response deadline: {specific_date_time}
Write a 120-180 word follow-up email that creates gentle urgency without being pushy. Reference the original invitation, restate key details, and give a clear deadline for responses. Include what happens if they don’t respond.
When to use it: When half your invitees have confirmed but critical stakeholders are radio silent 24-48 hours before the meeting.
Pro tip: Mention the confirmed attendees by name early in the email. Social proof works even in follow-ups.
You are sending a pre-meeting briefing email to ensure attendees come prepared.
Meeting name: {meeting_name} Date and time: {meeting_datetime} Attendees: {attendee_list} Key decisions needed: {main_decisions} Documents to review: {document_list} Data/metrics to bring: {required_data} Executive hosting: {executive_name} Meeting duration: {duration}
Write a 200-250 word pre-meeting email sent 24-48 hours ahead that outlines expectations, required preparation, and agenda flow. Use bullet points for clarity. Include attachments list and emphasize time efficiency.
When to use it: Before quarterly reviews, budget meetings, or strategy sessions where unprepared attendees kill productivity.
Pro tip: Send this exactly 36 hours before the meeting. Too early and people forget; too late and they can’t prepare properly.
You are coordinating a cross-department meeting with conflicting priorities and personalities.
Departments involved: {department_names} Main tension/conflict: {primary_disagreement} Meeting objective: {specific_outcome_needed} Key stakeholders: {names_and_roles} Timeline pressure: {deadline_or_urgency} Executive facilitating: {executive_name} Proposed solutions: {potential_compromises} Meeting length: {duration}
Write a 180-220 word invitation email that acknowledges different perspectives, sets collaborative expectations, and structures the agenda to minimize conflict. Frame the meeting as problem-solving, not blame assignment.
When to use it: When sales and marketing are fighting over leads, or operations and finance are clashing over budget priorities.
Pro tip: Seat people strategically and include a seating chart in complex meetings. Physical positioning affects meeting dynamics.
Client and Stakeholder Communication
You are communicating a significant delay or setback to an important client on behalf of your executive.
Client name: {client_name} Project/deliverable: {project_details} Original deadline: {original_date} New timeline: {revised_timeline} Reason for delay: {brief_explanation} Mitigation steps: {actions_being_taken} Executive name: {executive_name} Compensation offered: {discount_credit_or_none} Next update schedule: {when_next_communication}
Write a 200-280 word email that owns the problem, explains the situation clearly, and maintains client confidence. Lead with accountability, not excuses. Include specific recovery actions and next steps.
When to use it: When your executive is in back-to-back meetings but a client needs immediate communication about missed deadlines or budget overruns.
Pro tip: Always include a specific date for the next update, even if you don’t have full resolution yet. Clients hate communication black holes.
You are requesting additional information or documentation from a client to move a project forward.
Client contact: {client_contact_name} Project name: {project_identifier} Information needed: {specific_requirements} Why it’s needed: {brief_justification} Current project status: {where_things_stand} Deadline impact: {how_delay_affects_timeline} Executive name: {executive_name} Urgency level: {critical / important / standard} Format needed: {file_type_or_specifications}
Write a 150-200 word request email that explains why you need the information, how it impacts their project, and gives clear instructions for what to send. Make it easy for them to comply quickly.
When to use it: When projects stall because clients haven’t provided contracts, approvals, content, or technical specifications you’re waiting on.
Pro tip: Include examples of the format you need. A sample filename or document structure saves multiple back-and-forth emails.
You are scheduling a quarterly business review with a key client on behalf of your executive.
Client company: {client_company} Primary contact: {client_contact_name} Relationship duration: {how_long_working_together} Recent wins: {key_achievements_this_quarter} Topics to cover: {agenda_items} Executive presenting: {executive_name} Proposed duration: {meeting_length} Meeting format: {in_person_video_call} Supporting attendees: {who_else_attending}
Write a 180-240 word invitation email that positions the meeting as valuable for the client, highlights recent successes, and creates anticipation for strategic discussion. Include agenda overview and logistics.
When to use it: When quarterly reviews are coming up and you need to lock in calendar time with C-suite clients who have packed schedules.
Pro tip: Mention specific metrics or wins in the subject line like “Q3 Review - 40% Growth Discussion” to guarantee email opens.
You are following up on a proposal that was sent to a prospect several weeks ago.
Prospect name: {prospect_contact} Company: {prospect_company} Proposal details: {brief_proposal_summary} Date sent: {original_send_date} Proposal value: {contract_value} Decision timeline: {their_stated_timeline} Key benefits highlighted: {main_value_props} Executive who presented: {executive_name} Next steps proposed: {what_you_want_them_to_do}
Write a 160-200 word follow-up email that resurfaces the proposal value without being pushy. Reference specific benefits for their situation and offer to answer questions or schedule a discussion call.
When to use it: When promising prospects go dark after receiving detailed proposals and your executive needs to know where things stand.
Pro tip: Reference one specific metric or outcome from the original proposal to jog their memory about the value discussed.
You are coordinating a client complaint escalation that requires executive attention.
Client name: {client_name} Complaint summary: {main_issue} Financial impact: {revenue_at_risk} Previous attempts to resolve: {what_has_been_tried} Client contact person: {who_is_complaining} Urgency level: {immediate / urgent / standard} Proposed resolution: {executive_solution} Executive handling: {executive_name} Legal/PR concerns: {any_public_risk}
Write a 200-250 word email to the client that acknowledges their frustration, takes ownership of the problem, and outlines specific steps for resolution. Include timeline commitments and executive contact information.
When to use it: When front-line customer service can’t resolve an issue and the client is threatening to leave or escalate publicly.
Pro tip: Include your executive’s direct phone number only for truly critical issues. It shows commitment but protects their time.
Internal Team Updates and Announcements
You are announcing an organizational change that affects multiple departments.
Change description: {what_is_changing} Effective date: {when_change_starts} Departments affected: {which_teams} Reason for change: {brief_business_justification} New processes: {how_things_will_work} Training provided: {support_available} Executive sponsor: {executive_name} Questions contact: {who_to_ask} Timeline for full implementation: {rollout_schedule}
Write a 250-300 word internal announcement that explains the change clearly, addresses likely concerns preemptively, and provides clear next steps. Use a tone that’s informative but reassuring.
When to use it: When your executive needs to communicate restructuring, new policies, system changes, or process updates to the broader organization.
Pro tip: Send these announcements on Tuesday or Wednesday mornings. Monday emails get buried and Friday announcements get forgotten over weekends.
You are sharing quarterly results and company performance updates with all staff.
Quarter/period: {reporting_period} Key metrics: {main_performance_numbers} Goals achieved: {wins_and_successes} Areas for improvement: {challenges_or_misses} Individual recognition: {team_or_people_to_highlight} Market context: {external_factors} Next quarter priorities: {upcoming_focus_areas} Executive message from: {executive_name} All-hands meeting: {date_if_scheduled}
Write a 300-350 word company-wide email that celebrates wins, honestly addresses challenges, and rallies the team around upcoming goals. Balance transparency with motivation.
When to use it: After quarterly board meetings when your executive wants to cascade key results and strategic direction to the entire company.
Pro tip: Include one specific customer win or employee story. Abstract numbers don’t motivate people; real examples do.
You are communicating a policy change that may be unpopular with staff.
Policy changing: {specific_policy} Old policy: {how_it_worked_before} New policy: {how_it_works_now} Reason for change: {business_justification} Effective date: {when_it_starts} Exceptions process: {how_to_request_special_cases} Implementation support: {training_or_resources} Executive approving: {executive_name} Questions contact: {hr_or_manager_contact}
Write a 220-280 word policy announcement that explains the reasoning clearly, acknowledges the impact on employees, and provides implementation details. Be direct but empathetic in tone.
When to use it: When announcing changes to remote work policies, expense guidelines, PTO rules, or other employee-facing policies that affect daily work life.
Pro tip: Always include the effective date in the subject line. Employees need to know immediately when changes kick in.
You are announcing a new hire joining the executive team.
New hire name: {new_executive_name} Position/title: {exact_job_title} Start date: {first_day} Background summary: {previous_experience} Why they were chosen: {key_qualifications} Reporting structure: {who_they_report_to} Teams they’ll oversee: {direct_reports_or_departments} Introduction plan: {how_they_will_meet_teams} Announcing executive: {current_executive_name}
Write a 200-250 word announcement email that builds excitement about the new hire, establishes their credibility, and sets expectations for integration. Include how teams can connect with them initially.
When to use it: When announcing new VPs, directors, or C-suite hires who will impact multiple departments and need strong first impressions.
Pro tip: Include one specific achievement from their background that directly relates to current company challenges. It builds immediate credibility.
You are communicating an emergency policy or procedure update due to external circumstances.
Emergency situation: {external_event_or_crisis} Immediate actions required: {what_employees_must_do} Policy changes: {temporary_or_permanent_updates} Safety measures: {health_security_precautions} Work arrangements: {remote_office_schedule_changes} Resources available: {support_provided} Information updates: {how_often_communication_will_come} Executive coordinating: {executive_name} Questions contact: {emergency_contact_info}
Write a 250-300 word urgent communication that provides clear direction, reduces anxiety, and ensures everyone knows their immediate responsibilities. Use calm but decisive language.
When to use it: During natural disasters, security threats, health emergencies, or major technology failures that require immediate company-wide response.
Pro tip: Use “URGENT” in the subject line only for true emergencies. Overuse kills the effectiveness when you really need immediate attention.
Project Status and Timeline Updates
You are updating stakeholders on a project that is significantly behind schedule.
Project name: {project_identifier} Original timeline: {initial_deadline} Current status: {percentage_complete} Main blockers: {specific_obstacles} Revised timeline: {new_realistic_deadline} Recovery plan: {steps_to_accelerate} Resource needs: {additional_support_required} Executive sponsor: {executive_name} Next milestone: {immediate_next_deliverable} Stakeholders affected: {who_needs_to_know}
Write a 250-300 word project update that honestly assesses the situation, takes ownership of delays, and presents a credible recovery plan. Include specific actions and accountability measures.
When to use it: When major initiatives are running late and stakeholders need realistic timelines rather than optimistic promises that won’t be met.