Skip to content

AI Agents

The virtual workers inside Array HQ — what each one does in //Recruiting and //Ops, and how they respect your account's access controls.

The operational problem

The work that runs a frontline operation never stops. Recruiters configure screening for every new job, text applicants, schedule interviews, and track who advanced. Operators watch goal success rates, scan site metrics, and follow up on who is falling behind — often across spreadsheets and lagging reports. Humans do this work in fragments between everything else. The work gets done late, gets done inconsistently, or doesn't get done at all.

How Array HQ solves it

Array HQ has two product agents — //Recruiting and //Ops — each a virtual worker scoped to that area of the platform. They take repetitive work off the human queue, respect your account's access controls, and write results into the same system your team uses — so the audit trail and the handoff stay clean.

AI isn't just bolted onto the side of a point & click application. Array HQ agents take on assignments and complete measurable work for you.

How it works

What an agent looks like

Agents are not a separate system you configure from scratch. They are built into //Recruiting and //Ops and work the way those products work:

  • A clear purpose. Each agent handles a defined set of assignments in its product area.
  • Your account's access controls. An agent can only see and act on the organizations and data your role and permissions allow — the same boundaries that apply to the person using it.
  • A handoff point. Where a human reviews, confirms, or picks up the result before it goes live.

//Recruiting agent

The virtual worker for your hiring team. It runs inside the //Recruiting workspace as a conversational assistant — you tell it what you need, and it carries out recruiting assignments:

  • Jobs — import or create job records from a description or your existing job orders.
  • Screening — set up screening questions for a job; once active, the agent texts applicants via SMS in the background, evaluates their replies, and writes results back to the candidate record.
  • Candidates — move applicants through the pipeline, disposition hires and rejections, and send candidate notifications.
  • Interviews — when a recruiter invites a candidate to interview, the agent arranges it in the background and sends calendar links via text.
  • Advertising — post jobs to external boards, manage spend, and pause or cancel postings.

Recruiters interact with the agent through conversational chat in the //Recruiting workspace to manage their pipeline of candidates. Screening, interview scheduling, and other assignments continue in the background.

//Ops agent

The virtual worker for your operations team. It runs inside the //Ops workspace and helps operators stay on top of what is happening on the floor:

  • Goal performance — review how sites, shifts, and roles are tracking against the goals you have configured.
  • Operational metrics — surface site-level signals such as goal success rate, productivity measures, activity, and sales so you can spot issues before they show up in a handful of weekly reports.
  • Employee performance — review how individual team members are performing against goals and operational expectations on the roster.

Operators use the agent to get answers about performance without assembling data from multiple tools. Industry-specific views surface the information you care about when you want to dig in directly.

What you can count on

Array HQ agents are built for operators who need the work done — not a demo of what AI might do someday.

  • Your team stays in charge. Agents handle repetitive assignments in the background. Recruiters and operators make the decisions that matter — who gets hired, what screening goes live, who gets invited to interview.
  • The same access rules apply. An agent can only see and do what the signed-in user is allowed to see and do. There is no separate back door around your account's access controls.
  • The work lives in your system. Agent actions are recorded alongside everything else your team does — same records, same audit trail, nothing hidden in a separate tool.
  • Important steps have a handoff. When something needs a human review before it goes live, the product is designed for that pause — not to skip past your team.

Key terms

Term Meaning
Agent A virtual worker inside Array HQ with a defined purpose in //Recruiting or //Ops.
//Recruiting agent The virtual worker for hiring — jobs, screening, candidates, interviews, and advertising.
//Ops agent The virtual worker for operations — goal performance, operational metrics, and employee performance.
Screening configuration The set of questions and target responses used to screen applicants for a specific job.
Handoff The point where an agent's output reaches a human for review or action.