A digital business card opening on your phone does not prove that another person can save the name, company, phone and email correctly. The delivery route, browser, operating system and contact application can each change the journey.
Use the English device-test worksheet to check the complete receiving and saving process. It records tested combinations, not universal phone compatibility.
Define the source fields
Prepare full name, organisation, role, phone, email and website. Decide mandatory fields and intentional blanks. Use synthetic details and reserved example addresses so exact values can be compared without exposing personal data.
A contact format can describe these fields without guaranteeing identical display in every application. Add photographs or optional fields after the required set works on the selected combinations.
Test each sharing route separately
Treat a link, QR code, NFC reference, message and email as separate starts. Record whether the recipient first sees a web page, download, preview or warning. Two routes may end at the same address but need different actions to reach it.
Check camera recognition, any NFC confirmation and whether a messaging application preserves the destination. A working destination does not prove a physical NFC interaction. The managed destination belongs to Smart Links; activation and hardware testing are separate boundaries.
Choose a real device matrix
Record model, operating-system version, browser and contact application. Choose combinations relevant to recipients and label others untested. Two successful phones do not establish support for every iPhone, Android device or contact application.
Open, save and find the contact again
Opening is only the first stage. Inspect the preview, intentionally choose the storage account, save and search for the contact in that application. Compare each mandatory field with the source, including country code and organisation name. Check for unexpected merging with an existing contact.
Mark each field correct, changed, missing or extra. Six visible fields in a preview do not prove six stored fields.
Exercise failures and useful alternatives
Try network loss for web destinations, refusing a download and a route without NFC. Provide an alternative that completes the intended task and test it too.
A QR code pointing to the same unavailable website is not an independent network fallback. Visible contact information or an appropriately available contact file may help for the specific fields and devices checked.
Worked example and decision
A fictional card has six mandatory fields. Phone A saves all six. Phone B saves five and loses the organisation. Both open the link, but only A passes the saving test. Five saved plus one missing accounts for B's six expected fields.
The worksheet keeps route, device, version, original value and retrieved value together. Set expectations first and record results after reopening the saved contact. This example is not a physical test of an OmniTechs card.
Record compatibility by tested combination
Approve only the tested combination. Assign a workaround and retest to failures. Repeat checks after a relevant format, route or software change. See Smart Links when one maintained destination needs to support several touchpoints.