Skip to content
DeepShellDeepShell
People operations · People teams

Draft a rejection email from the application

Use selected browser sources to draft a rejection email from the application. DeepShell assists with draft work; you prepare the inputs, verify the evidence, and complete any external action.

Worked reference guideIllustrative — extension test pendingUpdated 2026-09-06

Before you start

Inputs: Application, role title, an approved rejection decision, approved feedback (if any), and company communication policy.

Define: the audience, date or version, comparison criteria, and intended destination.

Access: open the sources yourself and select only content you are authorised to send to a model provider. Inaccessible or unselected pages are outside the task.

The process, step by step

  1. 1
    You complete

    Prepare application, approved hiring decision, and communication policy. Confirm you can share the selected material with a model provider.

  2. 2
    You complete

    Open the relevant pages or attachments, select the sources in the panel, and set the scope. Log in or navigate to any required pages yourself.

  3. 3
    DeepShell assists

    Prepare an editable draft using only the supplied facts. Request: Subject, Greeting, Decision, Approved feedback, Closing.

  4. 4
    You complete

    Verify recipient, names, facts, tone, and approval before copying or sending.

  5. 5
    You complete

    Review the final text, then copy it into the intended application. You approve and send or publish it yourself.

Requires another tool: sending, publishing, form submission, CRM updates, purchases, and schedules are outside this extension workflow. Use the destination application yourself.

Your reusable workflow pack

Replace bracketed fields before use. Keep the sources and output together for the next reviewer.

Reusable prompt
Task: Draft a rejection email from the application.
Use only these selected sources: Application, approved hiring decision, and communication policy.
Audience: [add the intended reader].
Scope: [add dates, criteria, versions, or exclusions].
Return these fields or sections: Subject, Greeting, Decision, Approved feedback, Closing.
Cite the source and page or section for factual statements. Mark missing information as "Not stated". Separate facts from assumptions. Do not invent figures, decisions, or events.
Finish with unresolved questions and a review checklist. Do not send, submit, purchase, or update another system.
Output template
Subject: [fill from the selected source; otherwise Not stated]
Greeting: [fill from the selected source; otherwise Not stated]
Decision: [fill from the selected source; otherwise Not stated]
Approved feedback: [fill from the selected source; otherwise Not stated]
Closing: [fill from the selected source; otherwise Not stated]

Worked example

Recruitment & HRIllustrative workflow
Example output

Subject / Greeting / Decision / Approved feedback / Closing

  1. 01Subject: Update on your application for [Role]
  2. 02Hi [Candidate name],
  3. 03Thank you for your interest in [Role] and the time you spent applying. After reviewing your application, we will not be progressing it for this role.
  4. 04Thank you again for your interest in [Company]. We wish you well in your search.
  5. 05Best wishes, [Approved sender]
Worked reference example using fictional data or explicit placeholders. This is an illustration, not an extension test result.

Review, then complete the process

  • Confirm an authorised person has already made the decision. Do not ask the assistant to choose whom to reject.
  • Verify recipient, names, facts, tone, and approval before copying or sending.
  • Use approved job-related evidence only. Do not infer protected traits or let this output make the hiring decision.
  • Every material claim has a source you can open and inspect.
  • Missing information is explicitly marked; no placeholders remain in the final deliverable.
  • A named person has approved the result before it is shared or used.

Review the final text, then copy it into the intended application. You approve and send or publish it yourself.

Done means: the intended reviewer can trace the result to its sources, all missing details are resolved or explicitly flagged, and any external action has been completed by an authorised person.

If the result is incomplete

Check source selection and access first. Narrow the question, specify the missing field, or supply an authorised source. For long or scanned documents, verify that the relevant text is readable. If evidence is still missing, record the gap rather than accepting an invented answer.

Time, cost, and validation

No measured run time, cost benchmark, or end-to-end extension test is recorded for this guide. Actual cost depends on source length, model, and retries. Use the settled receipt from a real run; do not treat the example as a performance promise.

Practical questions

What should I prepare?

Application, approved hiring decision, and communication policy. Define the audience, scope, and required fields before you start.

Which steps are automated?

Prepare an editable draft using only the supplied facts. Source selection, review, and any sending, submission, or system update remain your responsibility.

What if the source is incomplete?

Keep missing values marked as Not stated. Add an authorised source or narrow the task; do not ask the model to fill gaps with plausible facts.

Has this workflow been tested in the extension?

This is an illustrative process guide. No end-to-end extension test or measured cost benchmark is recorded for this guide.

Part of: Candidate communication

Structure job information, review evidence, and prepare an approved response. Hiring decisions stay with people.

  1. Turn a job board page into a spreadsheet
  2. Match a CV against a job spec
  3. Draft a rejection email from the application

Continue the work