Close the loop with applicants who missed out
Every Monday, WebRun opens SEEK, finds the job ads where a hire has been made or the role closed, lists the applicants still sitting without an outcome, drafts a short courteous update for each one, records the ad and applicant counts in Notion, and posts the approval queue to Microsoft Teams for the recruiter to release.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I make sure every unsuccessful applicant hears back after a role closes?
WebRun checks SEEK every Monday for job ads where the role has closed and finds the applicants still left without an outcome. It drafts a short courteous update for each, worded differently for those who interviewed, logs the counts in Notion, and posts the approval queue to Microsoft Teams for the recruiter to release.
- No applicant is left guessing once a role is decided
- Interviewed candidates get different wording from those never progressed
- Response time to applicants is on record every week
Built for recruiters · talent acquisition teams · hiring managers · HR teams · recruitment agencies
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
www.seek.com.auin a real browser with your saved login - no setup, no API keys. -
1
SEEK - draft an update for every applicant left waiting
seek.com.au
WebRun opens SEEK to draft an update for every applicant left waiting. - Open SEEK and list the job ads where the role has been filled or closed
- For each ad, capture the applicants whose status is still unset or left at applied
- Separate those never progressed from those interviewed, since the two deserve different wording
- Draft a short, warm update per applicant that names the role and thanks them for applying
- Leave every message unsent inside SEEK. WebRun never messages an applicant on its own
Done when Every applicant left without an outcome has a drafted update waiting for approval.
-
2
Notion - log the ads and applicant counts
notion.so How to Automate Notion
WebRun opens Notion to log the ads and applicant counts. - Update your hiring page in Notion with one row per closed ad
- Record total applicants, how many were told an outcome, and how many are still waiting
- Note how many days have passed since each ad closed, so a slow loop is visible
- Keep the history so response time to applicants can be read across the quarter
Done when Every closed ad has its applicant response position recorded in Notion.
-
3
Microsoft Teams - post the approval queue
microsoft.com How to Automate Microsoft Teams
WebRun opens Microsoft Teams to post the approval queue. - Post the approval queue to your recruitment channel
- Show each ad, how many drafts are waiting, and the days since the role closed
- Link straight to the drafts so the recruiter can read and release them in one sitting
- Name the ads where applicants have waited longest so those go out first
Done when The recruiter has this week's approval queue in Teams.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it message applicants without me?
No. Every update is left as an unsent draft in SEEK for the recruiter to read and release. A rejection is a moment that shapes how someone sees your company, so a person always approves it.
Does it write the same message to everyone?
No. Applicants never progressed and applicants who interviewed get different wording, and each draft names the role they applied for. You can set the tone once and WebRun matches it.
What if a role is still open?
It is skipped entirely. Only ads where a hire has been made or the role has closed are picked up, so nobody is told no while they are still in the running.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.