Six recruiting replies for receipt, availability, missing information, status, rescheduling and candidate questions. Use only confirmed process details.
Saved shortcut;application
Space
→
Your reusable reply
Hello [name],
Thank you for your interest in [role]. We have received your application. The next step in the process is [verified process information].
Best regards,
Replace the example details before use.
Illustrated workflow. Create real fields in the visual editor for the details that change.
These are plain-text examples. Replace bracketed labels yourself, or add real fields with PhraseShelf’s visual editor. They are not executable template syntax.
01;application
Acknowledge an application
Confirm receipt without promising a selection outcome.
Hello [name],
Thank you for your interest in [role]. We have received your application. The next step in the process is [verified process information].
Best regards,
[your name]
Use only approved, current process details. Do not imply an interview is guaranteed.
02;availability
Ask about availability
Collect suitable times before arranging an interview.
Hello [name],
Would you be available to discuss [role] during [proposed period]? Please share a few suitable times and your time zone. We will confirm the details separately.
[your name]
Replace the period and confirm who will arrange the meeting. This does not create a calendar event.
03;candidate-detail
Request a missing detail
Ask for one relevant item needed at the current stage.
Hello [name],
To continue with the current stage for [role], could you share [specific relevant item]? Please use [approved sharing method].
Thank you,
[your name]
Check that the request is necessary and permitted. Avoid asking for sensitive documents in an insecure channel.
04;hiring-update
Give a process update
Communicate the actual stage without speculating.
Hello [name],
A brief update regarding [role]: [verified current stage]. We will share confirmed next steps when available. Thank you for your time and interest.
[your name]
Replace the stage with a checked fact. Include a date only when the responsible person has confirmed it.
05;reschedule
Propose rescheduling
Replace a proposed time with clear options.
Hello [name],
We need to revisit the proposed time for our conversation about [role]. Would [option one] or [option two], in [time zone], work for you?
We will confirm the final details separately.
Check both options with the participants first. Do not imply that this message updates a calendar.
06;candidate-answer
Answer a candidate’s process question
Distinguish confirmed information from pending decisions.
Hello [name],
Thank you for asking about [process question]. The confirmed information is [verified detail]. We are still checking [open point] and will share it once confirmed.
Thank you for your patience.
Remove the pending sentence if nothing is open. Do not imply an offer or selection outcome.
Write for the person, not just the process
Candidates need clear information and an accurate next step. Personalize the role and stage, use respectful language, and keep any request relevant to the process.
These examples do not make employment promises, guarantee interviews, or define hiring policy. Review your organization’s approved wording and applicable requirements before use.
Keep candidate data out of reusable defaults
Store the general structure, not a candidate’s private history. Fill in changing details at use time and avoid collecting sensitive information by ordinary email. Remember that a website can read inserted text.
PhraseShelf is an individual writing library. It is not an applicant-tracking system and does not schedule interviews, evaluate people, or send replies for you.
Save an example as your own reply
Copy an example, choose New snippet, give it a title and enter its suggested alias in Shortcuts and aliases. Paste into Plain text, edit the details, then choose Save snippet. Test it in Help & practice with the alias followed by Space.
For changing details, replace each bracketed label with a real field in the visual editor. Keep punctuation in the adjacent text segments. Preview a short and a long answer, then review the final message before using it. Choose a different alias if the suggestion already exists in your library.