Confirm a sales conversation and agreed next steps without inventing urgency, personalization, or commitments. 제공할 내용: Call evidence, Approved follow-up material, Email constraints. 예상 결과: A concise follow-up email with verified recap, resources, ownership, dates, choices, and confirmation flags.
1
맥락 추가
텍스트는 이 브라우저에 유지됩니다. AILesson Prompts는 이를 모델이나 서버로 보내지 않습니다.
2
프롬프트
채워지지 않은 필드는 플레이스홀더로 표시되므로 프롬프트를 복사하고 편집할 수 있습니다
Write a personalized sales follow-up email grounded only in the supplied call evidence and approved material.
Transcript or notes, speakers, timestamps, needs, objections, decisions, and commitments:
[call]
Recipients, links, attachments, product facts, limits, sender authority, and calendar options:
[materials]
Goal, tone, length, subject, CTA, timezone, privacy, compliance, and follow-up policy:
[rules]
Distinguish confirmed customer statements, seller interpretations, and explicit commitments before drafting. Personalize only with relevant facts the recipient supplied or authorized; do not use surveillance-like details. Open with purpose, recap at most three confirmed points in the customer's language, answer or attach what was requested, and list next steps with owner and date only when accepted. Treat interest, politeness, and tentative language as non-commitment. Do not invent urgency, scarcity, meeting dates, budget, authority, result, quote, attachment, link, concession, or guarantee. If a date, owner, or fact needs confirmation, ask or offer choices rather than assert it. Make opting out, pausing, or choosing no next step easy. Provide subject options, email draft, fact-and-commitment ledger, missing-material warnings, and final send checks.
기본적으로 비공개프롬프트 구성은 브라우저에서 로컬로 이루어집니다. 조직에서 허용하지 않는 한 기밀 정보를 AI 서비스에 입력하지 마세요.
입력에서 결과까지
적용 예시
구체적인 맥락이 이 레시피를 바로 사용할 수 있는 결과로 바꾸는 방법을 확인하세요
실제 입력
Call evidence
Priya: brand projects sometimes wait in review because acceptance authority is unclear; one launch waited two days, while Marco said most reviews move. Teams used; SSO required; hosting unknown. Marco requested security overview. Seller Alex explicitly promised to send it the next day. Priya said a mapping session sounds reasonable but must check IT; asked Alex to email time options. No budget, deadline, or target result confirmed.
Approved follow-up material
To Priya and Marco. Approved security link https://example.com/security. Available 45-minute options: Sep 3 10:00 or Sep 4 14:00 Europe/London. Alex may offer the free mapping review but cannot promise implementation or discounts. No attachment; link only.
Email constraints
Under 180 words, warm and concise. Goal: fulfill security promise and let them choose whether to schedule. Two plain subject lines. No artificial urgency; if neither time works, invite alternatives or pause. Internal CRM link must not appear.
예시 출력
Subject options
• Security overview and workflow-review options
• Follow-up: Teams, SSO, and review ownership
Hi Priya and Marco,
Thank you for walking us through the brand-project review process. I noted that acceptance ownership can sometimes be unclear, including one launch that waited two days, while most reviews do move as expected. You also confirmed that you use Teams, require SSO, and still need to check the hosting requirement.
If a 45-minute mapping review would be useful after you check with IT, I can offer:
• 3 September at 10:00 Europe/London
• 4 September at 14:00 Europe/London
We would map one handoff and identify the open fit questions; it would not commit you to implementation. If neither time works, feel free to suggest another, ask for information by email, or pause here.
Best,
Alex
Ledger: workflow issue includes Priya's example and Marco's limiting statement; Teams, SSO, hosting unknown, and security request are confirmed. Only Alex's security-send action was an explicit commitment. The mapping session remains optional; no budget, result, deadline, attachment, or implementation promise is added.
효과가 있는 이유
1
A commitment ledger prevents a friendly recap from quietly creating obligations.
2
Customer-language personalization is relevant without relying on invasive research.
결과 확인
Can every personalized point and commitment be traced to the call?
Are requested materials real, approved, and actually attached or linked?
Does the email preserve a genuine pause or no-next-step option?
안심하고 사용하세요
자주 묻는 질문
이 레시피를 언제 사용해야 하는지, 무엇을 제공해야 하는지, 그리고 어떤 부분에서 사람의 검토가 여전히 중요한지에 대한 실용적인 답변
What should I prepare before using “Write a personalized post-sales-call follow-up email”?
For “Write a personalized post-sales-call follow-up email,” prepare Call evidence, Approved follow-up material, and Email constraints. Replace placeholders only with information you can verify. If a detail is unknown, preserve that uncertainty explicitly instead of asking the model to infer it.
When is the “Write a personalized post-sales-call follow-up email” result not ready to use?
The result is not ready if it does not yet deliver the stated outcome—A concise follow-up email with verified recap, resources, ownership, dates, choices, and confirmation flags—from the supplied evidence, or if it relies on unresolved assumptions, missing approvals, or invented details. Use the checks as release gates: revise the source inputs or assign a named, authorized reviewer instead of polishing an unsupported output.
Which AI tools have recorded tests for “Write a personalized post-sales-call follow-up email”?
The published test record for “Write a personalized post-sales-call follow-up email” lists ChatGPT as of 2026-08-28. This confirms recorded runs, not guaranteed compatibility or identical results in later product versions. For another tool or version, keep every constraint visible and repeat the result checks before use.
ChatGPT
