Essential HR Tech Glossary: CRM, ATS, and Automation Terms

The fastest way to wreck a Keap CRM™ implementation is to build automation before your team agrees on what basic terms mean. ATS and CRM are not synonyms. Tags and segments are not the same operation. A trigger is not a workflow. These distinctions determine whether your automation stack compounds value over time or collapses under its own inconsistency. This glossary defines every core term HR professionals and recruiters need before touching a pipeline — and links each concept back to the Keap CRM implementation checklist for recruiters where the architecture decisions happen.

Applicant Tracking System (ATS)

An Applicant Tracking System (ATS) is software designed to manage active job applications against open requisitions — from submission through hire decision. It is reactive by design: it organizes people who have already raised their hand.

Core ATS functions include resume parsing, initial screening workflows, interview scheduling coordination, compliance documentation, and offer management. For high-volume hiring environments, an ATS is non-negotiable. SHRM research consistently identifies time-to-fill as one of the top metrics HR leaders are accountable for — and an ATS is the primary operational tool for compressing it on active openings.

What an ATS does not do: nurture passive candidates, maintain long-term relationship history, or trigger proactive outreach based on engagement signals. That is the CRM’s job. The strategic play is running both systems in integration — ATS handles active pipeline, CRM handles everything else. See the full breakdown of that integration in the guide to Keap CRM ATS integration for recruitment workflows.

Key Characteristics

• Requisition-centric: organized around open jobs, not candidate relationships
• Compliance-forward: tracks EEO data, disposition codes, and audit trails
• Reactive: only manages candidates who have submitted applications
• Workflow-driven: structured around hiring stages tied to specific job postings
• Integration point: connects to job boards, background check providers, and HRIS systems

Common Misconception

Many recruiting teams believe that storing a candidate in their ATS means they have a relationship with that candidate. They do not. A record in an ATS is a filing artifact. A relationship requires ongoing communication, engagement signals, and maintained context — which lives in the CRM.

Candidate Relationship Management (CRM)

Candidate Relationship Management (CRM) is both a strategy and a software category focused on building and maintaining relationships with candidates across the entire talent lifecycle — including those who have never applied to a specific role.

Where an ATS is reactive, a CRM is proactive. It stores communication history, engagement patterns, skills data, sourcing origin, and pipeline status for every contact in your talent network — regardless of whether they have an active application. Keap CRM™ applies this architecture to recruiting by centralizing candidate records, automating nurture sequences, and surfacing the right contacts at the right moment based on tags, custom fields, and trigger logic.

McKinsey Global Institute research on automation’s productivity impact underscores why this matters: knowledge workers — including recruiters — spend a disproportionate share of time on low-value communication tasks that automation handles at a fraction of the cost and with better consistency. A CRM with automation built in eliminates the manual follow-up burden that causes passive candidate relationships to decay.

Key Characteristics

• Candidate-centric: organized around people, not job postings
• Proactive: maintains relationships regardless of active application status
• Automation-ready: triggers nurture sequences, stage changes, and task assignments automatically
• Engagement-aware: tracks email opens, form fills, and communication history
• Pipeline-building: converts passive contacts into recruitable talent over time

CRM vs. ATS at a Glance

Automation Trigger

An automation trigger is a defined condition that causes a workflow to execute without manual intervention. Triggers are the decision points that separate a living recruitment system from a static database.

In Keap CRM™, triggers fire based on events: a lead form submission, a tag being applied, a pipeline stage moving, a scheduled date arriving, or a contact’s field value changing. Every sequence begins with a trigger. Without correct trigger logic, automations either fail to fire or fire at the wrong moment — producing duplicate emails, missed follow-ups, or misfired offer communications.

Gartner research on HR technology adoption identifies trigger design as one of the highest-leverage configuration decisions in any automation implementation. Getting it right requires mapping the exact condition, timing, and contact state before building the sequence. This is precisely why the Keap CRM implementation checklist for recruiters prioritizes trigger architecture before any workflow is activated.

Common Trigger Types in Recruiting

• Form submission trigger: candidate fills out a sourcing form → applies a tag and enrolls in nurture sequence
• Stage change trigger: pipeline card moves to “Offer Extended” → fires offer communication and compliance task
• Tag applied trigger: “Silver Medalist” tag added → enrolls contact in passive nurture campaign
• Date-based trigger: 30 days since last contact → assigns recruiter follow-up task
• Field value trigger: custom field “Availability” changes to “Open to Roles” → alerts assigned recruiter

Tags and Segmentation

Tags are labels applied to individual contact records in a CRM. Segmentation is the act of grouping contacts by those labels to target communication. They are related but distinct operations — and conflating them produces sloppy automation.

In Keap CRM™, tags serve as the primary routing mechanism. A contact’s tag profile determines which sequences they enter, which emails they receive, and which triggers fire against their record. A well-designed tagging taxonomy — built before any automation is activated — is one of the highest-leverage decisions in a Keap CRM™ implementation. A poorly designed one produces duplicate sends, contradictory sequences, and contact records that become impossible to interpret.

The full operational guide to building this correctly is covered in the satellite on Keap CRM tagging and segmentation for recruiters. For the custom fields that feed segmentation logic, see the guide to Keap CRM custom fields for HR data tracking.

Tagging Best Practices

• Use a consistent naming convention across all tags (e.g., Status::ActiveCandidate, Source::LinkedIn)
• Never use tags to store information that belongs in a custom field (e.g., salary expectations)
• Audit tags quarterly — unused tags create noise that degrades segmentation accuracy
• Document every tag’s purpose and the trigger it is connected to before creating it

Talent Pipeline

A talent pipeline is a structured, stage-based sequence of pre-qualified candidates being actively nurtured toward future roles. It is not a contact list. The distinction is operational: a pipeline implies defined stages, active progression logic, scheduled engagement, and assigned ownership for each contact.

Building a talent pipeline in Keap CRM™ means mapping stage definitions, configuring the triggers that move contacts between stages, designing the nurture sequences that maintain engagement at each stage, and establishing re-engagement criteria for contacts who go cold. Asana’s Anatomy of Work research found that workers spend a significant portion of their week on repetitive coordination tasks — talent pipeline management, when not automated, is exactly this type of work.

The full operational guide to this process is the satellite on automating your talent pipeline in Keap CRM.

Pipeline vs. Candidate Pool

• Candidate pool: a stored collection of contacts with no defined stage logic or engagement cadence
• Talent pipeline: a structured sequence with stage definitions, triggers, nurture sequences, and owner assignments
• A pool becomes a pipeline only when automation governs movement through it

Candidate Experience

Candidate experience is the sum of every interaction a job seeker has with your organization — from first awareness through hire decision or rejection. It is a measurable business metric, not a soft concept.

Harvard Business Review and SHRM research both link candidate experience directly to offer acceptance rates, referral volume from silver medalists, and long-term employer brand equity. A candidate who receives timely, personalized, and transparent communication is statistically more likely to accept an offer, refer colleagues, and re-engage in future hiring cycles — even if they were rejected for the current role.

Automation improves candidate experience by guaranteeing that no contact goes silent. Every stage change in a Keap CRM™ pipeline can trigger a communication that acknowledges where the candidate stands. The Forbes composite on unfilled position cost — citing significant average costs per day a role stays open — makes the business case for offer acceptance rate improvement concrete: a candidate who accepts on first offer rather than declining due to poor communication experience eliminates days of additional pipeline cost.

Automation Touchpoints That Directly Impact Candidate Experience

• Application confirmation within minutes of form submission
• Stage-change notifications when a candidate moves forward or is placed on hold
• Interview confirmation and pre-interview preparation sequences
• Post-interview follow-up within 24 hours
• Silver medalist nurture sequences for candidates not selected for the current role

Recruitment Workflow

A recruitment workflow is the defined sequence of steps that moves a candidate from initial sourcing through hire — or through an informed rejection that preserves the relationship. Workflow design determines how automation is configured: every step that can be systematized should be, so recruiter attention concentrates on the judgment-intensive steps that cannot.

In Keap CRM™, recruitment workflows are built from pipeline stages, triggers, task assignments, and email sequences operating in coordinated sequence. When a workflow is fully configured, a recruiter’s daily task list is generated by the system rather than memory — producing fewer dropped candidates and more consistent candidate experiences across the team.

What a Workflow Replaces

• Manual calendar coordination for interview scheduling
• Spreadsheet-based candidate status tracking
• Ad-hoc email drafts for stage communications
• Memory-dependent follow-up reminders
• Duplicated data entry between ATS and CRM

Pipeline Stage

A pipeline stage in Keap CRM™ is a discrete position in a visual candidate pipeline representing exactly where a contact is in the recruitment process. Stages are not labels — they are operational states that trigger behavior.

When a contact’s stage changes, Keap CRM™ can automatically fire email sequences, apply or remove tags, assign tasks, update custom fields, and notify the assigned recruiter. This means stage architecture is not a cosmetic decision — it is a trigger map. Every stage boundary is a decision point about what automation fires next.

Example Stage Sequence for Recruiting

1. Sourced
2. Initial Outreach Sent
3. Engaged / Responded
4. Screened
5. Submitted to Client
6. Interview Scheduled
7. Offer Extended
8. Placed / Closed
9. Silver Medalist — Active Nurture

Custom Fields

Custom fields are data fields added to contact records beyond a CRM’s default schema, allowing teams to capture information specific to their workflow. In Keap CRM™, custom fields are the foundation of segmentation, trigger logic, and reporting accuracy.

For recruiting, custom fields store data points like preferred work arrangement, compensation expectations, years of experience, skill certifications, last placement date, and availability status. A custom field’s value can trigger automations, filter contact lists, and populate dynamic email content. Inconsistent custom field naming across import batches is one of the primary causes of data hygiene failures — which is why field standardization must happen before any data import. The full guide is in the satellite on Keap CRM custom fields for HR data tracking.

Data Hygiene

Data hygiene is the ongoing operational discipline of ensuring contact records are accurate, complete, deduplicated, and consistently formatted. It is not a setup task — it is a permanent system maintenance function.

The MarTech-documented 1-10-100 rule, attributed to Labovitz and Chang, establishes the cost gradient: preventing a data error costs a fraction of correcting it after entry, and a fraction of what it costs after the error propagates into downstream records and automations. The Parseur Manual Data Entry Report found that manual data entry produces error rates that may appear small in percentage terms but carry outsized consequences in recruiting — where a single malformed compensation field can produce an incorrect offer letter, a compliance gap, or a candidate experience failure.

Data hygiene protocols should include: deduplication reviews on a defined schedule, import field mapping validation before every batch, required-field enforcement at the CRM configuration level, and a documented record-retirement policy for stale contacts. The complete operational guide is the satellite on CRM data clean-up strategy.

Lead Scoring

Lead scoring assigns a numeric value to contact records based on predefined criteria — skills match, engagement frequency, seniority, responsiveness, or sourcing channel. Higher scores indicate higher-priority candidates for recruiter outreach.

In Keap CRM™, lead scoring can trigger escalation sequences automatically when a threshold score is reached — moving a contact from passive nurture into active recruiter engagement without manual review. This concentrates recruiter attention on the contacts most likely to convert while ensuring lower-priority contacts remain in nurture rather than being forgotten.

Scoring Criteria Examples for Recruiting

• Opened 3+ emails in the last 30 days: +10 points
• Clicked a job alert link: +15 points
• Submitted availability update form: +25 points
• No activity in 90 days: -20 points
• Skills match to active requisition: +30 points

Employer Brand

Employer brand is an organization’s reputation as a place to work — shaped by candidate experience, employee referrals, glassdoor-equivalent reviews, and the quality of communication throughout the hiring process. It is not a marketing asset managed by a separate team. It is an operational output of how recruiting workflows are designed and executed.

Every automated touchpoint in a CRM — every timely stage notification, every personalized follow-up, every respectful rejection with a silver-medalist nurture sequence — contributes to employer brand. Harvard Business Review research on employer brand equity links it directly to candidate quality and offer acceptance rates. Automation is the mechanism that makes employer brand consistent at scale.

Onboarding Automation

Onboarding automation refers to the use of CRM workflows to manage and systematize the post-hire experience — from offer acceptance through the first 90 days of employment. In Keap CRM™, onboarding sequences can fire document distribution, compliance checklists, welcome communications, manager task assignments, and 30/60/90-day check-in sequences automatically upon a pipeline stage change to “Placed” or “Hired.”

Gartner research on employee retention identifies the first 90 days as the highest-risk period for new hire departure. Automated onboarding sequences reduce that risk by ensuring no new hire falls through a communication gap during the transition from candidate to employee. The full guide is the satellite on building onboarding workflows with Keap CRM automation.

Related Terms Quick Reference

Build the Vocabulary Before the System

Every term in this glossary represents a configuration decision in Keap CRM™. ATS versus CRM determines what you track and where. Trigger design determines what fires and when. Tag taxonomy determines whether segmentation is precise or chaotic. Data hygiene determines whether every automation that depends on clean records produces reliable output.

None of these decisions happen inside the software. They happen before implementation begins — which is exactly what the Keap CRM implementation checklist for recruiters is designed to enforce. Once vocabulary is shared and architecture is mapped, automation compounds. Without that foundation, it collapses.

To measure whether the system is working after it is built, see the guide to tracking recruitment ROI with Keap CRM analytics. For the candidate-facing application of these concepts, see the satellite on Keap CRM automation for candidate nurturing.