Skip to main content

​
Which should I use?

​
Interviewed Candidates

Why it matters: Everyone in this directory is already in your HeyMilo workspace — past applicants, sourced profiles, or anyone who entered through another flow. You’re not starting cold; you’re searching, filtering, enriching, importing, and inviting people you already have a record for.
What you do:
  1. Open Source Candidates → Interviewed Candidates.
  2. Search and filter (e.g. name, email, dates — whatever your workspace exposes).
  3. Sort and customize columns if the product offers it.
  4. Open a profile, then use Actions to invite to an agent, move to pipeline, or continue in your usual workflow.
Invited candidates follow the same path as other applicants: outreach (SMS, email, or link — per your settings) and results on your main dashboard when they finish. When to use it first: Before you spend on net-new sourcing, check Interviewed Candidates for strong fits you’ve already evaluated.

​
Sourcing Engine (ATS)

Why it matters: Sally runs autonomous sourcing for your agents — you define configs with quota, tiers (e.g. which sources apply: external pools, HeyMilo, ATS, etc.), mode (such as threshold vs manual), match threshold, and time limits, so sourcing isn’t only one-off manual searches.
What you do:
  1. Open Source Candidates → Sourcing Engine (ATS).
  2. Use + Create Config (or equivalent) to add or edit a Sourcing Engine (ATS) configuration (Sally).
  3. Tune quota, tiers, mode, and limits to match how aggressively you want to source and spend.
If you don’t see Sourcing Engine (ATS), your workspace or plan may not include it yet. When to use it: You want repeatable, capped sourcing rules instead of ad hoc searches only.

​
Apply via Email

Why it matters: Candidates can apply without a form by sending mail to a unique address you publish on postings, flyers, or campaigns — low friction on mobile and easy to drop into job board copy.
What you do:
  1. Open the agent (interviewer) → Integrations → Apply Email → Configure.
  2. Copy the generated email for that agent and share it where you recruit.
Limits (be explicit with candidates if needed): This path is for capturing contact / pipeline entry — it does not replace a full resume parser for attachments. For heavy document workflows, use your candidate ingestion options elsewhere in the product. When to use it: High-volume apply paths, events, or alongside a custom sender domain so mail looks like your brand.

​
Next steps