Write a polite progress follow-up email

작성자: AILesson3 분 소요테스트::ChatGPT검토일: 2026-08-28

빠른 답변

Request a concrete update while acknowledging context and avoiding invented urgency. 제공할 내용: Request history, Current impact, Reply needed. 예상 결과: A concise follow-up with a clear reply request and proportionate escalation.

맥락 추가

텍스트는 이 브라우저에 유지됩니다. AILesson Prompts는 이를 모델이나 서버로 보내지 않습니다.

Request historyCurrent impactReply needed

프롬프트

채워지지 않은 필드는 플레이스홀더로 표시되므로 프롬프트를 복사하고 편집할 수 있습니다

Write a polite progress follow-up email.

Request history and existing commitments:
[history]

Real dependency and impact:
[impact]

Update or decision needed and reply timing:
[ask]

Mention only documented requests and dates. Acknowledge known constraints without inventing excuses. State the dependency factually, ask for a concrete status or realistic revised date, and offer one practical way to unblock the work when supported. Do not use guilt, vague urgency, threats, or passive-aggressive phrasing. Do not imply escalation unless requested. Return a subject line, concise email, a softer alternative sentence for the main ask, and any fact that must be confirmed before sending.

Playground에서 사용해 보기

기본적으로 비공개프롬프트 구성은 브라우저에서 로컬로 이루어집니다. 조직에서 허용하지 않는 한 기밀 정보를 AI 서비스에 입력하지 마세요.

입력에서 결과까지

적용 예시

구체적인 맥락이 이 레시피를 바로 사용할 수 있는 결과로 바꾸는 방법을 확인하세요

실제 입력

Request history: On 3 March I asked Dev for the approved packaging dimensions. Dev replied on 4 March that they expected to send them by 7 March. It is now 10 March and no further update has arrived.
Current impact: The print supplier cannot finalize the dieline until dimensions are confirmed. The supplier has reserved production time but has not stated when that reservation expires.
Reply needed: Ask whether dimensions are ready; if not, request a realistic delivery date. Please reply by noon on 11 March. Offer to review a draft dimension sheet.

예시 출력

Subject: Follow-up on approved packaging dimensions

Hi Dev,

I’m following up on the approved packaging dimensions you expected to send by 7 March. The print supplier needs them before it can finalize the dieline.

Are the dimensions ready to share? If not, could you send a realistic delivery date by noon on 11 March? I’m also happy to review a draft dimension sheet if that would help move it forward.

Thanks, [Sender name]

Softer main ask: “When you have a moment, could you let me know whether the dimensions are ready or what delivery date would be realistic?” Confirm the sender name before sending. The email does not claim the supplier reservation is about to expire because no expiry was provided.

효과가 있는 이유

1
A factual timeline creates accountability without assigning motives.
2
Asking for a realistic revised date produces a usable response when the original date has slipped.

결과 확인

Are all referenced dates and commitments documented?
Can the recipient answer the request in one clear reply?
Does the email avoid blame, invented urgency, and hidden escalation?

안심하고 사용하세요

자주 묻는 질문

이 레시피를 언제 사용해야 하는지, 무엇을 제공해야 하는지, 그리고 어떤 부분에서 사람의 검토가 여전히 중요한지에 대한 실용적인 답변

What should I prepare before using “Write a polite progress follow-up email”?

For “Write a polite progress follow-up email,” prepare Request history, Current impact, and Reply needed. 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 polite progress 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 with a clear reply request and proportionate escalation—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 polite progress follow-up email”?

The published test record for “Write a polite progress 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.

더 많은 탐색 방법