▦ Luvox

Contact QR codes

Put your contact details within reach

Share a name, phone number, email, organization and job title through the contact workflow in your workspace. Use it on business cards and event badges.

Make it useful from the first scan.

Choose only the information you want recipients to keep. Test the contact destination on the devices your audience uses, and keep workspace details current.

Choose contact fields people will want to keep

A contact QR workflow helps someone move from a printed card or badge to contact information they can save. Begin with a recognizable name, a useful role and one reliable way to reach you. Adding every possible field makes maintenance harder and may expose personal details unnecessarily. Decide whether the card represents an individual, a shared team or an organization before choosing the phone number and email address.

Contact import behavior differs between phones and applications. Test the actual destination and any save-contact action on the devices your audience uses. Check how international phone prefixes appear, whether the organization and job title land in sensible fields, and whether accented characters remain readable. A working browser preview is not the same as a successful import into a contact application. Ask a colleague to save a sample and then use its email or phone field.

Public business cards can be photographed and forwarded. Publish only information you are comfortable sharing beyond the original recipient. A team mailbox may remain useful longer than an employee's personal address. When responsibilities change, update managed contact details and review any linked profile page. Already imported copies in another person's address book do not automatically become current just because you changed your destination. Explain major changes directly when the relationship requires it, and keep a human-readable name and contact option on the printed card for people who do not use a scanner.

A worked example

An exhibition team prints badges for a shared support desk. The contact destination includes the team name, support mailbox and main office number rather than each volunteer’s private phone. Two colleagues scan a sample badge, save the contact and send a test message. After the exhibition, the team updates the role description to remove temporary hours. The same managed destination stays useful, while the team understands that contacts already saved on visitors’ phones may retain the older text.

Common mistakes to avoid

Prepare, test, then publish.

  1. Choose the destination and check its details.
  2. Generate your code and preserve its white border.
  3. Test the artwork at the intended size, on a real phone.

Keep an accessible alternative such as a short written website address alongside the code. A QR image should make information easier to reach.

Frequently asked questions

Which phones can save the contact?

Device and application behavior varies. Verify the complete save flow on representative iOS and Android devices rather than promising identical imports.

Can I update details later?

You can update a managed contact destination. That change does not remotely edit contacts that recipients have already saved to their own devices.

Should I include my home address?

Only if you deliberately want it shared publicly. For professional cards, a business contact channel is usually a clearer starting point.

Related guides

Create in the workspace ↗

Compare static and managed workflows