7 Best Intake Form Tools for Recruiting Firms (2026)

TL;DR

• Intake form software for recruiting firms is the layer that captures a candidate or client requisition, enforces required fields, and lands a structured record in the ATS without a coordinator retyping a PDF.

• Greenhouse, Lever, and Ashby win when intake must live inside the ATS; Workable wins for a smaller desk that still wants an ATS-native form; Typeform and Jotform win only as a front door with an explicit write-back; Paradox wins when the “form” is a conversation on SMS or chat.

• US white-collar time-to-fill: 44 days is the clock a missing field actually burns, not a software score.

• US Tech Automations sits above the ATS: it maps the form event, holds incomplete EEO or work-auth packets, and queues a coordinator. It should not be the system of record for the candidate.

What the numbers say

Recruiting intake fails in hours, not in “engagement.” A desk that still pastes resumes into a Google Form while the ATS sits empty is paying recruiter time against a 44-day fill clock. US staffing industry revenue: $186B is the market that still runs on complete applications, not pretty surveys. Use the table as a baseline for a 12–20 recruiter firm, then replace every cell with your own last-quarter counts before you buy.

Time-to-fill and staffing revenue are industry benchmarks from SHRM and Staffing Industry Analysts, not vendor scores. Retention is a legal floor, not software advice.

US white-collar time-to-fill averages 44 days according to SHRM (2024 Talent Acquisition Benchmarks), so a form that sits in email for two business days is not a stationery problem. It is a measurable slice of the fill clock the desk already reports to clients.

Why recruiting operations break at scale

A 4-person boutique can babysit a Typeform and paste winners into Greenhouse. A 14-recruiter firm with 40 open reqs cannot. Volume creates three failure modes that look like “we need a better form tool” and are actually record problems: (1) the candidate submits twice, once on the career site and once on a job-board redirect, (2) the client intake for a new req never reaches the ATS so sourcers work off a Slack thread, (3) EEO, work-authorization, and source fields arrive as optional comments, so the file is not complete when a hiring manager asks for a slate.

Human resources specialists held a large US occupational base with a median annual wage of $67,440 according to the U.S. Bureau of Labor Statistics (Occupational Outlook Handbook). Paying that rate to re-key a PDF is how intake “software” still loses to a coordinator with two monitors.

The legal overlay is not optional. Employers must keep personnel and employment records, including application materials, for 1 year according to the U.S. Equal Employment Opportunity Commission, and federal contractors often keep them longer under OFCCP rules. A Typeform that auto-deletes after 90 days, or a chatbot that never writes the transcript into the ATS, is an operations choice with a retention cost.

Client intake is the twin of candidate intake. A new req that arrives as a forwarded email with a salary range in the signature block will not trigger interview scheduling or a clean pipeline track. The form has to create the job and the candidate, or the rest of the stack is theater.

Duplicate applications are the quiet killer at 1,200 submissions a month. Job-board redirects, employee referrals, and a career-site apply button can create three Greenhouse candidates for one person if the form tool does not pass a stable email-plus-phone key. Coordinators then spend the afternoon merging records instead of scheduling. Native ATS apply usually dedupes on email; Typeform and Jotform do not unless you map the key and refuse the second write.

Source tracking is the other incomplete-file pattern. A form that leaves “source” as a free-text comment will wreck every later report on which board actually produced a send-out. Put source on the 18-field complete list, stamp it from the landing URL or UTM, and do not let a recruiter overwrite it with “LinkedIn” because that is where they first talked. Intake software that cannot preserve source is not intake software; it is a contact form.

The automation blueprint

Do not start by ripping out Greenhouse. Start by naming the system of record, the 18 fields that mean “complete,” and the human who is allowed to create a candidate when the parser is unsure. Then attach one intake event to that rule.

Worked example: a 14-recruiter desk handling 1,200 applications a month with 18 required fields can treat Typeform form_response as the intake event, as documented in Typeform’s webhook reference. When that webhook fires, copy the answers into Greenhouse, stamp the source, and hold the ATS write if work-authorization or EEO packets are blank so a coordinator reviews the 1,200-row exception queue instead of a shared inbox. Those three figures—14 recruiters, 1,200 applications, 18 fields—are the volume that makes a missing field a fill-clock problem, not a survey-design problem.

US Tech Automations can subscribe to that form_response, map the 18 fields, and queue a coordinator task when the ATS write is held; prerequisites are API keys, a field dictionary, and a person who still owns the Greenhouse record. Inspect the same pattern on the recruitment workflow agents.

A Zapier or Make scenario can copy a PDF into a Drive folder. It does not enforce OFCCP-style retention, dedupe against the ATS candidate ID, or stop a write when the requisition is closed. If you only need a file dump, stay on no-code. If you need a complete, owned application record, the blueprint above is the job.

Closed reqs are the other write you must stop. A Typeform that still accepts applications for a job that filled on Tuesday will create Greenhouse candidates a recruiter has to reject by hand. Pass the job status into the form or kill the public link when the ATS job closes. Paradox scripts have the same leak if the conversation does not check req status. Native ATS apply usually dies with the job; standalone forms do not.

Employee referrals need a short, separate path, not the public 18-field apply. A referral form that still asks work-authorization twice will not get used. Keep required legal fields, drop the marketing questions, and stamp source as referral with the employee’s name. Jotform is often enough for that internal door if it still writes to the same ATS candidate object.

After the candidate lands, the next operational leaks are usually interview feedback collection and offer letter routing. Intake that never becomes an ATS application cannot feed either one.

Cost breakdown

Price the form and the ATS as one bill. A $29 Typeform seat that still costs two coordinators 15 hours a week of re-keying is not cheaper than Greenhouse’s native application. Figures below are public list or “contact vendor” as of vendor pages; confirm before a partner meeting. The sketch assumes 8 billed form/ATS seats and 1,200 applications per month.

List prices change. “Contact vendor” means we will not invent a seat fee. Re-key dollars are a labor sketch, not a vendor invoice.

US staffing firms billed on the order of $186B according to Staffing Industry Analysts (2025 forecast for 2024), which is why a $29 form seat is not the decision. The decision is whether the application becomes a billable search file.

Count coordinator hours before you celebrate a cheap form. If two coordinators spend 20 hours a month re-keying, that is 240 hours a year. At a fully loaded $40 hour that is $9,600, which already exceeds Typeform Plus for eight seats. If the ATS you already pay for will enforce the 18 fields, the cheap form is the expensive path. If the ATS apply experience is losing mobile candidates, pay for Typeform as a door and still budget the map.

Do not hide implementation in “we will figure out Zapier.” Greenhouse Harvest permissions, Lever API tokens, and Paradox script reviews are calendar time. A 14-recruiter firm should put 30–90 days on the wall for ATS-native changes and 2–10 days for a form tool that still needs a 3-week mapping if compliance fields are involved. The cost table above is software plus re-key; training and a named owner are extra.

Vendor / stack landscape

The shortlist is seven products. Native ATS intake (Greenhouse, Lever, Ashby, Workable) versus standalone forms (Typeform, Jotform) versus conversational intake (Paradox). Do not add an eighth “AI resume robot” to this table; if it cannot create an ATS application with a stable ID, it is not intake software.

Greenhouse

Best fit: Firms that already live in Greenhouse and whose intake problem is “the application never becomes a complete Greenhouse candidate.” Limitations: Quote-only commercial terms; native apply is an ATS screen, not a conversational form. Implementation: Harvest API mapping, permission roles, and a named coordinator. Primary evidence: Greenhouse Harvest.

Lever

Best fit: Lever shops that will not migrate and need req-plus-candidate intake in one CRM-style ATS. Limitations: Quote-only; client-facing forms are not Lever’s center of gravity. Implementation: Field mapping and a Lever admin. Primary evidence: Lever.

Ashby

Best fit: Teams that want a modern ATS with native forms and analytics in one product. Limitations: Quote-led; still an ATS, not a Typeform replacement for public microsites unless you use Ashby’s apply. Implementation: 21–60 days is a common window if data is clean. Primary evidence: Ashby.

Workable

Best fit: Smaller staffing desks that need ATS-native applications with a public-ish price rung. Limitations: Depth trails Greenhouse on enterprise compliance packages; confirm current list. Implementation: Faster than enterprise ATS programs. Primary evidence: Workable pricing.

Typeform

Best fit: A branded candidate or client form that must still write into an ATS. Limitations: It is not an ATS; without write-back you bought a prettier inbox. Implementation: Hours to a live form, weeks to a reliable Greenhouse map. Primary evidence: Typeform.

Jotform

Best fit: Internal client intake, referral forms, and tables when recruiters already live in Jotform. Limitations: Same write-back job as Typeform; PDF email is not a candidate record. Implementation: Fast for the form, slow for ATS hygiene. Primary evidence: Jotform pricing.

Paradox

Best fit: High-volume lines where the “form” is SMS or chat (Olivia) and must create ATS candidates. Limitations: Quote-only; a bad script creates incomplete files at scale. Implementation: Conversation design plus ATS mapping. Primary evidence: Paradox.

How we evaluated

This is a seven-product shortlist. We scored inspectable checks a recruiting operations lead can audit in a week, not analyst-quadrant slogans. Weights are editorial. Where a vendor hides price, the cell says contact vendor.

LinkedIn reports recruiter InMail acceptance in the 18–22% band according to LinkedIn Talent Solutions (2024 Talent Insights range). That figure is outreach math; it is not a reason to pick Paradox. It is a reason not to lose the people who do click Apply because the form asked 40 optional questions.

Pros and cons

Greenhouse

Pros

• The candidate, job, and scorecard already live here for many mid-market firms.

• Harvest webhooks give an overlay a real application event.

• Compliance packets are ATS workflows, not a second survey tool.

Cons

• Quote-only; contact the vendor.

• Native apply can feel like an ATS, not a candidate-facing form.

• Implementation is a program, not a weekend Typeform.

Lever

Pros

• CRM-style ATS keeps req and candidate in one place when mapped.

• Strong for teams that already standardized on Lever.

• API supports an overlay without replacing the ATS.

Cons

• Quote-only; contact the vendor.

• Client-facing intake UX is not why firms buy Lever.

• A failed map creates duplicate candidates, which is worse than a PDF.

Ashby

Pros

• Modern ATS with native forms and reporting in one product.

• Faster path than a two-vendor form-plus-legacy-ATS stitch for teams already moving.

• API-first enough for a hold-and-review overlay.

Cons

• Quote-led commercial terms.

• Still not a public microsite builder.

• Migration off Greenhouse or Lever is a data project.

Workable

Pros

• Public-ish starting rung for SMB staffing desks.

• ATS-native applications without an enterprise ATS program.

• Reasonable time-to-first-job-post.

Cons

• Confirm list price; published rungs move.

• Enterprise compliance depth is not Greenhouse.

• High-volume conversational apply is not the product.

Typeform

Pros

• Fast, branded candidate and client forms.

• Documented form_response webhook for a real overlay.

• Low software list versus an ATS seat.

Cons

• Not an ATS; write-back is your job.

• Easy to launch without retention rules.

• Coordinators will re-key if you skip the map.

Jotform

Pros

• Tables, PDFs, and internal req forms teams already know.

• Public Bronze/Gold rungs for a first bill.

• Webhooks exist if you use them.

Cons

• Email-PDF “integrations” fake a candidate record.

• ATS mapping is not native Greenhouse.

• Easy to sprawl 40 forms with no owner.

Paradox

Pros

• Conversational apply on SMS/chat for high-volume lines.

• Can create ATS candidates when mapped.

• Reduces form abandonment on mobile.

Cons

• Quote-only; contact the vendor.

• Scripts can skip required fields at scale.

• Overkill for a 4-recruiter retained-search boutique.

FAQs

Does Typeform replace Greenhouse for recruiting intake?

No. Typeform is a front door; Greenhouse is the candidate system of record, and without write-back you still have a coordinator inbox.

Can Jotform store EEO data for a staffing firm?

It can collect fields, but retention, access, and the ATS file are still your policy; treat the form as a capture step, not the employment record.

What is the cheapest intake form software for a 10-recruiter desk?

Typeform or Jotform on list price; the cheapest complete file is usually the ATS you already pay for, because re-keying 1,200 applications is the real bill.

Should a retained-search boutique buy Paradox?

Usually no. Paradox fits high-volume conversational apply; a boutique with 20 live searches needs complete client and candidate files, not a chatbot.

How do we compare Greenhouse vs Lever for intake specifically?

Ignore the generic ATS bake-off and inspect one thing: whether a submitted application becomes one candidate ID with required fields enforced, then pick the ATS you will not rip out.

Is US Tech Automations an ATS?

No. US Tech Automations maps form events, holds incomplete packets, and queues a coordinator; Greenhouse, Lever, Ashby, or Workable still own the candidate.

When is a Google Form enough?

When you run fewer than a handful of reqs, you will paste winners by hand, and you accept that the sheet is not an employment-record system.

Vendor facts on this page were last reviewed September 1, 2026.

Key Takeaways

• Start with the ATS you already trust, then decide whether intake is a native application, a Typeform/Jotform door with write-back, or a Paradox conversation.

• 44-day average time-to-fill is the clock; a two-day form chase is not “admin.”

• Typeform and Jotform are not ATSs; price the coordinator hours if you skip mapping.

• A connected route can validate, route, and draft the candidate; a recruiter still owns the req and the offer.

Who this is for

This page is for recruiting operations leads, staffing owners, and TA coordinators at US firms that already run an ATS and still retype candidate or client intake from email, job boards, and PDFs. It assumes you can name the system of record for the candidate, the job, and the client, and you can name who is allowed to create a candidate when the parser is unsure.

A 14-recruiter firm that still launches a new req in Slack is not ready for Paradox. Fix client intake first: one form, 18 fields, a Greenhouse or Lever job object, a named owner. Then fix candidate apply on the boards that actually produce send-outs. Then, and only then, add a conversational apply path for high-volume lines. Buying all seven products in this shortlist is how you get four candidate databases. Pick one ATS of record and at most one front door.

Mobile apply is the conversion leak that looks like “we need AI.” If most applications start on a phone and your Greenhouse apply is a long desktop form, Typeform as a door can raise completion without replacing the ATS. Measure completion rate on mobile for 30 days before you buy a chatbot. If completion is already high and the file is incomplete, you have a required-field problem, not a UX problem. Those two problems want different rows in the landscape table.

Red flags: you fill three roles a year and a spreadsheet still closes; you will not staff a coordinator to review held writes; you wanted a chatbot to auto-advance every applicant with no human gate; you cannot keep application records for the EEOC 1-year floor.

When NOT to use US Tech Automations: if Greenhouse or Lever already captures, validates, and writes the complete file you need; if you have no second system and a Google Form plus two recruiters is enough; if you will not name a human to release a held application.

If you need the overlay—field map, incomplete-packet hold, coordinator queue—start at US Tech Automations and keep the candidate record in the ATS.