AI can help candidates get a clear answer without turning rejection into a template.

Use the decision that was actually made.

The fastest way to damage candidate trust is to send a generic email after a specific process.

It is also risky to send a personalised email that states a reason nobody approved.

Start from the recorded outcome and the policy for that stage. Strawberry can prepare a clear draft based on those sources. The recruiter decides whether the wording is right for the person and situation.

Match the message to the time the candidate invested.

Someone declined after an application needs a different note from someone who completed three interviews or a practical task. The point is not to manufacture warmth; it is to acknowledge the process accurately.

Strawberry can apply stage-specific guidance. The drafts can mention the right level of detail, next step, or feedback policy without exposing internal deliberations.

Keep promises and permissions out of the guesswork.

Do not promise to keep a person in mind or retain their details unless the team has chosen that policy. Do not promise detailed feedback or to reopen a process unless the team has chosen that policy. These small phrases carry real expectations.

Use a reusable skill that reflects the organisation’s language on data retention, feedback, talent pools, and reapplication. Strawberry can then prepare consistent drafts without turning every candidate into a legal edge case.

Make the queue shorter without making the process colder.

The operational win is a smaller backlog.

Every decided candidate has a prepared message. Every exception is visible, and no one is left waiting because a recruiter ran out of time.

A routine can prepare a daily rejection queue from records already marked as decided. The recruiter should still review the wording and approve the external send. That matters particularly for late-stage, sensitive, or disputed processes.

Frequently asked questions