An agent that contacts candidates and submits them to your clients only becomes buyable if you can see what it did and stop it. This is our position on each area procurement asks about.
Two sourcing paths, two ownership positions. AriaScout works two candidate pools and they are not treated the same way.
Your database. Candidates already in your ATS are, and remain, yours. AriaScout searches them under your instruction and returns them to your system of record. We claim nothing over these records.
Job boards. Board searches run on AriaScout’s own subscriptions and at our cost, under our licence terms with each board. Records sourced this way are ours and stay part of our sourcing pool. When one is submitted against your requisition it is written into your ATS, and you hold and may use that record for the role it was submitted for and for your ongoing relationship with the candidate.
What that does and does not mean. A board-sourced candidate is not exclusive to you. The same person may be sourced for another firm’s requisition, exactly as they would be if two agencies found them on the same board independently. Our burn-rate signal exists so you can see when that has happened before you submit. What we never do is take a candidate out of one customer’s own database and work them for another customer.
Deduplication. Every board result is checked against your database before outreach, so you are never charged for a submission of someone you already owned.
Cross-network signals. AriaScout operates across a network of staffing firms. Behavioural signals — response patterns, submission frequency, rate outcomes — are derived and aggregated. Raw candidate records belonging to one customer are never exposed or resold to another.
Retention. Retention windows for sourced records, transcripts and recordings are configurable per customer and per jurisdiction, and are set during onboarding rather than defaulted.
Deletion. A candidate who asks to be removed is suppressed across outreach for the whole network, not just the requisition they were contacted about.
Identity. Messaging identity — sending domain, phone number and signature — is configured per client so candidates know which firm is contacting them.
Consent and opt-out. Opt-out handling is enforced before any message is sent, not reconciled afterwards. A suppressed record cannot be contacted by any channel.
Cadence. Maximum touches per candidate, per channel and per time window are set by you and enforced by the orchestration layer. A blocked send is logged with the rule that blocked it.
Off-limits. Client exclusivity, off-limits accounts and do-not-contact lists are imported during onboarding and evaluated before sourcing opens.
Disclosure. Candidates are told at the start of the call that they are speaking with an AI screener. This is not configurable off.
Recording consent. Recording disclosure and consent handling follow the rules of the candidate's jurisdiction, including two-party consent states.
Transcripts. Every completed screen produces a structured transcript attached to the candidate record, including the calls that end in a disqualification.
Escalation. Role families you nominate can be routed to human screening instead, without changing anything else in the pipeline.
Decision log. Every requisition carries a full log of what the agent did, when, and why — including scoring rationale, outreach history and blocked actions.
Exports. The log is exportable for internal review or to satisfy a client audit request.
Reconstruction. Any submission can be reconstructed after the fact: which candidates were considered, why this one cleared the bar, and what the others were disqualified on.
Access. Customer data is segregated per tenant. Internal access is role-based and logged.
Integration. The ATS connection is the only integration your team owns. Credentials are scoped to requisition read and submission write-back.
Encryption. Data is encrypted in transit and at rest.
Incident handling. Notification timelines and contacts are set out in the customer agreement.
Our current certification and attestation posture is shared under NDA during procurement. Confirm status with the account team before contracting rather than relying on this page.
Reviewing us formally? Send your security questionnaire to legal@ariascout.com and we will return it with the supporting documentation.
We will run AriaScout against a live req from your desk and show you exactly what comes back — the candidates, the scoring rationale and the screening transcripts.