> ## Documentation Index
> Fetch the complete documentation index at: https://docs.meetdarwin.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Follow up when a visitor leaves

> Use captured contact details without confusing them with a booked meeting.

<div className="darwin-location"><strong>Find it in Darwin</strong> Conversations → Contacts filter <a href="https://app.meetdarwin.ai/admin/conversations?filter=leads">Open this screen ↗</a></div>

A visitor can leave their name and email before finishing the calendar flow. That makes a follow-up possible even when there is no recorded booking.

<Steps>
  <Step title="Review the contact’s conversation">
    Open the contacts filter in Conversations. Read what the visitor wanted and whether a meeting has already been recorded before reaching out.
  </Step>

  <Step title="Export the relevant contacts">
    Select **Copy follow-up list** when available to copy the contacts as CSV. The copied list covers eligible contacts in the displayed list who do not have a recorded booking. Search and loaded-list limits affect the scope; it is not an export of every historical customer record.
  </Step>

  <Step title="Use your existing follow-up process">
    Import the CSV into your approved CRM or outreach workflow and follow your team’s consent and contact preferences. Tailor the message to the actual question rather than sending a generic pitch.
  </Step>
</Steps>

## Avoid duplicate outreach

Check your scheduling provider if the conversation outcome looks incomplete. A person may have booked even when completion tracking did not reach Darwin. Use the provider’s appointment record to resolve the discrepancy before contacting them again.

<Note>The current workspace provides a CSV follow-up workflow. Automatic HubSpot or Salesforce synchronization and enrollment into email sequences are not configured through these screens. Confirm any separately arranged integration before relying on it.</Note>

[Check missing booking outcomes →](/help/booking-troubleshooting)