Indian-language business cards: what breaks before you even follow up

Card scanning demos are always run on the same card: a clean, matte, English-language card with a two-line address and a nice sans-serif face. Indian exhibition stacks do not look like that.

A realistic stack has a Devanagari company name above a Latin-script email, a designation that only makes sense locally, a landline with an area code and a mobile without one, and at least three cards printed on something reflective. When capture goes wrong, it goes wrong here.

A mangled name is worse than no record

This is the part that gets underestimated. A missing record is a gap you can notice and fix. A wrong record is a follow-up that goes out addressed to a garbled version of someone's name, and it lands as carelessness at exactly the moment you were trying to demonstrate the opposite.

Somebody whose name has been transliterated into nonsense does not reply to tell you. They just do not reply.

The four things that actually break

1. Mixed scripts on one line. A company name in Devanagari followed by "Pvt. Ltd." in Latin. Tools that detect one language per card tend to drop whichever half loses the vote.
2. Transliteration instead of translation. A name should be transliterated so it sounds right in Latin script; a company name often should not be translated at all. Getting this backwards produces the classic literal-translation company name that no search will ever match.
3. Titles and honorifics read as names. Prefixes and suffixes vary by region and language, and a scanner that does not know them will happily file a title as a first name.
4. Phone number shapes. Indian cards carry a mix of ten-digit mobiles, landlines with two-to-four-digit area codes, numbers with +91 and numbers without, and separators that are spaces, hyphens or nothing. Normalising these wrongly gives you numbers that fail silently when you message them.

A five-minute test to run before the event

Do this on whatever you are planning to use, well before you are standing in a hall. Take four cards from your own drawer:

1. One entirely in English, as a control.
2. One with a Devanagari company name and Latin-script contact details.
3. One that is glossy or foil-printed, photographed under bad light.
4. One with a designation that is specific to your industry.

Then check three things on each result, in this order:

• Is the name right, character for character? Not close. Right.
• Is the phone number dialable as captured? Paste it into your phone and see.
• Did anything get silently dropped? A missing second phone number or a lost designation is the failure you will not notice until you need it.

Test on the cards you will actually collect, not on the card the demo used.

What to do with the ones that still fail

No capture method will be perfect, so decide in advance what happens to the failures rather than letting them sit in a sheet looking like real records.

• Keep the photo of the card attached to the record. It is the only source of truth when a field looks wrong.
• Flag low-confidence records rather than deleting them, and fix those first.
• When a name is uncertain, write the message so it works without it. A greeting that avoids a mangled name is far better than one that uses it.

The part nobody budgets for

There is a hidden cost in all of this: six or more hours per event spent retyping and correcting cards. That work reliably slips, which is how roughly 73% of event leads end up never being followed up at all. The language problem is not just an accuracy issue. It is one of the reasons the whole follow-up step gets abandoned. The first 48 hours after an event looks at what that delay costs.

Where Rizely fits

Reading Indian-language cards is one of the things Rizely does that the global scanners generally do not. It is a WhatsApp- and Telegram-native AI agent: you photograph the card in the chat app you already have open, including cards that mix Devanagari with Latin script, and it becomes a clean, event-tagged lead with the follow-up sent automatically.

It is the only tool that captures the card and sends the follow-up, in Indian languages, priced per event. Run the five-minute test on it with your own cards before an event, the same as you would with anything else — that is the honest way to find out whether it handles your stack.

If you are still deciding how to run the booth itself, the booth setup checklist covers the decisions worth making before the doors open.