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

# Scale ai

> Connect DialNexa calls to Scale ai for vault item, access request, identity check, security review, policy exception, or suspicious-call escalation workflows.

Scale AI provides data labeling and annotation services for machine learning, offering access to a global workforce and sophisticated tools for training AI models with high-quality labeled data.

<Note>
  Use Scale ai with DialNexa when the caller asks for access, recovery, permission changes, vault help, or anything that could expose sensitive systems.
</Note>

## Where Scale ai fits in a DialNexa workflow

Scale ai should receive DialNexa output when the conversation affects a vault item, access request, identity check, security review, policy exception, or suspicious-call escalation. 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="Escalate risky requests" icon="check-circle">
    Flag callers asking for secrets, emergency access, admin changes, recovery help, or unusual account actions.
  </Card>

  <Card title="Keep secrets out of notes" icon="check-circle">
    Store a safe summary and links to restricted evidence instead of writing passwords, tokens, keys, or recovery codes.
  </Card>

  <Card title="Preserve the audit trail" icon="check-circle">
    Attach call ID, owner, decision, timestamp, and review outcome so security can reconstruct what happened.
  </Card>

  <Card title="Route policy exceptions" icon="check-circle">
    Send unusual access requests to the correct security or IT owner with the policy, reason, and urgency attached.
  </Card>

  <Card title="Verify the caller before access changes" icon="check-circle">
    Capture who called, what access they requested, which workspace is affected, and whether identity confidence is high enough for review.
  </Card>
</CardGroup>

## What DialNexa should capture for Scale ai

* Caller identity, organization, role, account, phone, and verification confidence
* Requested permission, policy exception, recovery action, affected system, and severity
* Risk reason, suspicious phrases, urgency, approval requirement, and escalation owner
* Safe summary, transcript link, recording link, DialNexa call ID, and review status
* Redaction flag for secrets, tokens, passwords, keys, or recovery codes

## High-value Scale ai workflows

<AccordionGroup>
  <Accordion title="Security needs a post-call incident note">
    For this scenario, DialNexa should treat Scale ai as an escalation destination. Send the impact, urgency, affected customer or object, owner, and transcript link so the right team can act before the issue gets colder.
  </Accordion>

  <Accordion title="Caller asks for emergency account recovery">
    For this workflow, DialNexa should send Scale ai 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 requests access to a restricted vault">
    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 Scale ai.
  </Accordion>

  <Accordion title="Support needs identity confirmation before sharing private details">
    For this workflow, DialNexa should send Scale ai 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="A caller mentions leaked credentials or phishing">
    For this workflow, DialNexa should send Scale ai 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 create document transcription task">
    Use create document transcription task only when DialNexa has a matched caller, a clear destination object, and enough call context to justify opening a new security record. If the caller is unclear, route to review instead of creating noise.
  </Accordion>

  <Accordion title="Use update task unique id">
    Use update task unique id when the caller changes a field, status, owner, date, priority, note, consent choice, or next step on an existing Scale ai record. Include the old value, new value, and reason from the call.
  </Accordion>
</AccordionGroup>

## Workflows that pair Scale ai with other integrations

* [Scale ai](/integrations/scale_ai) + [Gmail](/integrations/gmail): Gmail for approved follow-up after review.
* [Scale ai](/integrations/scale_ai) + [Zendesk](/integrations/zendesk): Zendesk for the support ticket that triggered the access request.
* [Scale ai](/integrations/scale_ai) + [Slack](/integrations/slack): Slack for urgent review by security or IT.
* [Scale ai](/integrations/scale_ai) + [Jira](/integrations/jira): Jira for longer remediation work.
* [Scale ai](/integrations/scale_ai) + [Google Docs](/integrations/googledocs): Google Docs for audit notes and incident summaries.
* [Scale ai](/integrations/scale_ai) + [Google Sheets](/integrations/googlesheets): Google Sheets for access-review queues.
* [Scale ai](/integrations/scale_ai) + [HubSpot](/integrations/hubspot): HubSpot for account-owner awareness on enterprise customers.

## Implementation notes

* Use the DialNexa call ID as the idempotency key before running Scale ai actions.
* Write a short operational summary into Scale ai 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="What should happen after failed verification?">
    Stop the account-changing workflow, create a restricted review item, and include the attempted request, failed checks, call ID, and escalation owner.
  </Accordion>

  <Accordion title="What belongs in the audit trail?">
    Caller identity, requested action, reviewer, decision, timestamp, policy reason, DialNexa call ID, and links to restricted transcript or recording evidence.
  </Accordion>

  <Accordion title="How should suspicious callers be routed?">
    Tag the risk reason, avoid giving sensitive details, and notify the security or IT channel with the safe summary and evidence links.
  </Accordion>

  <Accordion title="What should stay out of Slack or CRM?">
    Secrets, recovery phrases, private keys, full transcripts, and detailed internal security reasoning should stay in restricted systems.
  </Accordion>

  <Accordion title="Should DialNexa ever store passwords or secrets here?">
    No. Store a safe summary, risk reason, and restricted evidence links. Do not write passwords, recovery codes, tokens, API keys, or private credentials into broad-access records.
  </Accordion>

  <Accordion title="When should a call become a security review?">
    Create a review when the caller asks for account recovery, admin access, permission changes, shared secrets, unusual exceptions, or anything that changes security posture.
  </Accordion>
</AccordionGroup>