Integrations, with their real status

Posting a job out to LinkedIn ships now. Everything deeper depends on partner access we have applied for and have not been granted yet.

The connector is in build for Wave 1: requisitions posted out to Indeed, applications ingested back, parsed and deduplicated on arrival.

In build for Wave 1: requisitions pushed to ZipRecruiter, applicants synced back, and source attribution that survives all the way to the placement.

In build and gated on Naukri partner access. The parsing work behind it, which is the part that actually decides whether the integration is useful, ships today.

In build for the UK market and gated on CV-Library partner access, with a manual sourcing loop that already works properly while we wait.

In build for Australia and gated on Seek partner enrollment. The state-based licensing and working-rights fields an Australian desk needs are already on the record.

WhatsApp is live in Surhires today, generally available for India-market recruiting, with United States sending held behind Meta template approval in Wave 2.

Twilio is connected today with your own credentials, so the number, the account and the carrier relationship stay yours rather than sitting behind a reseller margin.

The Slack connector is in active build for Wave 1 and is not connected today; it will post pipeline events into a channel rather than pushing candidate data around.

The Teams connector is in active build for Wave 1 and is not connected today; it will post hiring events into a channel and generate interview meeting links.

The Gmail connector is in active build for Wave 1 and is not connected today; it will file candidate and client mail on the record while leaving personal mail alone.

The Outlook connector is in active build for Wave 1 and is not connected today; it will file matching mail on the record and support shared mailboxes for a desk.

The Google Calendar connector is in active build for Wave 1 and is not connected today; it will feed the interview scheduler with real panel availability.

Exotel is on the roadmap and is not built. Voice today runs through Twilio with your own account, and that is the path an India desk uses right now.

Gupshup is on the roadmap and is not built. WhatsApp sending today routes through Meta, Twilio or DoubleTick, all of which are live in the product.

Wati is on the roadmap and is not built. WhatsApp sending today routes through Meta, Twilio or DoubleTick, all live and generally available for India desks.

Billing already happens on the placement record. This integration is being built so the invoice you raise there becomes the invoice your accountant sees.

UK and Australian agencies mostly keep their books in Xero. This integration is being built so placement billing arrives there without a second data entry pass.

Small clients pay faster when there is a link on the invoice. This integration is being built so that link exists and the payment finds its way back to the placement.

Indian recruitment desks bill under a different set of invoice fields and collect through different rails. This integration is being built for that, not adapted to it.

A screening order is a request and a result. This integration is on the roadmap so both live on the candidate record instead of in a recruiter's inbox.

Enterprise clients each mandate a different screening package. This integration is on the roadmap so which package applies is a field, not folklore.

Cross-border placements need checks that differ by country and sometimes cannot be run at all. This integration is on the roadmap; the judgment stays yours.

Indian IT hiring runs on employment verification, and the questions it answers are different from the ones a US criminal check answers.

Remote hiring made identity the first check rather than the last. This integration is on the roadmap so the result lands on the record, not in a mailbox.

Smaller Indian desks need verification without an enterprise program around it. This integration is on the roadmap; the ordering stays in your account.

Two documents decide whether a desk gets paid: the terms of business and the offer. This integration is on the roadmap so both are tracked, not chased.

An Indian fee agreement often needs stamp duty and an Aadhaar-based eSign. Neither exists in a US signature product, which is why this is its own integration.

When a client wants to hire someone in a country where they have no legal entity, the employment has to sit somewhere, and that somewhere is not Surhires.

Remote.com sits in the same category as Deel, and the practical choice between them usually comes down to country coverage and how contractors are handled.

Rippling is an HR system of record as well as an employment vehicle, which changes what a handoff from recruitment software is actually for.

Greenhouse stays the system of record for the hiring process. Surhires sits in front of it as the sourcing and relationship layer that feeds it.

Lever remains the hiring system of record. Surhires works the part of the funnel that happens before anyone is formally a candidate.

Ashby holds the hiring process and the analytics that go with it. Surhires holds the outbound work that happens before a person is a candidate.

Workday is the system of record for the whole employee lifecycle at the companies that run it, and integrating with it is scoped work rather than a toggle.

Mercer Mettl is widely used for volume hiring in India, and the operational pain is rarely the test itself. It is getting the result back onto the right record.

Technical screening usually happens in a specialist tool, and the recruiter loses the thread the moment the invitation leaves the recruitment system.

Most roles are not engineering roles, and the screening question for them is a mix of skills, situational judgment and language rather than code.

Every recruitment business runs two or three tools that will never justify a first-party connector, and a Zap is the honest answer for those.