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

# Close

> Connect DialNexa to Close CRM so every call is automatically logged, leads are updated, and reps see a clean activity feed without manual data entry.

Close is the CRM built for inside sales teams who live on the phone. It's designed around calling, emailing, and speed - which makes it a natural fit for DialNexa. When DialNexa makes calls on your behalf, the outcomes can flow directly into Close: calls logged, leads updated, activities created, and the next step queued up for the rep.

<Note>
  If your team uses Close because they're high-volume callers who track everything by lead and opportunity, DialNexa integrates exactly at that level - call outcomes go onto the right Close lead, not into a generic log.
</Note>

## What this integration does

DialNexa connects to Close through the Close API. After a call, DialNexa can:

* **Log a call activity** on the right Lead - with the recording, duration, outcome, and summary
* **Update Lead status** based on what was captured on the call (Active, Qualified, No Interest, Bad Data, etc.)
* **Create or update Contacts** with the information captured during the call
* **Create follow-up tasks** on the Lead with the right assignee and due date
* **Create new Leads** when a caller doesn't exist in Close
* **Add Lead notes** with the full call context - what the prospect said, what was agreed, and what the rep needs to do next

## When to use DialNexa with Close

**High-volume outbound** - your agent dials through lists at scale. Every answered call is logged in Close as a call activity, the lead status is updated, and a task is created if the rep needs to follow up. Reps don't spend 20% of their day on CRM admin.

**Inbound call handling** - a prospect calls in and the agent qualifies them. Close gets a new Lead with the full context - company, role, pain, timeline, interest level - so the rep who picks it up doesn't start from zero.

**Re-engagement campaigns** - old leads get called. Every outcome - interested again, gone dark, wrong number, changed jobs - updates the Close Lead with the right status and note. The CRM reflects reality instead of last year's best guess.

**Activity logging without rep involvement** - for calls where the agent resolves everything (appointment set, callback booked, DNC request), Close gets the full activity log without a rep needing to log it manually.

## What DialNexa writes to Close

<CardGroup cols={2}>
  <Card title="Call activity logs" icon="phone">
    Every call logged on the Lead with date, duration, direction, outcome, and a summary - including a link to the DialNexa recording and transcript.
  </Card>

  <Card title="Lead status updates" icon="refresh-cw">
    Status updated based on call outcome - Qualified, Not Interested, Bad Data, Connected (no decision), or any custom status your team uses.
  </Card>

  <Card title="Follow-up tasks" icon="check-square">
    Creates a task on the Lead for the assigned rep - with what to do, when to do it, and the context from the call already written in.
  </Card>

  <Card title="Lead notes" icon="file-text">
    Adds a note to the Lead with the full call context - what was said, what was agreed, what the prospect's situation is - in plain language.
  </Card>
</CardGroup>

## Setting up the integration

In your DialNexa agent workflow, add a Close action at call end. You'll configure:

1. **Close API key** - from your Close account settings (set up once in DialNexa integrations)
2. **Action** - log call, update lead, create lead, add note, create task
3. **Record matching** - DialNexa searches Close by phone number or email to find the right Lead
4. **Field mappings** - call variables mapped to Close Lead and Contact fields
5. **Status mapping** - which call outcomes update the Lead to which Close status
6. **Task creation rules** - conditions that trigger a rep task (e.g., only create a task when `call_outcome = callback_requested`)

## Workflow ideas

<AccordionGroup>
  <Accordion title="Power dialing at scale: log without slowing down">
    Your agent calls 300 leads a day. Every answered call gets a Close activity log in real time. Every disposition - connected, no answer, not interested, callback, demo booked - updates the Lead status and creates the right follow-up task. Reps see a clean, current Close feed without touching a keyboard after each call.
  </Accordion>

  <Accordion title="Inbound qualification: create the lead before the rep responds">
    A prospect calls your number. The agent qualifies them in 3 minutes - capturing company, role, pain, and timeline. Before the rep even knows the call happened, Close has a new Lead with the qualification notes already filled in, the status set to Qualified, and a task created for the rep to follow up within 2 hours.
  </Accordion>

  <Accordion title="List cleaning: make your CRM data accurate">
    A 6-month-old lead list gets called. The agent reaches everyone, marks wrong numbers as Bad Data, marks people who've left the company as Stale, updates emails and phone numbers where they've changed, and marks everyone else with their current status. Your Close CRM reflects real-world data in hours instead of weeks.
  </Accordion>

  <Accordion title="Demo confirmation: call, confirm, and close the loop in Close">
    The day before a booked demo, the agent calls the prospect to confirm. If they confirm, Close gets a note: "Demo confirmed for \[date/time]." If they reschedule, Close gets the new details and the rep task is updated. If they cancel, the Lead status changes and the rep is notified immediately.
  </Accordion>
</AccordionGroup>

## Pairing Close with other integrations

* **Close + Slack** - when a high-intent lead comes in or a hot prospect asks to speak to a human, Slack notifies the rep or team channel with the Close Lead link
* **Close + Google Calendar** - when a demo is booked on the call, create the Google Calendar event and log the booking as an activity in Close simultaneously
* **Close + Gmail** - post-call follow-up emails are sent from Gmail and logged as Close email activities so the full communication history is in one place
* **Close + Google Sheets** - export Close activity data to a Sheet for SDR leaderboards, calling cadence reporting, or pipeline health analysis

## Common questions

<AccordionGroup>
  <Accordion title="How does DialNexa find the right Lead in Close?">
    DialNexa searches Close by phone number first. If the number matches a Contact on a Lead, the activity is logged there. If the call captures an email, a secondary search runs on that email. If no match is found, DialNexa creates a new Lead - or routes to review if you prefer to audit new lead creation.
  </Accordion>

  <Accordion title="What does the Close call log look like?">
    A logged call activity on the Lead timeline with the date, duration, direction, and a note containing the call summary - what the prospect said, what was agreed, and what happens next. The DialNexa call recording is linked directly in the activity.
  </Accordion>

  <Accordion title="Can DialNexa update Close Lead statuses automatically?">
    Yes. You define the status transition rules - for example, set to Qualified when `lead_score > 60`, set to Not Interested when `call_outcome = rejected`, set to Bad Data when `call_outcome = wrong_number`. DialNexa applies these automatically based on what it understood from the call.
  </Accordion>

  <Accordion title="Can this work with Close Opportunities as well as Leads?">
    Yes. Close Opportunities (available in Close's Growth and Scale plans) can be created or updated by DialNexa in the same way as Leads - with stage updates, notes, and tasks.
  </Accordion>

  <Accordion title="Can DialNexa create Leads in Close automatically?">
    Yes. When a caller isn't found in Close, DialNexa can create a new Lead with the Contact details captured during the call. You can configure whether new Lead creation is automatic or requires human review.
  </Accordion>
</AccordionGroup>