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

# Collecting leads

> How capture works in the field, and what to do when it doesn't.

Capture happens in the conversation, not afterwards. A member shares their profile, the visitor fills in the form on their own phone, and the lead exists before anyone walks away.

## The three ways to share

<CardGroup cols={3}>
  <Card title="NFC tap" icon="wifi">
    The visitor holds their phone near the member's Tap tag or card. No app, no scanning, no aiming.
  </Card>

  <Card title="QR code" icon="qrcode">
    The visitor scans a code from the member's phone screen. Works at distance, across a table, and on every phone.
  </Card>

  <Card title="Link" icon="link">
    The member sends their profile URL by message or email. Works remotely.
  </Card>
</CardGroup>

See [Sharing your profile](/en/mobile/sharing) for the member's side.

## What the visitor sees

<Steps>
  <Step title="The profile opens in their browser">
    No app install. Name, photo, title, company, and the member's links.
  </Step>

  <Step title="They fill in the capture form">
    The fields you configured under [Lead capture forms](/en/leads/lead-capture-forms).
  </Step>

  <Step title="They submit">
    The lead is created immediately and appears under **Leads**.
  </Step>
</Steps>

If the visitor is themselves a Tap user, the form can prefill from their profile — they confirm rather than type.

## Capturing without a form

Members can also add a connection manually from the app — useful when someone hands over a paper card, or when a conversation ends before you can share anything. The member types what they have, and the lead behaves identically from then on.

## Making capture reliable at an event

<AccordionGroup>
  <Accordion title="Keep the form short" icon="scissors">
    Four to six fields. Every extra field is a chance for a distracted person in a noisy hall to give up halfway.
  </Accordion>

  <Accordion title="Test on the day, in the venue" icon="vial">
    Capture one lead when you arrive. Venue wifi and crowded mobile networks surface problems your office never will.
  </Accordion>

  <Accordion title="Check CRM access before you travel" icon="plug">
    A department without CRM access captures leads perfectly and syncs none of them. You'll only discover it when you go looking for the records.
  </Accordion>

  <Accordion title="Agree the event tag in advance" icon="tag">
    Decide the tag name before the event so everyone uses the same one, and apply it in bulk afterwards.
  </Accordion>
</AccordionGroup>

## Troubleshooting

<AccordionGroup>
  <Accordion title="The NFC tap doesn't work" icon="wifi">
    Some phones need NFC enabled in settings, and some cases block it. Fall back to the QR code — it works on everything, which is why it's worth having on screen anyway.
  </Accordion>

  <Accordion title="The visitor submitted but there's no lead" icon="user-slash">
    Check the member's app has connectivity and has synced. Captures made offline appear once the device reconnects.
  </Accordion>

  <Accordion title="The lead is in Tap but not the CRM" icon="plug-circle-xmark">
    That's an integration issue rather than a capture one. See [Integration troubleshooting](/en/integrations/troubleshooting).
  </Accordion>

  <Accordion title="Fields the visitor filled in are empty" icon="pen">
    Check whether the member's profile is on a template that defines its own capture fields — template fields override personal ones, so the visitor may have seen a different form than you configured.
  </Accordion>
</AccordionGroup>

<Card title="Next: managing leads" icon="arrow-right" href="/en/leads/managing-leads">
  What to do with leads once they're in.
</Card>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.