> ## 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.

# Rentman

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

Efficiently manage your crew and equipment from one place and ensure nothing falls through the cracks.

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

## Where Rentman fits in a DialNexa workflow

Rentman 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="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>

  <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>
</CardGroup>

## What DialNexa should capture for Rentman

* 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 Rentman workflows

<AccordionGroup>
  <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 Rentman. 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 Rentman. 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 Rentman 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 Rentman.
  </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 Rentman. Sensitive files should stay behind restricted links.
  </Accordion>

  <Accordion title="Offer detail needs review">
    For this workflow, DialNexa should send Rentman 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 delete appointment">
    Treat delete appointment as a controlled workflow. DialNexa should capture the caller's reason, identity confidence, approval owner, and rollback path before anything destructive or irreversible happens in Rentman.
  </Accordion>

  <Accordion title="Use get contact file folders">
    Use get contact file folders 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>
</AccordionGroup>

## Workflows that pair Rentman with other integrations

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

## Implementation notes

* Use the DialNexa call ID as the idempotency key before running Rentman actions.
* Write a short operational summary into Rentman 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 should employee service requests be routed?">
    Classify benefits, payroll, onboarding, access, documents, or policy questions and route to the right owner.
  </Accordion>

  <Accordion title="Should calls be recorded for HR workflows?">
    Follow policy and consent rules. Store recording links only where access is appropriate.
  </Accordion>

  <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>
</AccordionGroup>