Post to ZipRecruiter and see which board actually produced placements

ZipRecruiter is a United States board first, and the desks that lean on it are usually running high-volume commercial, light industrial, healthcare support or sales requisitions where speed of response matters more than the depth of any individual profile. Applications arrive quickly and in quantity, and the desk that answers first tends to win.

That shapes what the integration has to be good at. Not clever matching at the point of ingest, but speed: the applicant becomes a record with a parsed resume in seconds, the recruiter sees them in the requisition queue, and the first outreach can be a templated SMS or WhatsApp message sent from the list rather than a call that happens tomorrow.

It also shapes the compliance surface. Text messaging a US applicant means opt-in capture, STOP handling and suppression lists have to work properly, and 10DLC brand and campaign registration with the carriers is yours to hold. We provide the fields and the sending integration; the registration is not something we can do for you.

Sync is a word integrations pages use loosely. Here it means one specific thing: applicants who apply to a job you posted through the connector are written back into Surhires as candidate records attached to that requisition, with the resume parsed, the source set to ZipRecruiter, and the duplicate check run before anything new is created.

It does not mean a mirror of the ZipRecruiter candidate database inside your tenant, and it will not mean that later either. Board terms do not permit it and no serious vendor should offer it. What you get is the people who applied to your jobs, which is the set you have a relationship with.

Stage changes stay in Surhires. Once a candidate is in your pipeline, the board is a source rather than a system of record, and trying to keep two pipelines in agreement is how desks end up trusting neither.

Every job board reports the number it looks best on, which is applications delivered. A board can deliver four hundred applications to a requisition and produce no submittals at all, and if the only number on your desk is applications received, that board keeps its budget forever.

Because source is written at ingest and carried through every stage change, Surhires can report the funnel by board rather than the top of it. Applications by source, screened by source, submitted by source, interviewed by source, placed by source, over a period you choose. The same view broken down by requisition type usually shows that a board is excellent for one discipline and useless for another.

The uncomfortable version of this report is the one worth running. It is common for a desk to discover that the board consuming most of the advertising budget is producing the fewest placements, and that a quiet board is quietly carrying the desk.

US staffing desks generally run ZipRecruiter and Indeed together, because coverage overlaps but does not duplicate. Multi-board posting is built so a requisition is written once, formatted per board, and pushed to each connected board without retyping the description or diverging on salary and location.

Salary disclosure is worth a line of its own. A posting published into a state with a pay-range disclosure rule can be checked against the rules of the states and countries it is going to before it goes out, and flagged if the range is missing. Whether a given posting meets a given jurisdiction's requirements is a decision you make; the product's job is to raise it before publication rather than after a complaint.

Post on the board as you do now, and route the application emails into a requisition inbox so they parse on arrival. Set the source on the ingest rule rather than on each candidate, so the attribution reporting is already accurate before the API path exists.

For historic data, bulk resume import will take a folder of past applications and load them with the same parsing and the same duplicate check. Desks that do this in their first fortnight usually find several hundred people they were already paying to re-acquire.

When the connector is confirmed, the posting leg becomes automatic and the ingest path moves from email to API. Everything already in the database, including the source history the reporting depends on, stays exactly where it is.

There is no partnership announcement, no certification, no badge and no logo right implied anywhere on this page. We are building against a published API and applying for access through the same process any vendor uses.

If access is declined or the terms do not work, this page will say so and the state will change to reflect it. A roadmap that only ever moves forwards is a marketing document, not a roadmap.