> ## Documentation Index
> Fetch the complete documentation index at: https://dialnexa.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Breezy Hr

> Connect DialNexa calls to Breezy Hr for candidate, employee, job, interview, HR case, onboarding step, or people-operations request workflows.

Integrate Breezy HR to streamline your recruiting and applicant tracking processes.

<Note>
  Use Breezy Hr with DialNexa when candidate or employee calls need careful routing, privacy, scheduling, or HR follow-up.
</Note>

## Where Breezy Hr fits in a DialNexa workflow

Breezy Hr should receive DialNexa output when the conversation affects a candidate, employee, job, interview, HR case, onboarding step, or people-operations request. The handoff should explain what the caller asked for, what DialNexa learned, which record or object is affected, and who owns the next step.

<CardGroup cols={2}>
  <Card title="Route employee requests" icon="check-circle">
    Create cases for benefits, payroll, onboarding, access, documents, or policy questions with the right privacy level.
  </Card>

  <Card title="Protect people data" icon="check-circle">
    Mark compensation, legal, health, identity, or conflict-related details for restricted access.
  </Card>

  <Card title="Schedule interviews cleanly" icon="check-circle">
    Capture availability, timezone, role, interviewer, stage, and reschedule reason.
  </Card>

  <Card title="Summarize candidate screens" icon="check-circle">
    Record fit, motivation, constraints, next step, and review owner without over-sharing sensitive details.
  </Card>
</CardGroup>

## What DialNexa should capture for Breezy Hr

* Candidate or employee name, email, phone, role, department, stage, location, and owner
* Availability, qualification summary, start-date constraint, employee request, urgency, and next step
* Sensitive-data flag, consent note, case category, priority, SLA, and retention note
* Transcript link, recording policy, DialNexa call ID, job link, application link, HR case, and calendar link
* Review requirement for compensation, legal, benefits, payroll, or identity-sensitive details

## High-value Breezy Hr workflows

<AccordionGroup>
  <Accordion title="Hiring manager needs callback">
    DialNexa should capture the preferred time, timezone, owner, promise made, and contact channel before updating Breezy Hr. The receiving team should see exactly why the follow-up exists and what the caller expects next.
  </Accordion>

  <Accordion title="Sensitive people issue needs restricted handling">
    DialNexa should write the symptom, expected behavior, actual behavior, affected area, business impact, and evidence links into Breezy Hr. A teammate should be able to triage the issue without replaying the call.
  </Accordion>

  <Accordion title="Candidate asks to reschedule">
    DialNexa should capture the preferred time, timezone, owner, promise made, and contact channel before updating Breezy Hr. The receiving team should see exactly why the follow-up exists and what the caller expects next.
  </Accordion>

  <Accordion title="Recruiter needs screen summary">
    For this workflow, DialNexa should send Breezy Hr a concise, action-ready handoff: matched caller, affected record, reason for the update, urgency, owner, next step, and links to call evidence.
  </Accordion>

  <Accordion title="Employee has benefits question">
    DialNexa should keep this people workflow minimal and private: identity, role or case, requested next step, owner, timing, and sensitivity flag. Do not copy unnecessary personal details into Breezy Hr.
  </Accordion>

  <Accordion title="Onboarding document is missing">
    DialNexa should attach the relevant file or visual evidence, summarize what the caller says it proves, and mark the review owner in Breezy Hr. Sensitive files should stay behind restricted links.
  </Accordion>

  <Accordion title="Offer detail needs review">
    For this workflow, DialNexa should send Breezy Hr a concise, action-ready handoff: matched caller, affected record, reason for the update, urgency, owner, next step, and links to call evidence.
  </Accordion>

  <Accordion title="Use search candidates by email">
    Use search candidates by email before answering, routing, or creating follow-up. DialNexa should verify the lookup result against the caller and send low-confidence matches to a human queue.
  </Accordion>

  <Accordion title="Use create candidate from resume">
    Use create candidate from resume only when DialNexa has a matched caller, a clear destination object, and enough call context to justify opening a new people record. If the caller is unclear, route to review instead of creating noise.
  </Accordion>
</AccordionGroup>

## Workflows that pair Breezy Hr with other integrations

* [Breezy Hr](/integrations/breezy_hr) + [Slack](/integrations/slack): Slack for recruiter or HR-owner alerts.
* [Breezy Hr](/integrations/breezy_hr) + [Google Drive](/integrations/googledrive): Google Drive for restricted documents.
* [Breezy Hr](/integrations/breezy_hr) + [Notion](/integrations/notion): Notion for interview guides.
* [Breezy Hr](/integrations/breezy_hr) + [HubSpot](/integrations/hubspot): HubSpot for agency or partner context.
* [Breezy Hr](/integrations/breezy_hr) + [Google Sheets](/integrations/googlesheets): Google Sheets for candidate callback queues.
* [Breezy Hr](/integrations/breezy_hr) + [Google Calendar](/integrations/googlecalendar): Google Calendar for interview scheduling.

## Implementation notes

* Use the DialNexa call ID as the idempotency key before running Breezy Hr actions.
* Write a short operational summary into Breezy Hr and link to the full transcript or recording for audit.
* Map required fields before launch: destination object, owner, status, urgency, next step, and record URL.
* Create review paths for low-confidence matches, sensitive requests, high-value customers, and actions that change money, access, legal terms, or customer commitments.

## FAQs

<AccordionGroup>
  <Accordion title="How do we avoid duplicate candidates?">
    Match by email, phone, job, application ID, and existing stage before creating a new record.
  </Accordion>

  <Accordion title="When should HR review be required?">
    Require review for compensation, legal concerns, identity documents, health details, terminations, or employee relations issues.
  </Accordion>

  <Accordion title="What should follow-up emails include?">
    The confirmed next step, time or deadline, owner, and only the details appropriate for the recipient.
  </Accordion>

  <Accordion title="What HR details should be minimized?">
    Compensation, health, legal, identity, conflict, and sensitive employee details should be restricted and summarized carefully.
  </Accordion>

  <Accordion title="Can DialNexa schedule interviews?">
    Yes when availability, timezone, role, interviewer, and stage are clear. Otherwise create a recruiter review task.
  </Accordion>

  <Accordion title="What should a candidate summary include?">
    Role, fit, motivation, constraints, availability, next step, and reviewer. Avoid unnecessary personal detail.
  </Accordion>

  <Accordion title="How should employee service requests be routed?">
    Classify benefits, payroll, onboarding, access, documents, or policy questions and route to the right owner.
  </Accordion>
</AccordionGroup>