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

# Scanning

> Capture leads from business cards, QR codes, and event badges.

Not everyone you meet will tap your profile. The scanner covers the rest: someone hands you a card, wears a conference badge, or shows a QR code of their own.

## Three scan modes

<CardGroup cols={3}>
  <Card title="Business card" icon="address-card">
    Point the camera at any business card. Tap reads it and fills in the lead for you.
  </Card>

  <Card title="QR code" icon="qrcode">
    Point at any QR code — another Tap profile, or a third-party contact code.
  </Card>

  <Card title="Event badge" icon="id-badge">
    Point at a conference badge. Useful where badges carry more reliable data than the cards people are handing out.
  </Card>
</CardGroup>

You can also upload an image from your gallery instead of using the camera — handy for a pile of cards photographed earlier, or a card someone emailed you.

## Scanning a business card

<Steps>
  <Step title="Open the scanner">
    From the app, choose to scan a business card.
  </Step>

  <Step title="Capture the card">
    Point the camera at it, or upload a photo from your gallery.
  </Step>

  <Step title="Review the extracted data">
    Tap shows you what it read before saving. **Check it.** This is the step people skip and regret — an email address misread by one character is a lead you can never contact.
  </Step>

  <Step title="Save">
    The lead is created and behaves exactly like one captured through a form — it scores, syncs to your CRM, and accepts meetings and follow-ups.
  </Step>
</Steps>

## Getting good scans

<AccordionGroup>
  <Accordion title="Light matters more than steadiness" icon="sun">
    Most failed scans are underlit rather than blurry. Step toward a window or a bright stand light before blaming the camera.
  </Accordion>

  <Accordion title="Fill the frame with the card" icon="crop">
    A card occupying a quarter of the frame gives the reader far less to work with than one that fills it.
  </Accordion>

  <Accordion title="Flat, not angled" icon="ruler-horizontal">
    Hold the card flat and shoot straight on. Perspective distortion is the second most common cause of garbled text.
  </Accordion>

  <Accordion title="Unusual layouts read worst" icon="palette">
    Heavily designed cards — text over photos, vertical layouts, low-contrast foil — are the hardest. Review those extractions especially carefully.
  </Accordion>
</AccordionGroup>

## Saving to your phone contacts

A captured lead can also be saved into your phone's own contacts, so they're reachable from your dialler without opening Tap.

<Note>
  This copies the contact to your phone. It doesn't link the two — later edits in Tap won't update your phone contact, and vice versa.
</Note>

## Scanning versus tapping

Scanning is the fallback, not the default. A lead captured through your own form is better in two concrete ways: the visitor typed their own details, so there are no reading errors, and you get whatever custom fields you configured rather than only what fits on a card.

<Tip>
  When someone offers you a card, take it — then share your profile back and let them fill in the form. You end up with both: their card as a backup and a clean captured lead.
</Tip>

<Card title="How scoring works" icon="arrow-right" href="/en/leads/lead-scoring">
  Scanned leads are scored on the same rules — and missing fields cost points.
</Card>


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