Help me start the right Sales Reps workflow.
Task to use: Write Cold Emails: make email version with trigger, support, and ask reviewable.
Paste current work: Need subject lines and one 90-word email. Use trigger from job post, mention scheduling complexity, no fake personalization. The first human check for cold email work has to compare the answer with the supplied note. A practical prompt should keep the missing details visible. Start the cold email from the rough request before shaping a cold email. A usable starting note for cold email work includes what is known, what is uncertain, and what the reviewer must verify..
Audience and constraints: SDRs and account executives writing outreach, discovery, follow-up, and proposal materials..
Who checks it: Put a cold email under a human pass from the owner closest to a prospect, buyer committee, or sales manager, with cold email quality, account trigger and pain hypothesis, and recipient-safe next step as the acceptance lens..
Before writing, ask for anything missing that would change the write cold emails: make email version with trigger, support, and ask reviewable output.
Return: A usable handoff is a ready-to-edit message with subject line, body, tone notes, and review checklist with assumptions, source-backed sections, and a reviewer note for cold email quality, account trigger and pain hypothesis, and recipient-safe next step.
Stop if: Ask for a correction if it ignores the original notes and answers from general knowledge instead.
After the first answer
Save what came back, what needs fixing, and the next prompt change before moving to another task.
0No role notes yet
Run the prompt once, check the answer, then save the problem and next try here.
Nothing saved yet
Where ChatGPT helps this role
Turn rough notes into a reviewable asset for a prospect, buyer committee, or sales manager.
Convert a recurring sales reps workflow into a reusable prompt sequence.
Ask ChatGPT for clarifying questions before committing to tone, format, or evidence.
Create a quick version for routine work and a deeper version for high-stakes work.
Review an existing answer against privacy, accuracy, and role-specific constraints.
Rewrite output for a different audience without changing the underlying facts.
Build a checklist that makes the human review faster and less subjective.
Main Risks
Keep customer data minimal and verify account research before using it.
A broad prompt can hide missing source material, so sales reps should name the exact evidence before asking for output.
Over-polished wording can make weak assumptions look finished; every page links the prompt to a review step.
Copying the same prompt across tasks weakens results because sales reps need different inputs for planning, review, outreach, and explanation work.
Recommended Workflow
Pick the task page that matches the work to finish, not just the closest job title.
Prepare the source notes, audience, constraints, and forbidden assumptions before copying a prompt.
Run the prompt once for structure, then run a review prompt against facts, tone, and missing context.
Save the final prompt with the human review checklist so the workflow can be reused without becoming automatic.
Choose the first task by situation
Start with Write cold emails when the user has source notes but does not yet know the right output structure, then move to Write LinkedIn outreach or Prepare discovery questions only after the audience and review owner are clear.
Choose by situation
Choose Write cold emails when the main problem is shaping raw context into something a prospect, buyer committee, or sales manager can inspect.
Choose Write LinkedIn outreach when the user already has a first version and needs the next artifact in the same sales reps loop.
Choose Prepare discovery questions when the risk is quality control, review consistency, or a clearer handoff to another person.
Open the role guide when the user cannot name the task yet and needs to decide whether to create, revise, review, or sanitize context first.
Avoid starting with
Do not start from a broad role prompt when the user already knows the concrete task.
Do not start from a writing prompt when the missing piece is source material or named human check.
Do not reuse a sales reps prompt across unrelated tasks without changing inputs, constraints, and review checks.
Sales Reps pages are organized by the choice a person is trying to make, not by a generic prompt collection. The role page should help the user pick the first useful task, then the task page should carry the details: source material, variable fill, example, stronger prompt, and human review boundary.
Pick the workflow by the work in front of you
Write cold emails
Use when the next useful output is a cold email and the answer needs a ready-to-edit message with subject line, body, tone notes, and review checklist.
Write cold emails needs account trigger, prospect role, pain hypothesis, support, and requested action; the check focuses on cold email quality, account trigger and pain hypothesis, and recipient-safe next step, not a generic writing pass.
Write LinkedIn outreach
Use when the next useful output is a LinkedIn outreach message and the answer needs a ready-to-edit message with subject line, body, tone notes, and review checklist.
Write LinkedIn outreach needs profile context, shared relevance, reason for contact, and low-friction ask; the check focuses on LinkedIn outreach message quality, profile relevance and mutual context, and recipient-safe next step, not a generic writing pass.
Prepare discovery questions
Use when the next useful output is discovery questions and the answer needs discovery questions with named sections, action bullets, and a final reviewer pass.
Prepare discovery questions needs buyer role, suspected problem, deal stage, product fit, and learning goal; the check focuses on discovery questions quality, pain qualification and budget path, and buyer-specific next step, not a generic writing pass.
Handle objections
Use when the next useful output is an objection-handling response and the answer needs an objection-handling response with copy-ready parts, needs-checking parts, and reuse fields.
Handle objections needs objection wording, buyer context, support, tradeoff, and next commitment; the check focuses on objection-handling response quality, objection type and empathy, and buyer-specific next step, not a generic writing pass.
Send follow-up emails
Use when the next useful output is a follow-up email and the answer needs a ready-to-edit message with subject line, body, tone notes, and review checklist.
Send follow-up emails needs sales call recap, buyer objection, agreed action, deal stage, and next-meeting goal; the check focuses on follow-up email quality, buyer commitment and objection recap, and recipient-safe next step, not a generic writing pass.
Summarize account research
Use when the next useful output is an account research summary and the answer needs a structured analysis table with claims, evidence, gaps, and recommended next step.
Summarize account research needs company page, recent signals, role map, pain hypothesis, and source links; the check focuses on account research summary quality, company signals and role map, and learning-integrity check, not a generic writing pass.
Write call summaries
Use when the next useful output is a call summary and the answer needs a call summary with copy-ready parts, needs-checking parts, and reuse fields.
Write call summaries needs call notes, choices, objections, owners, dates, and follow-up commitments; the check focuses on call summary quality, choices and objections, and buyer-specific next step, not a generic writing pass.
Write proposals
Use when the next useful output is a proposal outline and the answer needs a proposal outline with named sections, action bullets, and a final reviewer pass.
Write proposals needs client problem, scope, deliverables, timeline, support, assumptions, and pricing context; the check focuses on proposal outline quality, buyer problem and commercial support, and scope and value-risk check, not a generic writing pass.
Sales Reps get a runnable cold email setup with sample notes, copyable prompts, and a review pass for cold email quality, account trigger and pain hypothesis. It is strongest when the weak spot is outreach can look personalized while relying on a guessed trigger.
Turn account trigger, prospect role, pain hypothesis, support, and requested action into a cold email for a prospect, buyer committee, or sales manager.
Bring first
Need subject lines and one 90-word email. Use trigger from job post, mention scheduling complexity, no fake personalization. The first human check for cold email work has to compare the answer with the supplied note. A practical prompt should keep the missing details visible. Start the cold email from the rough request before shaping a cold email. A usable starting note for cold email work includes what is known, what is uncertain, and what the reviewer must verify.
Reject if
Ask for a correction if it ignores the original notes and answers from general knowledge instead.
Use this LinkedIn outreach message workflow when the raw material is profile context, shared relevance, reason for contact, and low-friction ask. It turns that material into a ready-to-edit message with subject line, body, tone notes and keeps true experience, measurable support, and target role fit in front of the person checking the answer.
Turn profile context, shared relevance, reason for contact, and low-friction ask into a LinkedIn outreach message for a prospect, buyer committee, or sales manager.
Bring first
Need connection note under 250 characters and follow-up message. Mention public post, ask about cleanup process, no fake shared contacts. connection note with relevance support needs the source note, output shape, and review owner in the same pass. The answer should carry the user's boundary into the final sections. a LinkedIn outreach message should use the note as its source. Before sales reps run this, separate facts, preferences, and limits so the finished answer does not hide assumptions.
Reject if
Hold the answer if it blurs what is known, what is assumed, and what still needs evidence.
The discovery questions setup gives sales reps a working prompt pack backed by real notes, clear limits, and reviewable output. It centers question ladder by buyer signal, not generic advice.
Turn buyer role, suspected problem, deal stage, product fit, and learning goal into discovery questions for a prospect, buyer committee, or sales manager.
Bring first
Need questions by theme: current process, incidents, budget, stakeholders, timeline, and disqualification. Keep conversational. a prospect, buyer committee, or sales manager can be misled by polished wording, so the reviewer check needs to stay visible. The copied prompt should keep the rough-note evidence intact. Treat the rough request as first-pass evidence for discovery questions. Prepare Discovery Questions works better when the context is in named fields, because each variable can be checked before copying.
Reject if
Discard the answer if it cannot trace which details came from the source and which details were inferred.
Move from a rough objections request to an objection-handling response with copy-ready parts, needs-checking parts, and reuse with runnable prompts and revision rules. The page shows when to reject the answer and what to save for reuse.
Turn objection wording, buyer context, support, tradeoff, and next commitment into an objection-handling response for a prospect, buyer committee, or sales manager.
Bring first
Need response options for implementation concern, discovery follow-ups, supporting details to request, and when to pause the deal. The first human check for objection-handling response work has to compare the answer with the supplied note. A useful version should keep the task boundary visible. Start the objection-handling response from the rough request before shaping an objection-handling response. A usable starting note for objection-handling response work includes what is known, what is uncertain, and what the reviewer must verify.
Reject if
Ask for a correction if it ignores the original notes and answers from general knowledge instead.
Use this follow-up email workflow when sales reps need to move from source notes to a shareable answer without losing the original limits. It keeps follow-up email quality, buyer commitment and objection recap visible before reuse.
Turn sales call recap, buyer objection, agreed action, deal stage, and next-meeting goal into a follow-up email for a prospect, buyer committee, or sales manager.
Bring first
Need follow-up email with recap, two pains, promised case study, next meeting ask, and no pressure language. follow-up note with promised item and timing would be weak without the source details, so the evidence has to stay attached. The saved version should keep the one-time details editable. Sales Reps should use the note as the base for a follow-up email. Before sales reps run this, separate facts, preferences, and limits so the finished answer does not hide assumptions.
Reject if
Do not use the answer if it hides unsupported claims about verified account context, buyer language, and deal stage or treats uncertainty as fact.
Move from company page, recent signals, role map, pain hypothesis, and source to a structured analysis table with claims, evidence, gaps, and recommended with the account research summary workbench. It keeps assumptions, constraints, and the person checking the answer visible while you work.
Turn company page, recent signals, role map, pain hypothesis, and source links into an account research summary for a prospect, buyer committee, or sales manager.
Bring first
Need account brief with public triggers, possible hypotheses, questions to validate, stakeholders, and risks. Label assumptions clearly. The first human check for account research summary work has to compare the answer with the supplied note. The output should carry the user's limits into every section. Start the account research summary from the rough request before shaping an account research summary. A usable starting note for account research summary work includes what is known, what is uncertain, and what the reviewer must verify.
Reject if
Ask for a correction if it ignores the original notes and answers from general knowledge instead.
Move from a rough call summary request to a call summary with copy-ready parts, needs-checking parts, and reuse with runnable prompts and revision rules. The page shows when to reject the answer and what to save for reuse.
Turn call notes, choices, objections, owners, dates, and follow-up commitments into a call summary for a prospect, buyer committee, or sales manager.
Bring first
Need summary with pain, current process, stakeholders, objections, success criteria, next steps, owner, and follow-up email bullets. The first human check for call summary work has to compare the answer with the supplied note. The response should keep the actual request visible through the edit. Start the call summary from the rough request before shaping a call summary. A usable starting note for call summary work includes what is known, what is uncertain, and what the reviewer must verify.
Reject if
Ask for a correction if it ignores the original notes and answers from general knowledge instead.
The proposal outline setup gives sales reps a working prompt pack backed by real notes, clear limits, and reviewable output. It centers proposal section outline with scope and assumptions, not generic advice.
Turn client problem, scope, deliverables, timeline, support, assumptions, and pricing context into a proposal outline for a prospect, buyer committee, or sales manager.
Bring first
Need proposal outline, executive summary, scope, timeline, support, assumptions, risks, and next step. No made-up ROI. a prospect, buyer committee, or sales manager can be misled by polished wording, so the reviewer check needs to stay visible. The copied prompt should keep the rough-note evidence intact. Treat the rough request as first-pass evidence for a proposal outline. Write Proposals works better when the context is in named fields, because each variable can be checked before copying.
Reject if
Discard the answer if it cannot trace which details came from the source and which details were inferred.