Loxo

Loxo Source can search the vendor source and a firm's internal candidate database with natural-language terms, Boolean logic and filters. From within a Job Pipeline, a recruiter can choose which stage receives a sourced person; the same result can be added to a job, campaign or list. Test whether the specific search filters and contact data needed by a team are in its contracted tier.

The ATS has configurable stages, fields and job templates. Recruiters can move candidates in a Kanban view and inspect the Master Pipeline across active jobs. Set up one realistic fictional job with the team's actual stages before migrating records, because the stage model shapes reports and automations later.

Stage movement can trigger configured communication, scheduling, outreach or submittal actions. Map the trigger and recipient before turning on an automation: moving a candidate for internal review should not accidentally start a contact campaign. Keep a human decision point where a shortlist or submission needs judgment.

The Recruiting CRM collects candidates, clients, conversations, notes and activity history in one place. Search and filters help locate a person, and a recruiter can move the result into a job, campaign, list or call queue. Check duplicate handling and permissions with sample records before importing an existing candidate database.

Outreach brings email, SMS, phone and meeting activity into the recruiting record. Multi-stage sequences can send personalized email or SMS follow-ups, and interaction history can be logged on a profile. Confirm channel permissions, consent, sending identity and stop rules in a non-send draft before contacting real candidates.

The Hiring Manager Portal can share selected jobs, candidate stages and profiles with a hiring manager who may comment or rate candidates. Portal access is through an invitation or link; review exactly which jobs and candidate details are exposed before sharing it externally. A fictional job is enough to check that the view matches the intended audience.

Contact finding can fetch an individual email or phone, or run across a job stage. An automated stage fetch uses credits per candidate and contact type when information is found. Adding a sourced person straight to an Outreach Campaign can also use a credit to find contact information, so a seemingly simple stage or campaign action may have a data cost.

Natural-language candidate search itself is documented as free of credit charges, while adding people from that search to a job can consume credits. Inspect the Credit Usage view and test one fictional search-to-job path to understand the billing boundary before bulk additions.

ATS reports cover pipeline health, conversion, job search performance and recruiter activity. Use them to check where candidates are stalled, but agree how stages and owners are recorded first; inconsistent records can make a polished report misleading.