Close the loop: an ATS workflow that acknowledges, updates and rejects every applicant

Most people who apply for a job still hear nothing. In July 2026 fieldwork across more than 1,000 applicants at 120 employers, 64.6% said they had been ghosted after applying, and 34% had been ignored more than once. Of those who were ghosted, 55.3% then did something that hit the employer: they told other people, decided never to apply again, or stopped buying from that organisation.

That is not a problem a warmer careers-page sentence will fix. It is a missing close in the hiring process. Candidate status updates in an ATS should make acknowledgement, a stage update and a standard rejection the default, so recruiters do not have to write every message by hand.

What silence actually costs

The damage is easy to miss. Only 4.2% of ghosted candidates in that study posted about it online. About a third told friends or family instead, so the cost travels by word of mouth rather than a review you can answer.

A separate July 2026 survey of 1,008 employed US adults found 48% would not apply to the same company again after being ghosted, and 45% had been left without a reply while still in process. Later in July, a US poll of 2,000 job changers found 53% had themselves gone silent on an employer, often between offer and start, while another survey of more than 1,500 people put employer-side ghosting this year at 32%. The shared trigger is slow or inconsistent communication, not a one-sided manners problem.

At the end of July a public site also launched so jobseekers can report interview ghosting. Silence after a conversation is now easier to put on the record. The operational answer is still the same: every application needs a closing step.

Close the loop in the ATS, not in a private inbox

Most teams do not ghost on purpose. Applications sit in a folder, screening piles up, and there is no required action that says “this person has been told”. Sending nothing feels cheaper than sending a rejection. The research says the opposite: a short, standard close costs minutes; no close costs the next referral.

Treat candidate status updates as workflow rules, not as extra writing. Jobli’s guide to [improving recruiter productivity](https://www.jobli.io/news/improve-recruiter-productivity) makes the same point: automate the repetitive close so people keep the conversations that need judgement.

Four closing steps every applicant should receive

1. Acknowledge every application

Send a confirmation as soon as the application is recorded. Say that it has been received, what happens next and when they should expect an update. Honesty starts before apply as well: a mid-July 2026 survey of 1,060 workers found 85% were more likely to apply when the job was described honestly, and 78% were at least somewhat likely to abandon a vague listing. Do not promise a personal reply you cannot keep.

2. Update the stage, then tell the candidate

When the ATS stage changes — screening, interview, hold, offer — send a short status update from the same record. The message can be a template. The trigger should be the stage change, not a recruiter remembering to write. If the decision is still in process, say so and give a realistic next date.

3. Reject as a standard close, not a favour

A rejection should go out when the decision is recorded, including after first screening. Thank them, state that they will not progress, and keep the door open only if that is true. Do not wait for a perfect personal note. A clear no is better than an empty inbox.

4. Keep a person on exceptions

Automation should close the routine path. Failed delivery, a candidate who asks a question, a confidential search or a late change of brief should create a task for a named recruiter. That is also where time-to-hire work connects: Jobli’s guide to [reducing time to hire](https://www.jobli.io/news/reduce-time-to-hire) is about removing delay, not skipping the update.

Measure whether the loop actually closed

Track applications acknowledged, stage updates sent, rejections sent, messages that failed, and applicants still waiting past your service level. Compare roles before changing the whole process. A high volume of applications is not an excuse to skip the close; it is the reason the close has to be a rule.

Jobli can request the next message when a stage changes, show outstanding candidate updates and keep the recruiter in control of exceptions. To see that workflow on your roles, [request a demo](https://www.jobli.io/book-demo).

Candidate status update FAQs