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

# Emailable

> Connect DialNexa calls to Emailable for subscriber, audience, campaign, lead source, social profile, ad lead, or lifecycle event workflows.

Emailable provides an email verification API that allows developers to integrate real-time email validation into their applications, ensuring the accuracy and deliverability of email addresses.

<Note>
  Use Emailable with DialNexa when the call reveals intent, consent, objection, channel preference, campaign quality, or a reason to suppress messaging.
</Note>

## Where Emailable fits in a DialNexa workflow

Emailable should receive DialNexa output when the conversation affects a subscriber, audience, campaign, lead source, social profile, ad lead, or lifecycle event. 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="Suppress bad timing" icon="check-circle">
    Remove callers from promo flows when they are in support, billing, cancellation, or complaint mode.
  </Card>

  <Card title="Capture prospect language" icon="check-circle">
    Feed repeated caller wording into ads, landing pages, nurture copy, and FAQs.
  </Card>

  <Card title="Attribute call quality" icon="check-circle">
    Connect campaigns, keywords, pages, ads, or social sources to qualified calls, not just raw volume.
  </Card>

  <Card title="Personalize follow-up" icon="check-circle">
    Use product interest, objection, use case, and requested next step from the call.
  </Card>
</CardGroup>

## What DialNexa should capture for Emailable

* Contact, phone, email, consent, source, campaign, UTM, audience, and lifecycle stage
* Call intent, product interest, objection, segment, sentiment, and conversion outcome
* Suppression reason, unsubscribe or opt-out language, compliance note, and follow-up channel
* Transcript link, recording link, DialNexa call ID, CRM link, order link, and campaign URL
* Quality markers such as qualified lead, spam, vendor, student, support-only, or high intent

## High-value Emailable workflows

<AccordionGroup>
  <Accordion title="Support call should suppress promotions">
    When this happens, DialNexa should mark the record as a suppression or cleanup case in Emailable. 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="Ad lead requests a demo">
    DialNexa should capture the preferred time, timezone, owner, promise made, and contact channel before updating Emailable. The receiving team should see exactly why the follow-up exists and what the caller expects next.
  </Accordion>

  <Accordion title="Caller mentions a competitor">
    For this workflow, DialNexa should send Emailable 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="Prospect repeats a landing-page objection">
    For this workflow, DialNexa should send Emailable 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 asks for product education">
    DialNexa should write the symptom, expected behavior, actual behavior, affected area, business impact, and evidence links into Emailable. A teammate should be able to triage the issue without replaying the call.
  </Accordion>

  <Accordion title="Campaign source needs quality scoring">
    DialNexa should send Emailable the source, consent state, call outcome, audience impact, and suppression or enrollment decision. The goal is better targeting, not another generic campaign touch.
  </Accordion>

  <Accordion title="Qualified caller should enter a campaign">
    In Emailable, 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="Use verify email">
    Use verify email only after DialNexa confirms recipient, consent, channel, message purpose, and the exact follow-up promised during the call.
  </Accordion>

  <Accordion title="Use get account info">
    Use get account info 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 Emailable with other integrations

* [Emailable](/integrations/emailable) + [Klaviyo](/integrations/klaviyo): Klaviyo for ecommerce lifecycle messaging.
* [Emailable](/integrations/emailable) + [Slack](/integrations/slack): Slack for high-intent lead alerts.
* [Emailable](/integrations/emailable) + [Google Sheets](/integrations/googlesheets): Google Sheets for consent and suppression review.
* [Emailable](/integrations/emailable) + [Shopify](/integrations/shopify): Shopify for product and order context.
* [Emailable](/integrations/emailable) + [Gmail](/integrations/gmail): Gmail for human-approved follow-up.
* [Emailable](/integrations/emailable) + [Intercom](/integrations/intercom): Intercom for customer conversation history.

## Implementation notes

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

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