Afterclerk
Book a call
For independent US recruiting and staffing firms

Your recruiters finish the call. The write-up is already done.

After every candidate call, Afterclerk drafts the ATS note, the updated fields, the client submittal and the candidate’s follow-up email. Your recruiter gets one email, checks it, and clicks approve. The note lands in your ATS, and the emails wait in their drafts for them to send.

We build it for your firm: your ATS, your templates, your way of working. Fixed price, live in 7 days.

made-up example10:19 AM
FromAfterclerk approvals
ToDana (your recruiter)
Approve 5 drafts · call with Priya Example · Senior Accountant
  1. ATS note→ your ATSApprove
  2. 3 field updates→ your ATSApprove
  3. Client submittal→ Dana’s draftsEdit
  4. Follow-up to Priya→ Dana’s draftsApprove
  5. Task: call the client Thu→ your ATSApprove
The only email Afterclerk sends goes to your recruiter. They send the rest themselves.
$1,500, fixedlive in 7 days · half up front, half when it passes a test you agree
Works with your ATSCrelate first · Bullhorn, Loxo, Recruiterflow and others checked on the call
Nothing goes out on its ownyour recruiter approves every note and sends every email

3 founding places at $1,500 until 30 November 2026. No client is live yet; the first three firms help shape it. Reserve a place

01 / After the call

What happens after every candidate call.

Afterclerk isn't a note-taker and it isn't another app for your team to log into. When a recruiter finishes a candidate call, it drafts the admin they would otherwise type up, sends that recruiter one email to check it, and files only what they approve.

What it is
Software we build for your firm that does the typing after a candidate call.
Who gets emails from it
Only your recruiter. One email per call, asking them to approve the drafts.
What candidates and clients get
Nothing from us. Your recruiter sends those emails themselves, from their own mailbox.
Your recruiter's day
after every call, by handrepeated after every candidate call
  1. 1Open the candidate's record in the ATS and type up the call.
  2. 2Update the fields: pay expectation, notice, availability.
  3. 3Write the summary for the client, in that client's format.
  4. 4Email the candidate the next steps.
  5. 5Set a reminder to chase the next thing.

What does that add up to?

≈ 5 hours a week per recruiter

4 min × 15 calls × 5 days ÷ 60

Your numbers, not ours.

Who gets what, step by step

Four steps, using one made-up call. Click through, or press play.

walkthrough · one candidate callmade-up records · sample

Step 1 of 4

The call ends.

Your recruiter finishes a call with a candidate, the same as today. The words of the call come from your phone system (Aircall, Dialpad), your meeting recorder (Fathom), or notes your recruiter pastes in.

We don't record calls. We read the transcript your own system already makes.

Came from:
Phone call · from Aircallmade-up records · sample

Call with Priya Example · 4 min · Example Technical Staffing

Dana Example (recruiter) · Wed Oct 7 · 10:14 CT · Senior Accountant, JO-2041

call ended

from the transcript (excerpt)

01:57 Priya: I'd want to be around ninety-eight. Sorry, ninety-eight thousand base.

02:33 Priya: Four weeks. Maybe two if I can negotiate it with my manager.

02:43 Priya: About three weeks after an offer.

Isn't this just a note-taker?

Fair question. Note-takers are good at summaries, and some ATS vendors now include AI too. Afterclerk is for the step after the summary: your fields, your templates, and a named person approving each piece.

What it doesAI note-taker (Fathom, Otter…)AI inside your ATSAfterclerk
Writes a summary of the call✓ yesdepends on plan✓ yes
Puts it into your ATS fieldspartlydepends on plan✓ yes
Writes the client submittal in your formatpartlydepends on plan✓ yes
Drafts the candidate follow-uppartlydepends on plan✓ yes
Built around your templates and approvalpartlypartly✓ yes
Works from phone calls, not only videopartlydepends on plan✓ yes

“Partly” and “depends on plan”: depends on your plan; check with your vendor. If a good summary is all you need, a note-taker may be the simpler answer. Product names belong to their owners.

What you get for $1,500, one time

  • Built for your ATS and your templates
  • Live in 7 days
  • Paid 50% now, 50% when it passes a written test agreed with you
  • Yours to keep: it runs in accounts you own

Hosting and AI usage are billed to you by those providers, usually $50 to $60 a month plus usage.

02 / Fit check

Is it worth it for your firm? Find out in 60 seconds.

Six quick questions about your team and your calls. You get a rough count of the hours your recruiters spend typing after calls, and a straight answer on whether a build is worth it. Your answers stay in your browser unless you book or email them.

fit check · 6 questions stays in your browser

Question 1 of 6

How many recruiters do you have?

Rather just talk it through? Skip the questions and book 30 minutes.

03 / Who we are

A small software consultancy, not another subscription.

Afterclerk is one engineer, based in the UK, who builds this for a handful of US recruiting firms at a time. We don’t sell you a platform with seats. We look at how your recruiters work after a call, agree in writing what the software should produce, then build it inside accounts your firm owns. You keep it, and everything it needs to run, whether or not you keep us.

We don’t replace your ATS, your phones or your recruiters. Your recruiters keep the calls, the judgement and the final say. We take the typing.

WHAT WE HAVEN’T DONE YETworth reading before you book ·
  • No client is live yet, and no ATS connection is live. Every demo on this page uses made-up records.
  • No security certifications (no SOC 2, no ISO 27001). We publish exactly how it handles data instead.
  • Professional indemnity and cyber insurance with US cover is still being confirmed.
  • Our refund wording and regulatory position are with US counsel before launch.
  • It’s one person. That’s why every build comes with a runbook and handover video, so your firm isn’t stuck if we’re unavailable.
04 / How it works

How it works, from first call to live.

Five steps. You can stop after the first call or after the written plan, and nothing is billed until the plan is signed. Click a step to see what you do and what we do.

STEP 1 · SCOPING CALL

You

We

Output

    05 / Your ATS

    Your ATS sets how we write.

    Afterclerk writes into the ATS you already use, and only after a named recruiter approves. Crelate is the first build target. No ATS connection is live yet.

    Pick your ATS design · no ATS connection is live yet

    What its AI does

    listed price, Oct 2026

    Crelate AI Assistant is on the Business plan at $119 per user. Co-Pilot is unpriced.

    What Afterclerk adds

    Our first build target: open API, with notes and tasks written only after approval.

    Write mode

    API after approval

    approval API write ATS

    Notes, tasks and the agreed fields only, each after a recruiter approves it.

    Three questions to ask your ATS vendor first

    Tick each answer your vendor gives as a yes.

    Prices and features come from each vendor's own pages, October 2026. Prices change, so we check them again before every proposal. Product names belong to their owners, and we have no partnership with any of them.

    Book a call about Crelate

    06 / Proof

    A written test decides when it is done.

    Step 4 of every engagement. The acceptance test is written and signed by both of us before the build starts, and the second invoice is raised only when it passes. These are the minimum scenarios; yours are added in the scoping call.

    run log · sandbox made-up records · sandbox
    Scenario Pass Result
    Normal call Five drafts, every stated fact with its line queued
    Missing facts "Not stated", never a guess queued
    Duplicate candidate Stops and asks; no write queued
    ATS API failure Drafts kept; recruiter told; retry queued
    Messy transcript Facts only; low-confidence items flagged queued
    US dates and phones MM/DD/YYYY and 10-digit formats correct queued

    Not run yet. Press Run and the six scenarios play against made-up records in this page.

    Synthetic. A sandbox pass shows that the runner works; it says nothing about your firm yet. The real test is written and signed by both of us before the build starts. The target is agreed with you before the build, for example: on 10 agreed test calls, at least 9 notes approved without edits, and no writes without approval.

    Step 1 is a free 30-minute call. Bring one recruiter’s typical day and we’ll tell you honestly whether it’s worth it.

    Book the free first call Take the 60-second check first
    SEE IT WORK

    Try it yourself on made-up calls.

    Everything below runs in your browser on invented records. Nothing is sent anywhere.

    07 / Run it

    Run it on a made-up call.

    The firm, the recruiter, the candidate and the job are fictional, the ATS is a sandbox, and nothing leaves your browser: the whole run happens on this page.

    transcript · DEMO-CALL-0001 made-up records · sandbox
    10/07/2026 · 10:14 CT · 30 lines · 03:49 · 2 speakers
    redaction off · the model never receives the phone or the email, only [PHONE] [EMAIL]
    run · idle made-up records · sandbox
      idle · press Run · the run clock is the demo's own, not a measurement
      outputs · CAND-10482 · JO-2041 made-up records · sandbox

      Every record above is invented, the ATS is a sandbox, and the run clock is the demo's own, not a measurement.

      That was a made-up call. On a 30-minute call we run one of yours, with your fields and your template.

      Book a call to run one of your calls See the tricky calls
      08 / Six calls

      Six calls that go wrong, and what it does.

      Six made-up calls from six made-up firms. Each one has a line that trips a tool that only summarizes. Pick a call to see the step that caught it, the rule that fired, what the recruiter sees and what gets written.

      Every firm, person and record here is invented.

      made-up records · sample Left and right arrow keys move between calls

      09 / Built to your firm

      Your template, your fields, your rules.

      Each build is engineered to one firm: the redaction rules it applies, the house style of its submittals, the field names in its ATS. Try the three parts on made-up records. They run in your browser and send nothing.

      This runs before the model sees the text. The model gets the right-hand side; the log keeps counts, never values.

      made-up records · sample
      0 chars
      Edit it or type your own. It redacts as you type.
      sent to the model0 chars
      
                  
      • [SSN]3-2-4 digits, or 9 digits after "SSN"0
      • [DOB]a date within a few words of DOB, born or birth; other dates stay0
      • [CARD]13 to 19 digits that pass the Luhn check; others stay0
      • [BANK]6 to 17 digits right after routing, account, acct or bank0
      • [EMAIL]any email address0
      • [PHONE]US formats, with or without an area code0
      • [ADDRESS]number, street and suffix, with unit, city, state, ZIP0

      These patterns are the sample's. Your build's list is agreed with you and tested on your own notes before anything reaches a model.

      Book a call to agree your redaction rules
      10 / What you get

      The documents you get, before you pay for them.

      A consultancy is judged by its paperwork. These are the documents one engagement produces, filled in for a made-up firm: Example Technical Staffing in Austin, TX, with recruiter Dana Example, candidate Priya Example and job order JO-2041. Turn on the margin notes to see why each clause is there.

      document viewer · 6 samples made-up records · sample

      Showing the statement of work, page 1. 3 margin notes.

      AFTERCLERKcustom software for recruiting firms
      Doc
      AC-SOW-S01
      Version
      1.0
      Date
      2026-10-09
      Page
      1 of 6
      SAMPLE · made-up firm

      Statement of work

      Post-call admin workflow · one workflow · Example Technical Staffing

      ClientExample Technical Staffing, Austin, TX
      SupplierAfterclerk, [trading entity]
      ApproverDana Example, recruiter (backup: Sam Example)
      SystemsCrelate (sandbox first) · Aircall transcripts · approvals mailbox
      TermSeven business days, Day 0 to Day 6. Day 0 is the day this SOW is signed and the starting payment clears.

      1. Scope

      1. One trigger: a call transcript arrives from Aircall, or is pasted or uploaded.
      2. Extraction to the field list in Schedule B. Every fact cites its transcript line; anything the call did not state reads "Not stated".
      3. Five drafts per call: ATS note, candidate summary, client submittal, follow-up email, next task.
      4. Approve, Edit or Reject on every item, by a named recruiter.
      5. Writes after approval only: the note, three agreed fields and the task. Email drafts are saved to the mailbox, unsent.

      2. Deliverables

      #DeliverableDue
      1Field map and extraction rulesDay 2
      2Workflow in your hosting account, on test recordsDay 3
      3Acceptance test report against Schedule CDay 5
      4Live workflow, runbook, data-flow note, handover sessionDay 6
      5Failed-run checks each business dayDays 6–11

      3. Not included

      Scoring, ranking, fit labels, shortlisting, or any change to a candidate's stage or status. Sending anything to a candidate or a client. A second ATS, data migration, or backfilling past calls. Call recording and consent wording (yours, with your counsel). Salary history, background or credit data. Hosting and AI usage, billed to you by those providers.

      4. Changes

      Any change is quoted in writing before it is built. No work starts on an unagreed change, and nothing outside section 1 is built "while we're in there".

      5. Price and payment

      Starting payment (50%)$750On signature, before work begins
      Balance (50%)$750When the written acceptance test passes
      Total$1,500One-time

      Optional support: $199 a month, cancel any month. Not part of the total.

      6. Acceptance and refund

      The acceptance test in Schedule C, written and signed before the build, decides when the work is done. If the workflow still fails a criterion in scope at the end of the 14-day fix window, the starting payment is refunded and this SOW ends. [Refund wording: with US counsel before use.]

      Continues on page 2: data protection, AI terms, exit, signatures.

      AC-SOW-S01 · v1.0 · 2026-10-09made-up records · samplepage 1 of 6

      Every engagement starts with a statement of work written for your ATS, your fields and your approvers, signed before anything is built.

      Book a call and we'll draft your statement of work
      11 / Scope it

      Build your scope in a minute, then book the call.

      Pick your ATS, where your calls come from and what you want drafted. The draft scope beside the steps shows the engagement that fits, its price and the rule that set it. It is a starting point for the call, not a quote, and nothing leaves your browser until you copy it, email it or book.

      scope builder step 1 of 5

      Which ATS does your firm use?

      Pick one. Your ATS sets how approved items get written.

      How the price is set

      one rule applies

      1. R11 workflow · 1 ATSFounding $1,500 one-timefirst 3 US firms, before the end of November 2026
      2. R22 workflows · 1 ATSCore $2,500 + $299/monthopens after the founding cohort
      3. R33 workflows · 1 ATSGrowth $3,500 + $449/monthopens after the founding cohort
      4. R44+ workflows, or a second ATSCustom from $4,500priced on the written scope

      The post-call workflow counts as 1. Submittal from CV adds 1. A second ATS makes it custom. Support on the founding engagement is optional at $199/month, cancel any month. Hosting and AI usage are billed to you by those providers, usually $50 to $60 a month plus usage.

      12 / Price

      Price and guarantee

      Fixed price, scoped in writing before any build. The optional support plan is the only recurring fee we charge.

      founding price7 days · 50 / 50

      Founding price

      one-time · one workflow · built in 7 days

      Built to
      your ATS fields and templates, in your accounts
      Workflow
      note, fields, summary, submittal, follow-up and task
      Approval
      a named recruiter's step, with its record
      Handover
      runbook, handover video, a named way to switch it off
      Measure
      before and after, over two weeks
      refund wording: with US counsel

      If the workflow does not pass the written acceptance test within a 14-day fix window, your deposit is refunded. The written test decides pass or fail. We do not promise hours saved, placements or revenue.

      3 of 3 founding places open
      for three US firms, before the end of November 2026
      No client is live yet; these three firms are the first.

      Claim a founding place Build your scope

      Engagements
      EngagementOne-timeSupport a monthScope
      Founding$1,500$199, cancel any monthOne workflow, built in 7 days
      Core$2,500$299Two production workflows on one ATS, after the founding cohort
      Growth$3,500$449Three workflows on one ATS, deeper field mapping, after the founding cohort
      Customfrom $4,500On scopeFour or more workflows, or a second ATS
      • Support, optional: $199 a month for monitoring, fixes and small changes. You can cancel in any month.
      • Hosting and AI usage: billed to you by those providers, usually $50 to $60 a month plus usage. You keep those accounts if we part ways.
      • Invoices: in US dollars, by card or ACH. Run from the UK by one person, who builds, tests and supports each workflow.

      Payment: 50% to start, 50% on pass

      The clock starts when the deposit clears and we have access and a few sample calls.

      13 / Your numbers

      Your numbers

      Change any input and the estimate updates. It shows recruiter hours on post-call admin each week, and what that costs at a loaded hourly rate. It is arithmetic, not a promised return.

      The people who take candidate calls (slider to 20, type up to 200)
      Candidate calls that end in admin
      Notes, fields, the submittal and the follow-up
      BLS wage data for recruiters and HR specialists, with a 1.43 benefits multiplier, is about $43 to $52
      output · per week and per monthillustrative defaults
      Recruiter hours on post-call admin, per week
      30.0 h
      At your loaded cost, per month
      $6,500

      Check these numbers on a call

      For scale, $1,500 is about 41 hours of wages at the BLS median of $36.51 an hour for human resources specialists, a group that includes recruiters (May 2025).

      We could not find a US study of how much of a recruiter's week goes to admin, so we do not quote one. Before any build, your team logs its candidate calls and the admin after them for one working week, and we agree the measure in writing.

      The defaults are illustrative. The minutes-per-call figure has no public study behind it.

      Hours a week, by recruiter count, 1 to 20 Click a bar, or focus the chart and use the arrow keys

      Hover a bar to read it. The current count is amber.

      14 / Not for

      Who this is not for

      This is probably the wrong fit if any of these is true. Mark the ones that describe you.

      • 01

        Your ATS already covers your phone calls, on a plan you pay for, and it writes only after someone approves. Check that first.

      • 02

        You want the workflow to score, rank or shortlist candidates. It does not do that.

      • 03

        You want an unattended mode. There is none; a recruiter approves every write.

      • 04

        You need Bullhorn to take writes directly today. Bullhorn stays approval-first until it grants written API permission.

      • 05

        The admin after your calls is small. We count your numbers on the call, and we say so if there is no case for it.

      15 / Questions

      Questions owners ask

      Start with the three questions in the ATS section above. Most native features we read about draft text or summarize a record. The chain from a phone call to a filed record and a client-ready submittal, with a named person approving each step, is usually still manual. That chain is the part we build.

      Didn’t see your question? Ask it on the call. There’s no pitch deck and no follow-up sequence.

      Book a 30-minute call Email instead
      16 / Next step

      Book 30 minutes. Bring one recruiter’s typical day.

      We look at what your recruiters do after a candidate call, count the time against your own numbers, and tell you straight whether $1,500 is worth it for your firm. If it isn’t, we say so. If it is, you get a written plan, and you can be live seven days after the first payment.

      Book a scoping call Take the 60-second check Technical appendix

      Or email hello@afterclerk.com

      Replies within one US business day. Live-call hours of 11am to 1pm Eastern, Monday to Friday, are still being confirmed. Calls run on Zoom or Google Meet.

      1. THE 30 MINUTESagenda
      2. 00–05Your firm: ATS, phone system, desks, volume
      3. 05–15One recruiter's day after a call, step by step
      4. 15–20We run the demo on your kind of call
      5. 20–25Count the minutes; is there a case?
      6. 25–30Yes, no or not-now. No follow-up sequence.
      TECHNICAL APPENDIX

      For whoever checks the security and the build.

      Owners can stop here. This part is for your IT person, your compliance lead or your counsel: how it is built, where the data goes, and what it will never do.

      STACKcalls in: paste or upload · Aircall · Dialpad · Fathommodel: Claude via the Anthropic API, key in your nameATS: Crelate API first · Bullhorn approval-firstmail: Gmail or Outlook drafts, never sent by usruns in: your hosting account, US region
      17 / The pipeline

      Every step a call goes through.

      afterclerk pipeline · the design we build tomade-up records · sandbox
      • read
      • model call
      • human
      • write
      • holds to error workflow
      ready waiting on a person held or failed

      run log · sandbox · made-up records
      18 / Output

      Five drafts and the facts behind them.

      Five drafts come out of each call. Every fact carries the line it came from, and a fact the candidate did not state reads “Not stated”.

      drafts · one callmade-up records · sandbox
      1. Filled from the agreed fields and a fixed template. No model call. It reaches the record only after a recruiter approves it.

      2. Written once from the transcript and the agreed facts, then reused in the submittal. At most five bullets or about 120 words.

      3. In your template, saved to drafts. The recruiter-only block is removed before anything is sent.

      4. Saved as a draft, never sent. Not written at all if the candidate asked not to be contacted.

      5. One task, linked to the candidate record and the job order, with an owner and a due date.

        Owner: Dana Example · Due: suggested Thu 8 Oct 2026 · recruiter to confirm

      Open a draft to see what it is built from. Lengths are counted live from the made-up text.

      afterclerk.extraction.v1 · design stage
      Design stage. The field list the build writes to. No score, rank or fit field exists.
      validator · forbidden termssandbox · made-up sample

      A match in a model draft holds the draft. A match in a human edit is a warning only: a person wrote it, and the person decides.

        Whole words, any case. A * matches the rest of a word, so concern* catches concerns and concerned. Amber-marked terms are for review and do not hold. A sign-off line such as “Best,” on its own is not read as an opinion.

        19 / Architecture

        Where the data goes, and where it never goes.

        Below: the checks we write into every pipeline, the five places a call's data can sit, and the three keys you hold. Each check is code we write and test for your build.

        A

        What is custom-built

        design · not built yet

        The checks run in order. Each one passes the run on or holds it, and a held run writes nothing. Open a check to read what it does and when it holds.

        1. Checks the webhook signature and a five-minute timestamp window before anything is read. Sources: Aircall transcription.created, Dialpad call_transcription, Fathom new-meeting-content-ready, or a paste or upload.

          holds whenA bad or stale signature is refused. Nothing is read.

          timestamp within 300 s and signature valid → read · else refuse
        2. The recruiter confirms the recording disclosure was stated and the candidate agreed. On the made-up call the disclosure is at 00:11 and consent at 00:19.

          holds whenNo confirmation, the run waits.

          disclosure_at and consent_at → continue · else hold
        3. Numbers each line L1 to Ln with its time and speaker. The vendor's raw JSON is dropped here, not kept.

          holds whenNothing holds. The raw payload is discarded.

          L{n} · mm:ss · speaker → keep · raw_json → drop
        4. Stops very short or very long input, and calls that carry speaker labels but no candidate lines. Ceilings: 60,000 characters of transcript, 25 MB of audio.

          holds whenUnder 150 or over 9,000 words, or no candidate lines when labels exist. No model call.

          150 ≤ words ≤ 9000 · candidate_lines > 0 when labels exist
        5. Replaces SSN, date of birth, card, bank, email, phone and home address before the model call. Logs a count per token type, never the value.

          holds whenNothing holds. The model call runs on the redacted text.

          [SSN] [DOB] [CARD] [BANK] [EMAIL] [PHONE] [ADDRESS] · counts only
        6. Reads the candidate record and the job order from your ATS. A phone match on another record stops the run and asks the recruiter.

          holds whenPOSSIBLE_DUPLICATE. The run stops and asks the recruiter.

          phone_match(other_record) → ask "Same person?"
        7. Checks afterclerk.extraction.v1 for types, enums, required keys and no extra keys. Then each quote must sit inside its cited line, case-folded and whitespace-normalized, at 25 words or fewer.

          holds whenOne retry with the error text, then hold.

          required and enums and no extra keys · quote ⊆ line(evidence_id) · ≤ 25 words
        8. Summary at most five bullets, about 120 words. Follow-up at most 180 words. Submittal at most 350 words.

          holds whenA draft over its cap fails the draft check.

          bullets ≤ 5 · follow_up.words ≤ 180 · submittal.words ≤ 350
        9. Whole words, case-insensitive, with * for a stem. Covers evaluative, protected and injected phrasing. Runs on every model draft and every human edit.

          holds whenA match in a model draft holds it. A match in a human edit is a warning only.

          shortlist · pregnan* · ignore previous → hold (model) · warn (edit)
        10. Every name in a draft must appear in the transcript, the ATS record, the job context or the recruiter's form.

          holds whenA name that cannot be traced fails the draft check.

          name ∈ transcript ∪ record ∪ job ∪ form
        11. The approver types their name. Each decision is attributed to that name, and an edit is diffed against version 1 and checked again.

          holds whenEach decision is recorded under a typed name.

          approved_by = typed_name · diff(v1, edit) → re-check
        12. Writes the ATS note, the agreed fields and one task. Saves the follow-up and the submittal as mailbox drafts, unsent. Never a stage, a status or a pipeline.

          holds whenNo write without a decision row for that output.

          write ⊆ {note, agreed_fields, task} · mail = draft · decision.approved
        13. Keeps the workflow name, node name, execution id, HTTP status and error class. Drops messages and bodies, so no candidate text reaches the error log.

          holds whenThe run stops and writes nothing. The error log keeps IDs only.

          keep: workflow, node, execution_id, http_status, error_class · drop: message, body
        14. Holds the drafts and the transcript in staging until the decision. Deletes transcript and audio within 24 hours of it, a logged manual step until automated. Purges logs at 30 days and reports the counts.

          holds whenNothing reaches a system before approval. The sweep alerts if it deletes nothing for three days while open calls exist.

          ttl = 24 h from decision · logs ttl = 30 d · alert if deleted = 0 for 3 d and open_calls > 0
        B

        The data map

        made-up records · sandbox

        Five places a call's data can sit. Pick one to see what it holds, for how long, and who can revoke it. Move through the run to see what each place still holds. Never: a candidate or a client receives anything without a recruiter's approval.

        five territories · one runmade-up records · sample
        1. 1 Transcript in, at intake.
        2. 2 Redacted request out. Drafts back.
        3. 3 After approval: note, fields and task to the ATS. Drafts to the mailbox, unsent.
        4. 4 Transcript and audio deleted. Logs purged at 30 days.
        time through the run

        C

        Revoke in one step

        made-up records · sandbox

        One switch per key you hold. Flip one and the pipeline stops at once. These switches change this page only; nothing is sent to any system.

        • ATS access key

          Reads candidates and jobs. Creates notes and tasks. Updates the fields you agree.

          revoke in your ATS admin console
        • Mailbox grant

          Saves drafts in your Gmail or Outlook. Sends nothing.

          revoke in your Google or Microsoft account
        • Hosting account access

          Runs the workflow in your hosting account. Switching it off stops new intake. Nothing breaks in your ATS.

          switch the workflow off in your hosting account

        20 / Security

        What we touch, and what we never touch

        The architecture above shows every step. Here is the short version a security reviewer asks for: we read the call and the two records the run needs, through keys you create; identifiers are removed before the model sees the text; nothing reaches your ATS, a candidate or a client until a named recruiter approves; every decision is logged with who, when and what changed. We do not record calls.

        What we need from you: an access key with the narrowest permissions (read candidates and jobs, create notes and tasks, update the agreed fields), three to five sample calls, and two recruiters for the acceptance test.

        sample log · made-up records · sandbox

        We never touch the stage, the status, the pipeline or any record the approval did not name.

        register · 6 entrieswhat we do, and how you check it

        Showing 6 of 6 entries

        • Access

          Who can send anything to a candidate or a client?

          Only your recruiter. Nothing is sent or written until a named person approves it.

        • Model

          Does the model train on our candidates?

          No. The model provider's commercial terms say it may not train models on customer content sent through the API, and the key is in your name.

        • Keys

          Whose accounts and keys?

          Yours: your hosting account, the model provider and the transcription provider. Each client has separate credentials in a secrets manager, never shared between firms.

        • Model

          What does the model see?

          The transcript, the job context and your template, with identifiers removed first.

        • Retention

          How long do you keep call data?

          Transcripts and audio are deleted within 24 hours of the recruiter's decision. That deletion is a logged manual step until the automatic job is built. Workflow logs are kept 30 days.

        • Breach

          When do you tell us about a breach?

          Within 48 hours of awareness, in writing, with what was affected and what we did.

        You can do these without asking us

        1. Revoke the access key in your ATS, mailbox and hosting account, one step each.
        2. Export the workflow, prompts and logs from your own hosting account.
        3. Switch the workflow off. Nothing breaks in your ATS.
        4. Request deletion of anything we hold. We confirm it in writing within 30 days.
        5. Ask for the sub-processor list and the data processing addendum before we start.

        Book a call with your security questions

        21 / Administrative by design

        How it stays administrative

        The workflow writes up the paperwork. It does not make, score or recommend hiring decisions.

        What it will do

        • Extract the facts a candidate stated, each with the sentence it came from.
        • Draft the note, summary, submittal, follow-up and task for a named recruiter to approve, edit or reject.
        • Record every approval, with who, when and what changed.
        • Record compensation expectations as the candidate states them.
        • Stop and ask when a record may be a duplicate or a fact is missing.

        What it will not do

        • Score, rank, rate, label or classify a candidate, or say whether a candidate fits a job.
        • Screen, filter, shortlist, reject or withdraw a candidate.
        • Move a candidate between stages or change a status.
        • Send anything to a candidate or a client without a recruiter's approval.
        • Ask for, extract or store salary history or current pay.

        The design aims to keep the workflow outside the automated employment decision tool rules in New York City (AEDT), Colorado's AI Act and California's automated decision-making technology regulations (ADMT). Those rules apply to systems that make or substantially assist hiring decisions. This is a design position, not legal advice. We walk your counsel through it.

        Recording consent, state by state

        design view · not legal advice 11 all-party · 3 situational
        • All-party consent (11)
        • Situational (3)
        • Not on either list
        • ←→↑↓ move · Enter pin · Esc clear
        -- Hover, focus or tap a state No state selected A state shows its status here. Click or press Enter to pin it.

        The recording announcement is yours; your counsel decides the wording. A candidate who declines goes through the paste-in route. Source for the state list: Rev, November 2025.

        Want your IT or compliance person on the call? Bring them; it’s the same 30 minutes.

        Book a call with your IT person