Emails

The two system messages

• To the applicant — confirms the application arrived.
• To the hiring side — says an application arrived, with a link to it.

Both are ordinary Craft system messages, so edit and translate them under Utilities → System Messages, where every other Craft email lives. Switch either off under Hire → Settings → Notifications.

Who to notify takes addresses one per line or comma-separated. Left empty, it falls back to the system email address, so a fresh install still tells somebody.

On the team notification:

• Reply goes to the applicant — on by default, so hitting reply answers them
• Attach the CV — off by default; the email links to it either way

Stage emails (Pro)

Each stage can send the candidate an email when they are moved to it — so moving somebody to Interview is what sends the invitation. Write the subject and body on the stage. Both are Twig, with these in scope:

Variable
application, job, stage	The elements and the stage
firstName, applicantName, email, phone	The candidate
jobTitle, jobUrl	The job (the title survives the job being deleted)
answers, coverLetter	What they wrote
statusUrl	Their status page, when it is on
organizationName, siteName, cpUrl, submittedAt

Hi {{ firstName }},

Thanks for applying for {{ jobTitle }}. We'd like to talk — reply to this email with a couple
of times that suit you next week.

The same variables work in the two system messages.

Queued by default

Sending inside the request means a slow mail server presents to the applicant as a form that hangs. Send through the queue is on by default, so the applicant gets an answer straight away and the mail goes out on the next queue run. Turn it off only if the site has no queue runner.

If mail failed — wrong SMTP credentials, say — resend both messages for one application:

php craft hire/applications/resend 412