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

# Ip2Whois

> Connect DialNexa calls to Ip2Whois for lead, contact, company, deal, activity, task, or account-owner alert workflows.

IP2WHOIS provides a WHOIS lookup API that returns comprehensive domain information, including creation date, updated date, expiration date, domain age, registrant contact information, and nameservers.

<Note>
  Use Ip2Whois with DialNexa when a buyer, customer, partner, or account contact gives information that should change pipeline, ownership, qualification, or follow-up.
</Note>

## Where Ip2Whois fits in a DialNexa workflow

Ip2Whois should receive DialNexa output when the conversation affects a lead, contact, company, deal, activity, task, or account-owner alert. 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 hot accounts" icon="check-circle">
    Notify the owner when an existing account calls with expansion intent, churn risk, procurement questions, or renewal blockers.
  </Card>

  <Card title="Keep CRM hygiene clean" icon="check-circle">
    Search by phone, email, company, and open opportunity before creating new records.
  </Card>

  <Card title="Record the promise" icon="check-circle">
    If DialNexa promises a callback, quote, demo, or email, create a task with owner and deadline.
  </Card>

  <Card title="Qualify callers" icon="check-circle">
    Capture pain, role, budget signal, timeline, objection, source, and next step before a rep follows up.
  </Card>

  <Card title="Move deals with evidence" icon="check-circle">
    Update stage or activity only when the caller confirms intent, decision process, urgency, or blocker.
  </Card>
</CardGroup>

## What DialNexa should capture for Ip2Whois

* Caller name, company, email, phone, source, owner, lifecycle stage, and CRM match confidence
* Qualification answers, pain point, objection, urgency, budget signal, and buying timeline
* Deal stage suggestion, callback window, meeting request, task owner, and due date
* Opt-out, wrong-number, duplicate, student, vendor, competitor, or low-fit flags
* Recording link, transcript link, DialNexa call ID, CRM URL, calendar URL, and email thread URL

## High-value Ip2Whois workflows

<AccordionGroup>
  <Accordion title="Procurement or legal blocker appears on a call">
    For this scenario, DialNexa should treat Ip2Whois 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 a callback from the account owner">
    DialNexa should capture the preferred time, timezone, owner, promise made, and contact channel before updating Ip2Whois. The receiving team should see exactly why the follow-up exists and what the caller expects next.
  </Accordion>

  <Accordion title="Wrong-number or low-fit lead should be suppressed">
    When this happens, DialNexa should mark the record as a suppression or cleanup case in Ip2Whois. Include the exact reason, caller identity, source, and whether future outreach should stop so the team does not keep chasing a bad or unwanted contact.
  </Accordion>

  <Accordion title="Renewal-risk account calls with a complaint">
    For this scenario, DialNexa should treat Ip2Whois 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="Partner or referral lead needs routing">
    In Ip2Whois, this should become a revenue handoff with the matched account, buying signal, stage or owner suggestion, objection, and next action. DialNexa should separate real intent from noise before creating tasks.
  </Accordion>

  <Accordion title="Inbound demo request from a qualified buyer">
    DialNexa should capture the preferred time, timezone, owner, promise made, and contact channel before updating Ip2Whois. The receiving team should see exactly why the follow-up exists and what the caller expects next.
  </Accordion>

  <Accordion title="Use hosted domains lookup">
    Use hosted domains lookup 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 ip2whois domain lookup">
    Use ip2whois domain lookup 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 Ip2Whois with other integrations

* [Ip2Whois](/integrations/ip2whois) + [Intercom](/integrations/intercom): Intercom for support history on existing customers.
* [Ip2Whois](/integrations/ip2whois) + [Zendesk](/integrations/zendesk): Zendesk for support escalation tied to account value.
* [Ip2Whois](/integrations/ip2whois) + [Notion](/integrations/notion): Notion for call playbooks and objection tracking.
* [Ip2Whois](/integrations/ip2whois) + [Google BigQuery](/integrations/googlebigquery): Google BigQuery for pipeline attribution reporting.
* [Ip2Whois](/integrations/ip2whois) + [Gmail](/integrations/gmail): Gmail for the exact recap promised on the call.
* [Ip2Whois](/integrations/ip2whois) + [Google Calendar](/integrations/googlecalendar): Google Calendar for demos and follow-up meetings.
* [Ip2Whois](/integrations/ip2whois) + [Slack](/integrations/slack): Slack for hot-account owner alerts.

## Implementation notes

* Use the DialNexa call ID as the idempotency key before running Ip2Whois actions.
* Write a short operational summary into Ip2Whois 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 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>

  <Accordion title="Should every call create a new CRM record?">
    No. Search contacts, companies, deals, and open tasks first. Create a new record only when the caller is new or the call changes pipeline, ownership, qualification, or follow-up.
  </Accordion>

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