# Applicant tracking system high volume features: what to test before you buy

> How to choose an applicant tracking system high volume hiring won't outgrow: features to test, 12 vendor questions, a trial plan, and pricing traps.

Source: https://deephire.com/blog/applicant-tracking-system-high-volume
Last checked against the product: 2026-11-18

## Key takeaways

- Judge an ATS on what it does in bulk: knockout questions, bulk messaging, bulk status changes, and self-scheduling.
- Apply to your own test job on a phone during every demo, and time it.
- Run a two-week trial on two real requisitions, with real recruiters and at least one hiring manager, before you sign.
- Ask how pricing changes when applicant volume spikes, because per-applicant and per-job models can surprise you in peak season.
- Plan the screening step separately, since an ATS tracks candidates well but usually cannot tell you how they communicate.

An applicant tracking system for high volume hiring has to move hundreds of applicants through a stage without a recruiter opening each profile. Before you buy one, check that it has a short mobile application, knockout questions, bulk actions, text messaging, self-scheduling, and reporting by location, then test each of those on a real requisition. Below you'll find a feature table to use in demos, questions to send vendors, a two-week trial plan, and the red flags that tend to surface only after go-live.

## What makes an ATS work for high volume hiring?

Most applicant tracking systems were built for a recruiter who reads every resume. That works when a req gets thirty applicants. It breaks down when a distribution center opens a seasonal req and applications arrive faster than anyone can read them.

At volume, the system has to apply your rules for you. It should reject the candidate who cannot work weekends and text the qualified one a link to book an interview. When someone misses that interview, the system should send the reminder too. Your recruiters then spend less time processing candidates and more time on the exceptions, like the person who answered one knockout question oddly or the strong applicant who applied to the wrong location.

So judge an ATS less on how a single candidate profile looks and more on what happens when you select two hundred candidates and click one button.

## Which ATS features matter most at volume?

Use this table during demos. The third column matters most, because a feature that looks fine on a slide can take far more clicks than you expect once you try it yourself.

| Feature | Why it matters at volume | How to test it in a demo |
|---|---|---|
| Mobile application | Hourly applicants often apply from a phone, sometimes on a break | Apply to a test job on your own phone and time it |
| Knockout questions | Filters out people who cannot meet hard requirements, like a required shift or a license | Build three knockouts, then submit an application that fails one |
| Bulk actions | Lets you reject or message a whole group at once | Ask the rep to reject 100 test candidates with a personalized message |
| Two-way text messaging | Many hourly candidates check texts more often than email | Send a text from the ATS and reply to it from your phone |
| Self-scheduling | Removes the back-and-forth of booking interviews | Book a slot from your phone, then reschedule it |
| Multi-location requisitions | One posting can feed several sites without duplicate work | Post one job for three locations and check where applicants land |
| Duplicate detection | The same person often applies to several stores | Apply twice with a slightly different email and see what happens |
| Location and source reporting | Shows which sites and job boards actually produce hires | Ask for a funnel report by location without exporting to a spreadsheet |
| Hiring manager access | Store and shift managers need a limited, simple view | Log in as a manager and try to review and advance a candidate |
| API and integrations | Connects your screening and onboarding tools | Ask to see the actual API documentation |

If the application step is where you lose people, run your current form through a [mobile friendly job application checklist](https://deephire.com/blog/mobile-friendly-job-application-checklist) before you blame the ATS. Some of the fixes are in your questions, not the software.

## Where an applicant tracking system falls short at volume

An ATS knows who applied and what they answered. It does not know whether the candidate can explain a forklift safety check to a customer or show up for a call on time. For many high volume teams, that screening step is where recruiter hours go, often to phone screens that get rescheduled more than once.

A common fix is to pair the ATS with a one-way video interview tool. DeepHire, for example, sends candidates one link to record answers to three to five questions in the browser on a phone or laptop, with nothing to download. It sends two automatic reminders. Recruiters can review at up to 2x speed, and results can go out through CSV export or a REST API. Whatever tool you use, check that screening results can get back into the ATS without someone retyping them.

Also plan for what happens after a candidate passes screening. Background checks usually come first, then the offer letter and the I-9 and onboarding paperwork. Some ATS platforms handle these natively and others rely on partners. Ask which, and who supports it when it breaks. For how the pieces fit into a recruiter's day, see this [high volume recruiter workflow](https://deephire.com/blog/high-volume-recruiter-workflow).

## Questions to ask ATS vendors before you buy

Send these in writing so you can compare the answers side by side.

1. How many clicks does it take to reject 200 candidates with a personalized message?
2. Can knockout questions auto-reject and auto-advance candidates, and can candidates see why?
3. Does text messaging cost extra, and is there a per-message charge?
4. How do you handle one candidate who applies to five locations?
5. What does a hiring manager see, and can we limit them to their own location?
6. Can candidates self-schedule into a calendar that several managers share?
7. What reports can a recruiter build without help from your support team?
8. What does your API let us read and write, and are there rate limits?
9. How do you import our existing candidate data, and who cleans it?
10. What happens to pricing in a month when applications triple?
11. How long does implementation usually take for a team our size, and what do we have to do?
12. Can we talk to a current customer who hires hourly staff at several locations?

On question 9, a migration is the best chance you will get to clean up old records. Read up on [candidate database hygiene](https://deephire.com/blog/candidate-database-hygiene) before you hand over an export full of duplicates.

## How to run a two-week trial with real requisitions

A demo shows the vendor's best path through the product. A trial shows you what your team will deal with every day. Ask your top two vendors for a sandbox or a paid pilot.

### Pick two live roles

Choose one high volume hourly role and one role that needs more judgment, like a shift lead. Use your real job descriptions and real knockout questions.

### Write down your baseline

Before the trial, note how long it takes today to post a job, screen a batch of applicants, book interviews, and send rejections. Without those numbers, it is hard to tell whether a new tool is actually faster or just feels that way.

### Apply as a candidate

Have three people apply on different phones, including an older Android device. Watch for any field they have to fill in twice, and check whether a confirmation text arrives.

### Put a hiring manager in it

Give a store or site manager a login and no training beyond a one-page guide. If they cannot review and advance a candidate on their own, adoption will stall.

### Score each vendor the same way

Score each area from 1 to 5 and weight it to match your priorities.

| Area | Weight | Vendor A | Vendor B |
|---|---|---|---|
| Candidate mobile experience | High | | |
| Bulk actions and automation | High | | |
| Hiring manager ease of use | High | | |
| Reporting by location and source | Medium | | |
| Integrations and API | Medium | | |
| Implementation and support | Medium | | |
| Total cost at peak volume | High | | |

## Red flags that show up after go-live

These are easy to miss in a demo and expensive to discover later.

- Bulk actions exist but cap out at a small number of candidates per batch.
- Text messaging is a paid add-on billed per message, so costs jump in peak season.
- Only vendor support can set up automation rules, so your team has to file a ticket for every change.
- Basic questions can only be answered by exporting a report to a spreadsheet.
- The application works on a phone but asks for a resume upload first.
- Hiring managers need a full paid seat just to view candidates.
- The API is read-only, so your screening tool cannot update candidate status.
- The reference customers all hire a few salaried people a month and have never run hourly hiring at volume.

## How do ATS pricing models compare for high volume teams?

The pricing structure matters as much as the price, because high volume hiring is seasonal and spiky.

| Pricing model | How it works | What to watch for |
|---|---|---|
| Per recruiter seat | You pay for each user | Hiring manager seats can quietly double the bill |
| Per active job | You pay for each open requisition | Multi-location postings may count as several jobs |
| Per applicant or per hire | Cost scales with volume | Peak months can blow the budget |
| Flat platform license | One annual fee, often tiered by company size | Texting, scheduling, and API access may be sold as add-ons |

Ask every vendor to quote the same scenario. Give them your number of recruiters, managers, locations, and open roles in your busiest month. Then ask what that quote leaves out.

## What to measure in the first 90 days

Track a few numbers from the start so you can tell whether the switch worked: application completion rate, time from application to first contact, time to hire by location, interview no-show rate, and recruiter hours spent on screening. If completion drops after launch, the new form is probably too long. This guide on how to [measure and raise application completion rate](https://deephire.com/blog/application-completion-rate-raise) walks through the usual fixes.

Compare each number to the baseline you wrote down during the trial, and share the results with the hiring managers who use the system. They are often the first to notice which automation rules are rejecting good people.

## Frequently asked questions

### What is the best ATS for hourly hiring?

The best ATS for hourly hiring is one your candidates can finish on a phone in a few minutes and your managers can use without training. Prioritize knockout questions, text messaging, self-scheduling, and bulk actions, then test them on a real requisition before you buy.

### Do small recruiting teams need a high volume ATS?

If a small team handles hundreds of applicants a month, yes, because automation matters more when there are fewer people to read profiles. If you fill a few roles a month, a simpler ATS is usually enough.

### Can an applicant tracking system replace phone screens?

Not on its own. An ATS can filter on knockout answers, but it cannot tell you how a candidate communicates. Many high volume teams add a one-way video interview step that feeds results back into the ATS.

### How long does it take to switch to a new ATS?

It depends mostly on how much data you migrate and how many integrations and locations you need to set up. Ask each vendor for a written implementation plan that lists your team's tasks, and try not to go live right before your busiest hiring season.
