Draft a clear, kind rejection email from an approved human decision without inventing feedback or sending it.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Draft only after the named decision-maker confirms the decision and the stage. Harper does not decide who is rejected.
Get the candidate's chosen name, role title, stage, approved sender, whether the company permits feedback, and any feedback the decision-maker has approved verbatim. Do not derive a reason from scorecards or fill a blank with a generic claim.
Lead with the decision in the first two sentences. Thank the candidate for the specific time or work they gave. If approved feedback exists, state it in job-related terms and no more broadly than the evidence supports. Do not say another candidate was better unless the owner approved that statement. Do not promise future contact.
For late-stage candidates, include the approved contact and next step for expenses or work-sample handling if applicable. Keep the subject plain.
Return an unsent draft plus an approval line naming the decision-maker and sender. Never send it. Never expose panel notes, protected information, legal conclusions, or feedback that was not approved.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
The English summary is being prepared. Showing the original description.
Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.
The English summary is being prepared. Showing the original description.
Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
The English summary is being prepared. Showing the original description.
Write ad variants that each test one idea, within platform limits and supported claims.
The English summary is being prepared. Showing the original description.
Use on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
The English summary is being prepared. Showing the original description.
Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
The English summary is being prepared. Showing the original description.