Screening
SMS screening that flags applicant responses for recruiter review. Recruiters make every hiring decision.
The operational problem
Screening at high-volume operations gets handled in one of two unhelpful ways. Either a recruiter spends most of the week reading applications one at a time, or screening is offloaded to a rule that hides half the applicants a recruiter would want to see. Neither produces a working list for the recruiter to review. Recruiters need a fast, consistent read on each applicant without losing visibility into any of them.
How Array HQ solves it
The SMS Screening Agent sends each applicant a short set of screening questions configured by the recruiter. It evaluates responses against the target responses set on each question and surfaces the result as a flag on the applicant record. Every applicant remains visible to the recruiter. Recruiters read the flags and decide.
How it works
Setting up screening
For each job, a recruiter configures screening questions and target responses. The //Recruiting agent drafts an initial question set from the job details to speed up setup. Recruiters can edit, reorder, delete, or add questions from scratch. Recruiters approve the question set before screening goes live.
Running screening
When an applicant applies to a job, the Screening Agent sends the configured questions over SMS. The applicant responds in free-form text. The agent evaluates each response against the target response and records the result.
Screening flags
For each screening question, the applicant record shows the question, the target response the recruiter set, and the applicant's raw response. An overall flag rolls the responses up per applicant: match, borderline, or no-match. The reason behind the flag is visible. No applicant is auto-rejected, hidden, or filtered out based on screening. Recruiters see every applicant.
Consent and opt-out
Applicants can end screening at any time. Standard opt-out keywords are recognized automatically: STOP, STOPALL, UNSUBSCRIBE, CANCEL, END, QUIT, and OPT OUT. Natural-language opt-out (for example, "please don't text me anymore") is also detected. Opted-out applicants receive no further screening messages. The recruiter still sees the applicant and the screening state up to the opt-out point.
Human request and accommodation
Applicants who ask to speak to a human, or who request an accommodation during screening, are flagged on the applicant record for recruiter review. The Screening Agent does not act on those requests directly.
Recruiter workflow
Recruiters open the applicant list for a job. They see every applicant with the screening flag and reason visible. From here, they can advance or reject applicants through chat or the pipeline UI. Every action is audited.
What you'll be able to do
- Set screening questions per job with target responses that reflect your operation.
- Screen high volumes of applicants over SMS without hiding anyone from the recruiter.
- See screening flags on every applicant with the reason behind each flag.
- Have opt-out, human-request, and accommodation requests surfaced automatically for recruiter follow-up.
Key terms
| Term | Meaning |
|---|---|
| SMS Screening Agent | The agent that sends screening questions to applicants over SMS and evaluates responses. |
| Screening question | An SMS question with a recruiter-set target response. |
| Screening flag | The evaluation result surfaced on an applicant record (match, borderline, no-match). |
| Opt-out | An applicant declining further SMS. The applicant remains visible to the recruiter. |