For about thirty years the answer to “how do I send my contact info digitally?” has been the same: a vCard. A .vcf file with your name, number, email, maybe a photo, attached to a message or saved as a download. It still works. But for a growing set of use cases — phone calls, in-person hand-offs, fast deal moments — it’s the wrong shape of thing.
The replacement is something we’ve been calling a contact session: a temporary, two-sided, expiring exchange of contact details that exists only for the duration of a conversation. Here’s what that actually means, and why it works better than a vCard for live moments.
A quick recap of what a vCard is
A vCard is a small text file (.vcf) describing a contact. It can include name, phone, email, organization, photo, address, notes, and so on. It’s a standard (RFC 6350), and basically every contacts app on every operating system can read it.
The strengths:
- It’s portable and standardized.
- It’s a permanent file the recipient can keep.
- It works offline.
The weaknesses, when you actually try to use one in a live conversation:
- It’s an attachment workflow. You email or message a
.vcf. The recipient sees an unfamiliar attachment. On mobile, half the time it opens in a preview rather than offering to save the contact. - It’s permanent. Once you’ve sent it, it lives in the recipient’s mail account, their device, sometimes their cloud backup. No way to take it back.
- It’s static. A vCard sent today reflects today’s number, today’s email. If your number changes next month, last month’s vCard is silently wrong.
- It carries everything or nothing. Sending one is binary: they either get the full file or they don’t. There’s no “share my mobile and email but not my address.”
- It’s awkward on a phone call. The hand-off requires the recipient to open email, find the message, tap the attachment, and accept the import. By the time that’s done, the call is awkward.
What a contact session does instead
A contact session inverts most of the assumptions:
- It exists for a fixed window (commonly 15, 30, or 60 minutes).
- It’s revealed to one specific person, not broadcast.
- It’s field-by-field controllable — you can toggle phone, email, or note off mid-session, and the recipient’s view updates within a second.
- It leaves no permanent footprint on either side. When the session ends, the data is gone from the server. The recipient kept whatever they actively saved.
- It’s designed for the specific moment of exchange, not as a long-lived artifact.
That last point is the conceptual shift. A vCard is a file. A contact session is a moment.
How it works in practice
Here’s the MangoContact flow as a concrete example of a contact session.
- You open mangocontact.com, type your fields (any of: first name, last name, phone, email, free-text note), and pick a session length.
- The server gives you a 6-digit code and one matching emoji.
- You read both to the other person — typically over a phone call.
- They go to mangocontact.com on their device, type the digits, then tap the correct emoji from a small set of options. The emoji is a second factor, so a wrong number who happens to enter your code can’t see your details.
- Your contact card appears on their screen, live. They tap once to call, once to email, once to save.
- The session expires automatically. The encrypted blob is wiped from the server. They keep what they saved; nothing remains shared.
What we did not do, in that flow:
- Send an email
- Send a text
- Send any kind of file
- Create a permanent web page with your number on it
- Require either side to install anything
That’s the difference. The session lives only in the moment of exchange. Detail in our FAQ.
When the session model wins
Contact sessions don’t replace vCards for everything. They win in specific scenarios:
On phone calls. The buyer can’t open a vCard attachment with one hand while listening to you. They can type six digits and tap an emoji.
At in-person moments. Coffee shops, conferences, showings. Reading out a code is faster than fumbling AirDrop or “let me find your number on LinkedIn.”
For sensitive numbers. A personal mobile that you don’t want sitting on a public profile or in someone’s email backups.
For per-conversation context. Sessions can carry a free-text note (“ref MLS-4421” or “second number is the office”) that wouldn’t make sense on a permanent vCard.
For ad-hoc hand-offs. No need to update anything when your number changes — just generate a new session next time.
When vCards still win
Sessions don’t replace vCards for:
- Long-lived professional profiles
- Bulk contact transfers between systems
- Email signatures
- Anywhere you need an offline file
If your boss asks you to email them everyone’s contact info from a recent meeting, you’re still sending vCards. That’s fine.
The clean rule of thumb
Use a vCard for “here’s a record of me.”
Use a contact session for “here’s how to reach me right now, for this conversation.”
The first is a file. The second is a handshake.
Most of the friction in modern contact exchange — dictating digits on phone calls, awkward .vcf attachments, fumbling AirDrop — is what happens when you use the file model for a handshake moment. Reach for the right tool, and the awkwardness disappears.
Mango it.