Most advice about trade show lead capture is written for American and European exhibitors, and a fair amount of it transfers. Some of it does not, and the parts that do not are exactly the parts that break a process on the second day of a large Indian expo.
This is about the differences: what the cards look like, which channel people actually reply on, how booths are staffed, and the practical bits like invoicing that decide whether a tool gets approved at all.
Start with the vocabulary
Almost nobody in India says business card in conversation. They say visiting card. If your internal documentation, your training for stand staff, or your search advertising uses the international phrasing exclusively, you are slightly out of step with how your own market talks about the object.
It matters more than a style preference. Buyers searching for tooling use the phrasing they speak, which is why our own page for the market is the visiting card scanner guide rather than a translation of the global one.
The cards themselves are different
Four characteristics show up far more often on Indian visiting cards than on the cards most extraction tools were benchmarked against.
The generic email problem deserves particular attention here because it is more prevalent than in Western markets. If three people from one firm all hand you cards printed with info@ their domain, and your deduplication matches on email, you will finish with one record and two lost leads. The handling is covered in why event lead imports create duplicates: treat generic addresses as company addresses rather than as people, and keep those rows separate on the strength of the name.
On bilingual cards, photograph both sides as a rule rather than as an exception. The second side frequently carries a different name spelling and occasionally a different number, and it is not recoverable later once the card is in a drawer.
WhatsApp is not a channel, it is the channel
In most markets WhatsApp is one option among several for business communication. In India it is frequently the default, and treating it as a secondary channel produces worse results than the same approach would elsewhere.
Two practical consequences. First, capture should happen inside WhatsApp rather than in a separate app, because that is the app already open on the phone in your hand, and every app switch is a place where the habit breaks. That is the reasoning behind the WhatsApp capture flow.
Second, follow-up frequently belongs on WhatsApp too, and a follow-up sequence designed for email alone will underperform. The sequence logic from the 48-hour playbook still applies: same-day for the leads that matter, then substance rather than nudges. The channel changes, the discipline does not.
A caution worth stating: business messaging on WhatsApp is subject to platform rules about template messages and opt-in for outbound at scale. Sending individual replies to people who gave you a card is ordinary conversation. Bulk sequencing is a different thing with different rules, and it is worth checking the current position before building a process on it.
Booths are staffed differently
Indian expo stands, particularly at the large industrial and trade fairs, tend to run larger teams and higher footfall than an equivalent Western B2B event. That changes the capture constraint.
On a stand with eight or ten people working it, the single most valuable property is that every capture lands in one list rather than in ten phones. Otherwise the post-show consolidation is a genuine project, and duplicates are guaranteed. That is what shared team capture is for.
The procurement details that decide adoption
A tool can be right and still not get used, because it fails on something unrelated to the product. Three things come up repeatedly.
GST invoicing. Anything expensed needs a compliant invoice with your GSTIN on it, or finance will not process it and the person who bought it will not buy it again. Confirm this before the show, not after.
Payment method. UPI, cards and netbanking cover almost everyone. A tool that only accepts international cards adds friction at exactly the moment somebody is trying to buy quickly before an event.
Rupee pricing. Being billed in dollars introduces exchange rate noise into an expense claim and makes budgeting harder. It is a small thing that produces disproportionate resistance.
Our own pricing is in rupees for India with the payment methods above, and the pricing page lists what each pack covers. The broader point is that these details decide adoption more often than feature comparisons do.
Planning across a season rather than an event
Indian expo activity is seasonal rather than evenly spread, and most exhibitors work a cluster of shows within a few months rather than one every quarter. That argues for a different purchasing shape than a monthly subscription.
This is also why a one-time pack suits seasonal exhibiting better than a subscription. A yearly plan bills through the months you are not exhibiting; a pack sized to the season does not. Reviewing at the end of the cluster rather than after each show also gives you enough data to say something meaningful, using the method in how to tell whether a show was worth it.
Which language to capture in
On a stand where conversations happen in two or three languages, a question comes up that does not arise in single-language markets: what language should the voice note be in?
Capture in whichever language the person speaking is most fluent in. A note recorded in Hindi, Tamil or Marathi by someone thinking in that language contains more detail than the same note laboured through in English, and detail is the entire point. Transcription quality varies by language, but the audio is retained regardless, so nothing is lost even where the transcript is imperfect.
The one thing worth standardising is the field values rather than the notes. Event tags, company names and job titles should go in consistently, usually in English, because those are the fields you will filter and deduplicate on later. Free-text context can be in any language; structured fields should not be.
Brief this explicitly on day one, because the default assumption on a mixed-language stand is that everything should be in English, and that assumption quietly costs you the richest part of the capture from the staff whose English is their third language.
Working with organisers and associations
Indian trade fairs are frequently run by industry associations and chambers rather than by commercial event businesses, which changes what is negotiable and what is available.
Lead retrieval offerings vary enormously as a result. Some large fairs have a sophisticated badge system; plenty of substantial regional shows have nothing at all, and the badge is a printed name tag with no machine-readable element. Assume nothing and check the exhibitor manual, because planning around a scanner that does not exist is a common and avoidable mistake.
Where there is no badge system, cards are the only identifier in the room, which makes card capture the primary method rather than a fallback. That is the inverse of the situation at large Western B2B events and it should shape what you buy before the season starts.
Association-run shows also tend to publish exhibitor and visitor lists, sometimes in advance. That is not a substitute for capture, since it tells you who attended rather than who spoke to you, but it is genuinely useful for pre-show outreach and for filling gaps afterwards.
Follow-up timing around the Indian calendar
The 48-hour rule holds, with one local adjustment worth planning for: the festival and holiday calendar is denser and more regionally variable than in most Western markets, and a follow-up landing in the middle of a regional holiday is a follow-up nobody reads.
Check the calendar for the states your leads are actually in rather than for a national list, because the significant days differ considerably between regions. A message that arrives in Chennai during a holiday that Delhi is working through will simply be missed, and the sender usually reads that as disinterest.
Where a holiday falls immediately after a show, the same-day contact for your top leads becomes more important rather than less, since it is the only message that will land before the gap. Everything else can wait until the following working day without penalty, and sending into the gap is worse than waiting, because you spend the lead's attention when they have none to give.
This applies to the show calendar too. Expo clusters tend to sit around the shoulder seasons, which is part of why buying by season rather than by event works better here.
The short version
Say visiting card. Photograph both sides, because they often differ. Treat generic company email addresses as companies rather than people, or deduplication will merge colleagues. Capture inside WhatsApp, since that is where the phone already is, and expect follow-up to happen there too. Put every staff member’s captures into one shared list, because large stands are the norm. Check GST invoicing and rupee payment before the show rather than after. Buy for the season, not the event, and review across the cluster.
Most of these are small things individually. Together they are the difference between a process that survives a busy day at a large Indian expo and one that quietly stops on the second afternoon.