Q01Will agents email candidates or employees on their own?
No. Every gmail_send, linkedin_send_message, and linkedin_send_connection_request is HITL-gated by default. The crew prepares the message, the recruiter or people manager approves the send. You can lift the gate per template once a workflow has proven itself.
Q02Can the agents reason over our ATS, HRIS, and policy docs?
Three ways. Static context attaches your interview rubric, leveling guide, and policy handbook to specific personas on every run. The rag_retrieve tool lets PeopleAnalyticsLead and CompensationSpecialist pull from ATS exports, comp bands, and engagement surveys on demand. Cross-run memory carries last week's flight-risk panel into this week's review.
Q03Does this replace Eightfold, Beamery, Gem, or HiBob?
No, it sits next to them. Melaya is the research, draft, and analysis layer. You keep your ATS and HRIS as the system of record. Approved drafts and updates flow back into the tool you already pay for, so the recruiter and people-ops workflow does not change.
Q04How do we keep candidate outreach from sounding like AI?
Drafts cite specific sources from the dossier, a GitHub repo, an arXiv paper, a recent talk, or a LinkedIn post, and reuse phrasings from your won-candidate email corpus loaded into the knowledge store. Recruiters can require a citation on every draft as a HITL pre-check.
Q05Which models can we run this crew on?
Any. Claude on EmployeeRelations where the reasoning earns the cost, GPT on the drafting personas, a local Ollama on PeopleAnalyticsLead when employee data must not leave your network. Each agent picks its own model.
Q06How fast can a People team get the first pipeline running?
With Gmail, LinkedIn, and Sheets connectors authorized, the inbound-triage workflow is a 4-node canvas: ingest application, score against rubric, draft reply, approve. Most teams ship it in a working session and have the first reviewed drafts in queue the same day.
Q07How does this handle employee data privacy and GDPR?
HRComplianceLegal tracks legal basis, retention, and cross-border transfer for every data category the crew touches. Scoped tools keep personal data inside the workflow that owns it, and the audit log records every read and every write.
Q08Can I audit exactly what the agent did and why?
Every run logs every step, every tool call, every model invocation, and every approval decision. Replay any candidate triage, any comp recommendation, or any ER note at any time. The audit log is the people record.
Q09Why use Melaya instead of n8n or Zapier for HR automation?
n8n, Zapier, and Make execute predefined trigger-action steps, while Melaya's HR & People crew plans across steps: the Talent Acquisition Lead scores candidates against your rubric, then stages outreach behind approval gates. Melaya adds full run traces and deterministic-first evaluation. Zapier and Make still win on connector breadth for simple linear automations.
Q10Can we reuse the same hiring workflow across different roles and teams?
Yes. Melaya, the visual AI agent builder, lets you save any run as a template, so the pipeline behind Triage inbound candidates against rubric or Prepare competitive offer packages becomes a reusable AI agent workflow. Swap the knowledge bundle, which holds interview rubrics, leveling guides, and comp bands, and the same crew serves engineering, quant, or sales hiring.
Q11Can we run HR agents locally so employee data never leaves our infrastructure?
Yes. Melaya runs in the cloud or on your local runner, and per-step model routing across 23 providers lets you route sensitive steps, like the People Analytics Lead's 90-day flight-risk panel, to local models. Cloud models can still draft public-facing outreach while HRIS and compensation data stays on hardware you control.
Q12Can Melaya operate HR apps that have no public API?
Yes. Melaya's Device Control operates a real Android phone: agents open allowed apps, read the screen, tap and type, and pause for on-device approval before anything is sent. The HR crew's default bundles, social_linkedin, email, and gsuite_tools, work through connected accounts, and Device Control covers the tools those bundles do not reach.
Q13How does the weekly 90-day flight-risk panel work?
The People Analytics Lead scores attrition risk at a 90-day horizon from 14 signals and names the primary driver per employee, the Compensation Specialist flags everyone paid below market P40, and gsuite_tools writes the panel into Sheets behind a human-in-the-loop approval gate. The full run trace shows every input each conclusion used.