Tell us about your service
We use this to write every template in your voice. The more specific you are about how your service sounds, the better the emails will feel.
We bake this straight into every email.
If you already have brand or comms guidelines, drop them in. We accept .txt, .docx or .pdf.
Anything you say a lot that you want to hear in these emails.
Which templates do you need?
Pick every touchpoint you want to cover. We generate the whole set in one go so your voice stays consistent across the funnel.
0 of 11 templates selected
Email
Application Acknowledgement
Automatic reply sent the moment a candidate applies, so they know their application was received.
Email
Did Not Make Shortlist
Early, kind regret for candidates not going through to interview.
Email
Interview Invitation
First interview invite, includes options for time, location and who they'll meet.
Email
Interview Confirmation
Sent after the candidate accepts, confirming the details and what to bring.
Email
Meet the Room / Trial Shift
Invitation to a paid trial shift, with practical detail on the room and the day.
Email
Referee Details Request
Ask the candidate for two referees with the right context to be useful.
Email
Regret After Interview
Warmer regret for candidates who put time in and met your team.
Email
Verbal Offer Follow Up
Holding email after a verbal yes, confirming what happens next.
Email
Formal Offer Email
Pay range, hours, start date, WWCC, qualifications and contract timeline.
Email or SMS
Pre Start Holding Note
Keep your new starter warm between contract sign and day one.
Email
Keep On File / Talent Pool
Strong candidate, wrong moment. Keep the door open for next time.
Quick review
Have a last look before we write everything. You can come back and change any field after.
Service details
Service name
-
Service type
-
Role being hired
-
Sign off name
-
Your service voice
-
Templates to generate
Your recruitment comms pack
Click into any template to edit it inline. Use copy, print or save when you're done.
AI generated draft. These templates are a starting point. Read them through, swap any phrasing that does not sound like your service, and check every placeholder before sending.