How to Capture and Export Leads From Your Digital Business Card
A digital business card shouldn't just share your details; it should capture the details of the people who view it. AtlasLinq's lead capture turns every profile view into a potential contact you can follow up with, and the admin dashboard lets you review and export those leads (or push them to your CRM). Here's how it works, end to end.
What Lead Capture Does
When someone opens your AtlasLinq share page, they can leave their own contact details through a capture form, typically their name, email, phone, and a short message. Each submission becomes a leadattached to your account. Instead of a one-way exchange where only the recipient gets your info, you both come away with a contact.
Step 1: Make Sure Capture Is Active on Your Card
Lead capture appears on your share page so visitors can reach out. On an Enterprise team, capture works across every member's card, and all the leads roll up to the admin dashboard. Share your card as you normally would, by NFC tap, QR code, or link, and any visitor can submit their details.
Collecting and reading are two different things
Worth being clear about before the rest of this guide, because it is the part people get wrong: your card collects leads on every plan, Essential included. There is no monthly capture quota to run out of. A submission that arrives while you are on the free plan is stored the same way as one that arrives after you upgrade.
What the plan decides is how many of them you can open. Essential shows you a count and the date of the most recent one, without the contact details. Pro opens the 25 most recent in full. Enterprise opens all of them, across every member of the team, and adds the CSV export and CRM sync covered below.
The practical consequence: if you have been handing out a free card at events, the contacts people left you are not lost. They are waiting.
Step 2: Review Leads in the Dashboard
Sign in at atlaslinq.com/dashboard and open the Leads section. You'll see your captured contacts ordered by most recent, each showing the details the visitor provided:
- Name and email
- Phone (if provided)
- Message (if they left one)
- Which profile the lead came from, and on a team, which member
- The date it was captured
On an Enterprise team this is especially useful: you can see at a glance which member's card generated each lead, so the right person follows up.
Step 3: Export Your Leads to CSV
From the Leads page, use Export CSV to download your contacts as a spreadsheet. The file arrives named for the day you pulled it, and the columns are fixed:
| Column | Contents |
|---|---|
| Name, Email | Always present. Both are required before a lead can be submitted. |
| Phone, Message | Optional, so these are often blank. |
| Profile | Which of your cards the visitor was looking at. |
| Member | Only appears when the export contains team leads. |
| Date | When it was captured. |
One detail worth knowing before you rely on it: the export pulls every lead you have, not just the ones currently loaded on screen. The Leads page pages through your history as you scroll, so an export that only covered the visible rows would quietly hand you a truncated file after an event, which is exactly when you would not think to check.
What the form will and will not accept
The capture form is public, so it is defended rather than trusting. Two things follow from that, and both occasionally surprise people.
Fields are length-capped. A message runs to 500 characters, a name to 100, an email address to 254, and a phone number to 30. These are generous for the job, but someone pasting a paragraph will hit the message cap.
Submissions are also rate limited per day, in two layers: a single visitor can leave at most three submissions against one card, and a single card accepts at most two hundred in a day across everyone. The first stops one person filling your inbox. The second stops a distributed flood from doing it through many addresses, and protects the sync quota on whatever CRM you have connected downstream. At a busy stand you will not come close to either.
Step 4: Send Leads to Your CRM
AtlasLinq is built to connect with the tools you already use. The dashboard supports moving your captured contacts into popular CRMs and contact managers:
| Destination | Use it for |
|---|---|
| Google Contacts | Keep new contacts synced across your Google account |
| Zoho CRM | Push leads into your sales pipeline |
| HubSpot | Feed inbound contacts into marketing and sales workflows |
If you connect a CRM, the sync matches on email address and updates the existing record rather than adding a second one, so the same person captured at two events normally lands as one contact with newer details rather than a duplicate for somebody to merge later. Treat that as very good rather than guaranteed: matching depends on the CRM finding the existing contact, and a lookup that comes back empty is treated as a new person. Setting up CRM sync covers the connection itself.
Asking for someone's details without being strange about it
Lead capture asks a stranger to type their email into a form on a phone they are holding at a noisy event. Whether they do it is mostly about the thirty seconds before they look at the screen, not about the form.
Give a reason that is specific and true. "Leave your email and I will send you the deck we were talking about" works. "Stay in touch" does not, because it describes a cost with no benefit. If you have nothing to send, it is usually better to take their card the traditional way and not ask.
Say what happens next, then do that. Someone who fills in a form expecting one follow-up email and receives a newsletter has been added to a list they did not agree to join, which in several jurisdictions is also a legal problem rather than only a rude one. The message box is the useful field here: ask them to note what they wanted, and your follow-up writes itself.
The first forty-eight hours
Follow-up decays fast, and the decay is about memory rather than interest. Two days after a conference, someone remembers the conversation. A week later they remember neither your name nor which of thirty conversations was yours.
- Same evening. Open the Leads page while the day is still legible to you and add nothing but a note to yourself against the names you cannot place. This is the step people skip, and it is the one that makes the rest possible.
- Next morning. Send the specific thing you promised, referencing where you met and what you talked about. One paragraph. No attachment they did not ask for.
- Within two days. Export or sync, so the record leaves your head and enters the system you actually work in.
- After that. Anyone who has not replied gets one more message, later, with something new in it. Not a nudge about the previous message.
Why It Matters
Paper cards are a one-way street: you hand them out and hope. Lead capture flips that: every view is a chance to get the other person's details too, attributed to the right card and ready to export or sync. For teams, it means no lead falls through the cracks, because everything lands in one central dashboard.