AMPROFEC's annual study calculates 170 contacts per exhibitor per event, and CEIR documents that only 39% of trade show leads end up qualified. The difference between a show that pays for itself and one that was just an expense is not the booth: it is what the team does in the next 72 hours, while the memory is still there and the competitor hasn't written yet.
Short answer: In the first 72 hours you need to segment contacts into four groups, write to the hot group within 24 hours quoting their exact words, send something useful to the warm group at 48 hours, nurture the cold group at 72, load everything into the CRM with source and consent tagged, and create the 30- and 90-day reactivation tasks before you move on.
- Why is the value lost in the first 72 hours?
- The four groups: how to segment contacts before you write
- Day 0: closing night, hour by hour
- Day 1: the first 24 hours
- Days 2 and 3: the warm group, the cold group and closing the window
- Email sequence, ready to copy
- WhatsApp sequence: templates, consent and the conversation window
- How do you use AI to personalize at scale without sounding automated?
- CRM loading and data cleanup
- Dividing the work and filling the meeting calendar
- Reactivation at 30 and 90 days
- How to measure the event's return: formula and example
- Typical post-show follow-up mistakes
- Tricks that aren't in the manual
- What to do this week
Why is the value lost in the first 72 hours?
Because memory fades faster than interest. Whoever talked to you also talked to twenty other exhibitors in three days: after 72 hours they no longer remember your company — at best they remember one sentence. If your first message lands on Monday saying "it was a pleasure meeting you at the show," you're asking them to do the work of remembering. Almost nobody does.
And there's a second, more mundane reason: the team comes back exhausted, with a backlog of email and operations waiting. Follow-up gets pushed to "once I catch up," and that moment arrives two weeks later, when the contact has already talked to your competitor.
The Annual Exhibition Industry Study by AMPROFEC, released in June 2024 with 2023 data, calculates an average of 170 contacts per exhibitor per event in Mexico. And the report How Exhibitors Can Improve Lead Quality and Sales Conversion, published in 2019 by CEIR, documents that only 39% of trade show leads end up qualified against the exhibitor's own criteria (CEIR figure from 2015).
Put the two figures together: roughly 170 contacts of which perhaps 66 are worth pursuing, and a tired team that has to separate them, write to them and book meetings. Without a written process, the selection is made by chance: you work the people you remember, not the ones most likely to buy.
The good news: 72 hours is more than enough if the process is set up before you travel. Pre-show preparation and booth capture are covered in the trade show and lead capture guide.
The four groups: how to segment contacts before you write
Before you draft a single line, contacts get split into four groups. Each one gets a different message, on a different timeline, through a different channel: writing the same thing to everyone is the fastest way to burn an entire list.
| Group | How to recognize it | First-contact deadline | Channel and goal |
|---|---|---|---|
| A — Hot | Specific, quantified problem with a decision window inside six months | Under 24 hours | WhatsApp or call + email. Goal: a meeting with a date and time |
| B — Warm | Real problem but a distant window or no identified decision-maker | 48 hours | Email with something useful. Goal: a second conversation |
| C — Cold | Genuine interest with no defined problem; also partners and channel | 72 hours | Nurture email. Goal: stay on the radar |
| D — Disqualified | Students, vendors, competitors, out-of-scope profiles | No sales follow-up | Recorded and flagged, so nobody works them twice |
A healthy split is usually 10 to 20% in group A and 30 to 40% in B; the rest, C and D. If you come out with 60% hot you aren't qualifying, you're being optimistic; if you come out with 2%, either the show was the wrong choice or the booth script didn't ask what it should have.
A fifth group that isn't a group: current customers who stopped by to say hello. They go on a separate list and are handled by whoever owns the account; mixing them in with cold leads is the segmentation error that irritates a customer most.
The rating has to come in already done from the booth, as a required field on the form. If you come back with 170 unclassified records, day 0 disappears into sorting them.
Day 0: closing night, hour by hour
Day 0 is the late afternoon and evening of the show's last day: 90 to 120 minutes, at the hotel, and it's the most profitable stretch of the entire event.
- First 20 minutes — consolidate. Every record in a single file: digital form, the organizer's lead retrieval export, photos of business cards, voice notes. One single source of truth.
- Next 20 minutes — transcribe. Voice notes to text, dropped into each contact's context field. With AI it's minutes; by hand it never happens.
- Next 20 minutes — classify and assign. Records without an A/B/C/D group get resolved now, with the team in the room, and every A and B contact is assigned to a person by name. No owner, no follow-up.
- Last 20 minutes — fire off the acknowledgment. A short message to the whole A group, that same night. It isn't the proposal: it's the signal that you exist.
Day 0 message (WhatsApp, group A contact with consent)
Spanish version — send this one:
Hola [nombre], soy [tu nombre] de [empresa]. Nos vimos hoy en el stand [número] de [feria] y quedamos en lo de [tema exacto que mencionó].
Le escribo antes de que se me pierda entre tantos contactos: mañana le mando el detalle de [lo prometido]. ¿Le viene bien que lo llame el [día] a las [hora] para verlo en quince minutos?
English translation — for reference:
Hi [name], this is [your name] from [company]. We met today at booth [number] at [show] and talked about [the exact topic they raised].
I'm writing before it gets lost among so many contacts: tomorrow I'll send you the details on [what you promised]. Would it work if I called you on [day] at [time] to go through it in fifteen minutes?
Two things make it work: it arrives the same day, while you're still in their head, and it contains "the thing about [exact topic]" — the phrase you wrote down verbatim at the booth, which acts as a memory key. Without it, the message is indistinguishable from the other nineteen they're about to get.
If the day ran long, cut it down: consolidating and firing off the group A acknowledgment are the non-negotiable steps.
Want a hand applying this?
Free 30-minute working session. Uniamos is a remote AI automation agency (Austin and Mexico City) working over video calls and WhatsApp.
Day 1: the first 24 hours
Day 1 is the day after the show closes, even if that's a Saturday. Three blocks and one goal: every group A contact either has a meeting booked or an open conversation.
| Block | What happens | Who |
|---|---|---|
| Morning (2 h) | Data cleanup, deduplication and CRM load with the source field tagged | Whoever administers the CRM |
| Late morning (2 h) | Personalized one-to-one email to the whole A group, with what you promised attached | The rep who owns each contact |
| Afternoon (2 h) | Calls to the group A contacts who didn't reply to the email | The same rep |
The order matters: first the email with what you promised —quote, spec sheet, a concrete case— then the call. That way the call has a reason: "I sent over what we talked about, did you get a chance to look at it?"
What you promised gets delivered to the letter. If you said "I'll send you a proposal," you send a proposal, not a catalog. The first broken minor promise tells the person on the other side exactly what working with you will be like.
The three-line rule: the day 1 email doesn't run past three lines of body copy plus the attachment. Nobody reads a long email from someone they met in an aisle yesterday; the proposal goes in the attachment and the email only has to get it opened.
At the end of the day, three numbers in the team channel: contacted, replied, meetings booked. One message, no follow-up meeting about it.
Days 2 and 3: the warm group, the cold group and closing the window
Day 2: the warm group and the first meetings
Day 2 splits between closing out what's open in group A and starting on B, the biggest group and the one that takes the most discipline because it has no urgency of its own.
- Morning: second attempt with the hot leads who didn't reply. Switch channels —if you sent email, now use WhatsApp— and switch angles: don't resend the same message with exclamation marks.
- Late morning: send the group B email. Here a template with merge fields is fine, because the volume demands it, but with at least three personalized elements: name, company and the topic they raised.
- Afternoon: the first booked meetings from group A. Yes, that soon: the closer to the event, the fresher the conversation and the better the show-up rate.
What goes in the group B email. Not a proposal —there isn't enough information to write one yet— but something that solves a piece of their problem: a guide, a calculation, a comparison. The goal isn't to sell, it's to earn the second conversation.
The day 2 mistake is spending all your time on group A, which is the exciting one, and leaving B for "next week." B is what sustains next quarter's pipeline: the hot leads, by definition, were already buying. Block the hours for B on your calendar as if they were customer meetings.
Day 3: close the loop and shift to normal pace
Day 3 closes the 72-hour window. By the end of the day, no contact from the event should still be untouched.
- Group C: a nurture email, one single send, with your best content and a clear invitation to reply. No pressure, no aggressive sequence.
- Group D: closed in the CRM with a disqualification reason. It sounds bureaucratic and it stops someone from prospecting, six months from now, the competitor who wandered by to have a look.
- Third attempt on group A: the last one in this window. With no reply after three attempts across two channels, the contact drops to group B. You don't push six times in a week.
- Closing report: the event's numbers to sales leadership, on one page.
72-hour closing checklist
- ☐ All records loaded into the CRM, deduplicated and with source tagged
- ☐ The four groups assigned, with a named owner for A and B
- ☐ Group A: three touches across at least two channels
- ☐ Group B: email sent with something useful
- ☐ Group C: nurture email sent
- ☐ Group D: closed with a reason
- ☐ Meetings booked, with invitations sent
- ☐ 30- and 90-day reactivation tasks already created in the CRM
- ☐ Event report delivered
The second-to-last box is the one almost nobody checks and the one worth the most: the reactivation tasks get created now, with a future date and a note that will actually help the version of you that reads it in a month. In a month, nobody remembers to create them.
Email sequence, ready to copy
Three sequences, one per group. Change the tone so they sound like you, but keep the structure: specific context, value, and a single ask at the end.
Group A — email 1 (day 1)
Spanish version — send this one:
Asunto: [tema que mencionó] — lo que quedamos en [feria]
Hola [nombre]: ayer me comentó que [frase textual que dijo en el stand]. Le adjunto [lo prometido] con el detalle para [su caso concreto].
Tengo hueco el [día] a las [hora] o el [día alternativo] a las [hora] para revisarlo en quince minutos. ¿Cuál le sirve? [firma con teléfono directo]
English translation — for reference:
Subject: [topic they raised] — what we agreed at [show]
Hi [name] — yesterday you mentioned that [their exact words at the booth]. I'm attaching [what you promised], with the details for [their specific case].
I have a slot on [day] at [time] or [alternative day] at [time] to go through it in fifteen minutes. Which works for you? [signature with direct phone number]
Group A — email 2 (day 3, if there was no reply)
Spanish version — send this one:
Asunto: Re: [mismo asunto]
Hola [nombre]: imagino que la vuelta de la feria viene cargada. Una sola pregunta para no robarle tiempo: ¿[el tema que mencionó] sigue siendo prioridad este [trimestre], o lo retomamos más adelante? Si es lo segundo, le escribo en [mes] y listo.
English translation — for reference:
Subject: Re: [same subject line]
Hi [name] — I imagine the week back from the show is a busy one. Just one question so I don't take your time: is [the topic they raised] still a priority this [quarter], or should we pick it up later? If it's the latter, I'll write again in [month] and leave it there.
Group B — email 1 (day 2)
Spanish version — send this one:
Asunto: Lo que hablamos sobre [tema] en [feria]
Hola [nombre]: nos cruzamos en el stand [número] de [feria] y me quedé con lo que comentó sobre [tema].
Le dejo [recurso concreto: guía, calculadora, comparativa] que aborda justo eso. No hace falta que conteste; si quiere ver cómo se aplica a [su empresa], respóndame con una línea.
English translation — for reference:
Subject: What we discussed about [topic] at [show]
Hi [name] — we ran into each other at booth [number] at [show] and what you said about [topic] stuck with me.
Here's [a specific resource: guide, calculator, comparison] that addresses exactly that. No reply needed; if you'd like to see how it applies to [their company], just send me one line back.
Group C — single email (day 3)
Spanish version — send this one:
Asunto: Gusto en saludarlo en [feria]
Hola [nombre]: le dejo [el mejor recurso que tengas sobre el tema del evento] por si le resulta útil.
Si en algún momento necesita [lo que haces], aquí estoy. Le escribo cada tanto solo si tengo algo que realmente valga su tiempo.
English translation — for reference:
Subject: Good to meet you at [show]
Hi [name] — here's [the best resource you have on the event's theme] in case it's useful.
If you ever need [what you do], I'm here. I'll only write now and then, and only when I have something genuinely worth your time.
Two rules matter more than the templates. One ask per email: if you ask them to book a meeting, answer a survey and download something, they do none of it. And the subject line names the topic, not the show: "Re: Expo 2026" gets archived, "Waste on the packaging line" gets opened.
WhatsApp sequence: templates, consent and the conversation window
In Mexico and Paraguay, WhatsApp is where the sales conversation actually happens — and also where it's easiest to burn yourself: the channel is personal and tolerance for unsolicited messages is zero.
Two conditions before you type the first word: explicit consent, collected at the booth with its own checkbox for the channel, and approved templates. The WhatsApp Business Platform requires business-initiated messages —those that aren't replies inside a conversation the contact already opened— to use a previously approved template, per Meta's official documentation. Check there for current timeframes and categories.
The practical consequence: templates get submitted for approval before the show. If you wait until you're back, the 72 hours disappear into paperwork. With an official provider like 360dialog or Twilio, they handle the registration; the process is in the guide to AI agents on WhatsApp Business.
Template 1 — acknowledgment, day 0 (group A)
Spanish version — submit and send this one:
Hola {{1}}, soy {{2}} de {{3}}. Nos vimos hoy en {{4}} y quedamos en {{5}}. Mañana le envío el detalle por correo. Si prefiere que lo llame, dígame qué hora le sirve.
English translation — for reference:
Hi {{1}}, this is {{2}} from {{3}}. We met today at {{4}} and agreed on {{5}}. I'll email you the details tomorrow. If you'd rather I call, just tell me what time works.
Template 2 — meeting request, day 1
Spanish version — submit and send this one:
Hola {{1}}, le envié al correo {{2}} lo que conversamos sobre {{3}}. ¿Le sirve una llamada de quince minutos el {{4}} a las {{5}}? Si no, dígame dos horarios y me acomodo.
English translation — for reference:
Hi {{1}}, I've emailed {{2}} what we discussed about {{3}}. Would a fifteen-minute call on {{4}} at {{5}} work? If not, give me two times and I'll fit around you.
Template 3 — soft close, day 3
Spanish version — submit and send this one:
Hola {{1}}, no quiero insistir de más. ¿{{2}} sigue siendo prioridad este {{3}} o lo retomamos más adelante? Con una palabra me basta.
English translation — for reference:
Hi {{1}}, I don't want to keep pushing. Is {{2}} still a priority this {{3}}, or should we pick it up later? One word is all I need.
Three rules of the trade: one question per message, because people reply on WhatsApp with their thumb; no voice notes on first contact — from a stranger they land as an intrusion; and an easy way out in the third message —"if you'd rather I didn't message you here, we can move to email"— which preserves relationships that otherwise end in a block.
Disclaimer: operational best practice, not legal advice. Personal data and commercial communication requirements differ between Mexico and Paraguay; review them with your advisor. For Paraguay specifically, see the guide on customer data and AI.
How do you use AI to personalize at scale without sounding automated?
The trick isn't asking AI for pretty emails. It's giving it the specific material from each conversation and asking it to fill in a structure you defined. The difference between an email that sounds automated and one that sounds human isn't style, it's the concrete detail only someone who was there could know. That's why the "their exact words" field on the capture form is worth more than all the others combined.
Prompt 1 — draft in batches
"Here's a CSV of contacts from the [name] trade show, with columns: name, company, job title, group (A/B/C), need identified, time window, and their exact words.
Write an email for each contact in group [X] with exactly this structure: 1) a subject line naming the topic they raised, without mentioning the show; 2) a first line that quotes or paraphrases their exact words; 3) one line on what I'm bringing them; 4) a single ask, with two specific time slots.
Rules: write in neutral Latin American Spanish, informal 'tuteo'; maximum 90 words of body copy; and the following are banned: 'espero que este correo te encuentre bien,' 'sinergia,' 'solución integral,' 'no dudes en,' and exclamation marks. If a contact has no exact-words field, write 'FALTA CONTEXTO' instead of inventing something. Return it as CSV with 'asunto' and 'cuerpo' columns."
The instruction to write "FALTA CONTEXTO" instead of inventing is what saves the whole system: without it the model fills the gap with a plausible generality, and that well-written email is precisely the one that gives away that nobody was paying attention.
Prompt 2 — audit before sending
"Review these [N] emails as if you were the recipient: a busy manager who got back from a trade show yesterday. For each one, answer: is it clear in five seconds who's writing and why? is there any detail only someone in that conversation would know? is there a single ask, and is it easy to answer? Mark LOW any that sound like a template and explain in one line what's missing."
The last-mile rule: no group A email goes out without a person reading it and changing at least one thing. That's twenty or thirty contacts and twenty minutes of review. For B and C it's enough to review a sample of ten and fix the pattern. If you work inside an AI workspace loaded with your catalog and your tone of voice, quality rises on its own: how to set that up is in the guide to prompts for sales teams.
CRM loading and data cleanup
A trade show list always arrives dirty: names in all caps, misspelled emails, the same company duplicated under three spellings, phone numbers with no country code. Loading it as-is contaminates the CRM for years.
| Step | What it fixes | How |
|---|---|---|
| 1. Normalize | Capitalization, accents, stray spaces, phone format with country code | A spreadsheet or a cleanup prompt run over the CSV |
| 2. Deduplicate | The same contact captured by two people at the booth | Match on email and phone; keep the record with more context |
| 3. Cross-check against the CRM | Contacts that already existed as a customer or an open opportunity | Import with duplicate detection turned on |
| 4. Validate emails | Misspelled or non-existent addresses | A verification tool before the first send |
| 5. Enrich | Missing job title, company size, sector, website | A B2B enrichment service |
| 6. Tag | Lead source, specific event, group A/B/C/D, consent by channel | Fixed CRM fields, not free-text notes |
For steps 4 and 5: Apollo, Lusha, Clearbit or Dropcontact, the last of which has an explicit compliance focus; and Clay to orchestrate several sources. To move data between form, CRM and messaging without code, Zapier or Make; if your system is custom-built, see integraciones y APIs.
The field that decides whether the event looks profitable is lead source, and it must not be overwritten by the latest interaction. If your CRM attributes the close to the last touch, the show will never show up as having generated anything. In HubSpot, Pipedrive or Zoho CRM you solve it with a custom field that's write-once.
And consent gets stored as structured data —channel, date, time and event— not as a comment: the day someone asks where that phone number came from, a field is queried in five seconds and a free-text note is never found at all.
Dividing the work and filling the meeting calendar
Follow-up collapses when everyone is responsible for everything. Four functions, assigned to named people before you travel.
| Function | Responsibility | Window |
|---|---|---|
| Data coordinator | Consolidation, cleanup, deduplication, CRM load and tagging | Day 0 and the morning of day 1 |
| Owning rep | All contact with their A and B leads: email, WhatsApp, calls and scheduling | Days 1 to 3 and onward |
| Content owner | Making sure the promised resources exist and the templates are approved | Before the show |
| Measurement owner | Event report and the 30-, 60- and 90-day checkpoints | Day 3 and each checkpoint |
On a small team one person covers several functions; what doesn't work is leaving them unnamed. "Someone should load that into the CRM" means nobody loads it.
Assignment rule: whoever had the conversation keeps the contact, unless the account already has an owner. Splitting by territory or by shift forces the contact to explain themselves twice, which is the fastest way to lose them.
Realistic workload: a rep works 25 to 35 leads well in the first 72 hours, counting emails, calls and scheduling. If 170 contacts come back and there are two reps, either you prioritize with real criteria or the whole thing turns into a mass mailing.
The meeting calendar: how to fill it and keep it
The meeting is the only real outcome of the 72 hours; everything else is activity. And it holds together on operational details almost nobody attends to.
- Book within the first ten days. Beyond that, attendance drops and the conversation loses the thread of what was said at the booth.
- Send the calendar invite immediately, with the video call link already in it and a subject line that names the topic, not "follow-up." Without an invite there is no meeting: there's a good intention.
- A three-point agenda in the description, one line each: people who know what will be discussed cancel far less.
- A reminder the day before, through the channel where they replied to you, not the one you prefer.
Offer two specific times, never "whenever you can." The calendar of someone back from a trade show is a battlefield and deciding costs effort; two options get answered in one word.
Anyone who says "write to me in a month" almost always means it. Create the task in the CRM with an exact date and a two-line context note written today: a month from now, that note is the difference between picking the conversation back up and starting from zero.
And a realistic expectation: a well-qualified group A doesn't turn into meetings with everyone — part of it does, and the rest migrates to B. That's the funnel working; the failure is not having tried inside the window.
Want a hand applying this?
Free 30-minute working session. Uniamos is a remote AI automation agency (Austin and Mexico City) working over video calls and WhatsApp.
Reactivation at 30 and 90 days
The 2019 CEIR report recommends staggering post-event follow-up with three firm reporting dates —for example 30, 60 and 90 days, adjusted to your sector's sales cycle. It works just as well as a reactivation calendar: without fixed dates, everything dissolves into day-to-day operations.
| Timing | Who | What you send |
|---|---|---|
| Day 30 | Group A with no reply, and all of group B | Something new and useful: a piece of content, a regulatory change, a relevant product improvement |
| Day 60 | Open opportunities | A status review and a concrete next step |
| Day 90 | Everyone who didn't move forward | A cycle-closing message, with the door left open |
30-day reactivation email
Spanish version — send this one:
Asunto: [novedad concreta] — me acordé de lo que hablamos
Hola [nombre]: hace un mes conversamos en [feria] sobre [tema].
Le escribo porque [novedad concreta: cambio normativo, dato nuevo, función nueva] afecta justo a eso. Le dejo [el recurso] por si le sirve.
Si el tema quedó en pausa, sin problema: ¿le escribo de nuevo en [mes] o prefiere que lo dejemos por ahora?
English translation — for reference:
Subject: [specific development] — it reminded me of our conversation
Hi [name] — a month ago we talked at [show] about [topic].
I'm writing because [specific development: a regulatory change, a new data point, a new feature] affects exactly that. Here's [the resource] in case it's useful.
If the topic is on hold, no problem: should I write again in [month], or would you rather we leave it for now?
90-day cycle-closing message
Spanish version — send this one:
Hola [nombre]: le escribí un par de veces desde [feria] y no quiero seguir ocupando su bandeja.
Cierro el tema por mi lado. Si en algún momento [el problema] vuelve a la mesa, escríbame y lo retomamos donde lo dejamos.
English translation — for reference:
Hi [name] — I've written a couple of times since [show] and I don't want to keep taking up space in your inbox.
I'll close this out on my end. If [the problem] ever comes back to the table, write to me and we'll pick up where we left off.
That last message usually generates more replies than anything else in the sequence: it removes the pressure and gives an easy reason to answer. Don't write it as a reproach — write it as a clean close, because that's what it is.
How to measure the event's return: formula and example
With a simple formula, applied at three checkpoint dates. The usual trap is measuring closed sales at thirty days: no B2B cycle fits in that window, so every show looks bad.
The formula
Estimated return = (Pipeline generated × Historical close rate × Gross margin) ÷ Total event cost
Where pipeline generated is the sum of opportunities opened with the event as their source; historical close rate is your real one, not an optimistic estimate; and total cost includes space, booth, travel, tools and team hours.
An illustrative example —made-up figures to show the calculation, not a real case. A 40-person company exhibits at a regional show at a total cost of 500,000 currency units. It captures 150 contacts, 60 qualify, and at 90 days it has 12 open opportunities worth 4,000,000. Its historical close rate is 25% and its gross margin is 40%.
Estimated return = (4,000,000 × 0.25 × 0.40) ÷ 500,000 = 0.8: 0.8 units of expected margin for every unit invested, which means the event doesn't yet pay for itself. If that same company improves its qualification and ends up with 18 opportunities worth 6,000,000, the calculation gives 1.2. The show didn't change: the 72-hour process did.
| Indicator | When it's measured | What it diagnoses |
|---|---|---|
| Effective contact rate | Day 7 | Quality of the data and of the first message |
| Meetings booked ÷ group A | Day 10 | Quality of the qualification at the booth |
| Opportunities opened | Days 30, 60 and 90 | The team's ability to turn conversation into process |
| Pipeline generated | Days 30, 60 and 90 | The real size of the harvest |
| Cost per opportunity | Day 90 | Whether the show is worth it or needs replacing |
If you run a tablero de indicadores comerciales, keep these five visible with the event as a filter: seeing them every week turns follow-up into a habit instead of a campaign you ran once.
Typical post-show follow-up mistakes
- The identical mass email to all 170 contacts. It saves two hours and burns the entire list.
- Opening with "it was a pleasure meeting you at the show." That line forces the reader to remember something they don't remember. Start with the topic they raised.
- Waiting for Monday. If the show closes on Thursday, day 1 is Friday. The weekend isn't a pause in the process: it's when the memory fades.
- Sending the proposal before you understand. A quote sent to someone who hasn't defined their need does one thing: get you compared on price.
- Pushing six times in four days. Three touches across two channels in 72 hours is the maximum. After that, slow down.
- Messaging on WhatsApp without consent. Beyond breaking the channel's terms, the first reaction is to wonder where you got the number.
- Not recording disqualifications. Six months from now, someone on the team prospects the competitor who stopped by to look around.
- Leaving the CRM for later. The data gets loaded in the first 24 hours or it gets loaded badly, with half the context lost.
- Measuring only closed sales at 30 days. No serious B2B cycle fits in that window; by that metric, every show looks like a failure.
- Not closing the loop at 90 days. Eternal limbo inflates the pipeline, distorts the forecast and demoralizes the team.
Tricks that aren't in the manual
- Send the first message from the show floor, not from the hotel. Half an hour before closing, with traffic already down, the group A contacts from the first two days can get their acknowledgment. You gain half a day.
- Use their exact words as the subject line. If they said "we lose a whole month reconciling invoices," your subject is "Reconciling invoices": it gets opened far more than "Expo 2026 follow-up." And if you took a photo at the booth with permission, attach it: it reactivates the visual memory in a second.
- Write the templates before you travel and leave them in drafts, with the blanks marked and the attachments loaded. Coming back and only having to fill in blanks changes the odds that the follow-up happens at all.
- Block days 1, 2 and 3 on your calendar before the show, as if they were travel days. Otherwise they fill up with internal meetings someone booked while you were away.
- Call at the odd hour: eight-thirty in the morning or six-thirty in the evening; at eleven they're in a meeting. And if your email tool tracks opens, someone who opened three times without replying is a candidate for a call, not another email.
- Prepare the "rescue email for the forgotten contact." For the contact whose note went missing: "I took your details at the show and misplaced the specifics. Could you remind me in one line so we can pick it up?" Honesty works better than pretending.
- Ask for an introduction in the second message. "Are you the right person to look at this, or should I pass it to whoever is?" unblocks contacts who weren't decision-makers and didn't know how to tell you.
- Save the objections that kept coming up at the booth, three or four verbatim lines in a shared document: they're the best input for next year's talk track and for group C content.
- Always close the loop with the 90-day message. It produces the most replies and it leaves the door open at no cost.
- Build an AI workspace for the event and keep it alive, with the contact CSV, your templates, your tone of voice and the objections you collected. It serves the follow-up, the 30- and 90-day reactivations, and comparing harvests next year.
What to do this week
- Monday. Define the four groups with written criteria and add them as a required field on your capture form.
- Tuesday. Draft the four email templates from this article in your own tone and save them as drafts.
- Wednesday. Submit the three WhatsApp templates for approval: it's the step with an external timeline.
- Thursday. Check that your CRM has a lead source field that doesn't get overwritten and another for consent by channel. If not, create them today.
- Friday. Assign the four functions to named people and block days 0 to 3 of the next event on the calendar.
- Before the week ends. Test the batch drafting prompt on ten old contacts: in ten minutes you'll see what your context field is missing.
If you'd rather build the whole circuit with support, at Uniamos we implement it alongside your sales team. And if what you want is to set the channel up properly from the ground up, start with la parte de WhatsApp con IA.
Frequently asked questions
Does replying within 72 hours really matter, or is it just a marketing rule?
It matters for one concrete reason: memory. Whoever visited you talked to dozens of exhibitors in three days, and a week later they can't tell one conversation from another. A message that arrives the same day quoting their exact words is recognized instantly; the same message ten days later demands a feat of memory that almost nobody makes.
How many touches before I stop pushing?
Three in the first 72 hours, across at least two channels: email, call and WhatsApp. With no reply, the contact drops a group and moves to the normal cadence, with reactivation at 30 and 90 days. Pushing six times in four days speeds up nothing and ruins the relationship for the day that person actually needs what you sell.
Can I message someone on WhatsApp if they gave me their business card?
A business card is not consent for a personal channel. The official WhatsApp Business Platform requires prior authorization and approved templates for business-initiated messages. Collect consent at the booth, with its own checkbox for WhatsApp, and store it as structured data with date, time and event. This is not legal advice: review it with your advisor.
Is it better to call first or write first?
Write first and call afterward, the same day or the next. The message delivers what you promised and gives the call a concrete reason: “I sent over what we agreed on, did you get a chance to look at it?” Calling without having sent anything leaves the conversation with nothing to stand on and usually ends in “just email it to me,” which is back to square one having spent an attempt.
What do I do with the contacts who were only browsing?
They go to group C: one nurture email, just one, with the best content you have and no pressure. They don't enter a sales sequence. And the ones who clearly aren't a market —students, vendors, competitors— get recorded as disqualified with a reason, so that six months from now nobody works them by mistake.
How do I keep AI-written emails from sounding robotic?
By giving it material only you have: their exact words, the need you identified and the time window. Set an exact structure in the prompt, a word limit and a list of banned phrases, and tell it to write “FALTA CONTEXTO” instead of inventing. And review every group A email by hand.
How often do you measure a trade show's return?
At three checkpoints: 30, 60 and 90 days, adjusted to your sector's sales cycle. The 2019 CEIR report specifically recommends staggering follow-up across three firm reporting dates. Measuring only closed sales at thirty days makes any show look bad, because almost no B2B sales cycle closes in a month.
Should I automate the whole follow-up?
Automate the repetitive work —CRM loading, deduplication, enrichment, reminders and creating reactivation tasks— and leave group A drafting and all calls to people. The automation that works best is the kind that frees up time to talk, not the kind that replaces the conversation.
Related articles
- Trade shows and expos: preparation, calendar and lead capture
- AI agents on WhatsApp Business: the definitive guide
- B2B lead generation with AI in Mexico and Paraguay
- AI prompts and tricks for sales teams
- What an AI agent on WhatsApp is and how it works
- Using AI with customer data in Paraguay
- How to roll out AI in your company, phase by phase
- More from the blog