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

# Companyenrich

> Connect DialNexa calls to Companyenrich for incident, alert, issue, repository, deploy, monitor, log, build, or technical escalation workflows.

CompanyEnrich provides instant company data enrichment, search, and similar company discovery through API endpoints.

<Note>
  Use Companyenrich with DialNexa when a caller reports a technical failure, API problem, broken workflow, regression, outage, or engineering escalation.
</Note>

## Where Companyenrich fits in a DialNexa workflow

Companyenrich should receive DialNexa output when the conversation affects a incident, alert, issue, repository, deploy, monitor, log, build, or technical 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="Connect calls to alerts" icon="check-circle">
    Link customer symptoms to monitors, deployments, incidents, repositories, or on-call ownership.
  </Card>

  <Card title="Avoid noisy escalations" icon="check-circle">
    Separate true incidents from setup questions, product confusion, account configuration, and known limitations.
  </Card>

  <Card title="Create incident-ready reports" icon="check-circle">
    Capture affected customer, service, error, region, severity, start time, workaround, and business impact.
  </Card>

  <Card title="Create reproducible issues" icon="check-circle">
    Record expected behavior, actual behavior, steps, endpoint, screenshots or logs mentioned, and account context.
  </Card>
</CardGroup>

## What DialNexa should capture for Companyenrich

* Customer, account, plan, environment, region, product area, endpoint, and error message
* Severity, business impact, affected users, start time, workaround, and urgency
* Steps described by caller, logs referenced, repo, deploy, monitor, alert, owner, and escalation channel
* Transcript link, recording link, DialNexa call ID, support ticket, CRM account, and status page link
* Privacy note, customer-facing update status, and next update time

## High-value Companyenrich workflows

<AccordionGroup>
  <Accordion title="Status update should be sent after fix">
    For this workflow, DialNexa should send Companyenrich 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="Support needs logs linked to the ticket">
    For this workflow, DialNexa should send Companyenrich 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="Customer reports an outage">
    For this scenario, DialNexa should treat Companyenrich 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="API error blocks a workflow">
    DialNexa should write the symptom, expected behavior, actual behavior, affected area, business impact, and evidence links into Companyenrich. A teammate should be able to triage the issue without replaying the call.
  </Accordion>

  <Accordion title="Deployment regression appears after release">
    For this workflow, DialNexa should send Companyenrich 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="Caller gives reproducible bug steps">
    DialNexa should write the symptom, expected behavior, actual behavior, affected area, business impact, and evidence links into Companyenrich. A teammate should be able to triage the issue without replaying the call.
  </Accordion>

  <Accordion title="On-call needs customer impact">
    For this workflow, DialNexa should send Companyenrich 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 countries">
    Use search countries 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 find similar companies">
    Use find similar companies 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 Companyenrich with other integrations

* [Companyenrich](/integrations/companyenrich) + [GitHub](/integrations/github): GitHub for linked code issues.
* [Companyenrich](/integrations/companyenrich) + [Google Sheets](/integrations/googlesheets): Google Sheets for incident review logs.
* [Companyenrich](/integrations/companyenrich) + [Zendesk](/integrations/zendesk): Zendesk for customer-facing support records.
* [Companyenrich](/integrations/companyenrich) + [Slack](/integrations/slack): Slack for on-call alerts.
* [Companyenrich](/integrations/companyenrich) + [Jira](/integrations/jira): Jira for engineering tasks.
* [Companyenrich](/integrations/companyenrich) + [Google Docs](/integrations/googledocs): Google Docs for incident notes.
* [Companyenrich](/integrations/companyenrich) + [HubSpot](/integrations/hubspot): HubSpot for affected-account visibility.

## Implementation notes

* Use the DialNexa call ID as the idempotency key before running Companyenrich actions.
* Write a short operational summary into Companyenrich 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 the CRM note sound like?">
    Short and factual: who called, why they called, what DialNexa learned, what was promised, who owns the next step, and when it is due.
  </Accordion>

  <Accordion title="Can DialNexa move deal stages automatically?">
    Yes for clear rules such as booked demo, confirmed no interest, or requested quote. Use review for high-value deals, legal blockers, procurement issues, and unclear intent.
  </Accordion>

  <Accordion title="How should low-fit leads be handled?">
    Tag the low-fit reason, suppress from sequences when appropriate, and avoid creating sales tasks that reps will ignore.
  </Accordion>

  <Accordion title="How do we prevent duplicate contacts?">
    Match by phone, email, domain, company name, and open deal before creating or updating records. Store the DialNexa call ID on the activity.
  </Accordion>

  <Accordion title="What fields matter most for sales follow-up?">
    Caller identity, company, pain, urgency, buying role, objection, requested next step, owner, and transcript link.
  </Accordion>

  <Accordion title="How should missed calls be logged?">
    Log missed-call status, voicemail summary if available, retry window, owner, and whether a human callback is required.
  </Accordion>

  <Accordion title="When should Slack be notified?">
    Notify Slack for hot accounts, enterprise prospects, renewal risk, buying intent, escalation requests, or missed VIP callbacks.
  </Accordion>
</AccordionGroup>