Exhibitor communication: Notification, email, portal

Sometimes the participant receives a portal notification, sometimes an email, sometimes a push notification; when messages conflict, trust decreases. A communication center approach ensures channels operate harmoniously.

A single channel is not a requirement; consistent content and timing are essential.

Symptoms of inconsistent channels

• One date on the portal, another in email
• Excessive notifications
• Critical message remaining on a single channel
• Language inconsistency

Consistency framework

1. Source text: Single source of truth for content.
2. Channel selection: Based on urgency.
3. Frequency: Fatigue limit.
4. Personalization: As needed.
5. Measurement: Open/action.

Frequently asked questions

Is push notification mandatory?

Useful for critical reminders.

Is the portal sufficient?

Can remain passive; email complements it.

Who authors?

Ops + Marketing collaborate.

Crisis?

Short, clear message, multi-channel.

Modules?

Attendee management + automation.

Don't make channels compete, align them.

Consistent communication also reduces support tickets.

Discover QEMENT features or contact us.

The most common mistake teams make regarding the attendee communication center is setting up the tool but not documenting the process. If questions like who enters the data, who approves it, who makes it visible to visitors, and who manages exceptions on the fair day are not clear, even if the system is filled, operations remain chaotic. Therefore, a single-page responsibility matrix should be updated at the beginning of each season.

Without measurement, the attendee communication center cannot be improved. Take a baseline before the season; monitor with the same definitions during the season; and write three concrete actions at the end of the season. Instead of saying 'It got better,' talk about rates, durations, and volumes. The next team should be able to read the same numbers.

Changes on the fair day are inevitable. What's critical is which record the change is applied to and who is informed. Verbal updates alone are not enough; if the relevant profile, map, notification, or request record is not updated simultaneously, the field and office will become disconnected.

Use consistent language in exhibitor and visitor communication. Explaining the same rule one way on the portal and another way in an email increases the support load. Short help texts, screenshot guides, and a deadline calendar should work together.

Even on an integrated platform, Excel backups don't completely disappear; the problem is when the backup is declared the 'primary source'. Keep the official source in one place, use exports for reporting purposes. Otherwise, the debate over which file is correct will reopen in two days.

As your international exhibitor and visitor rates increase, language, time zone, and permission rules become part of the same process. Leaving translations until the last day weakens the registration and discovery funnel. Set a target of at least two languages for critical areas at the beginning of the season.

Checklist

• Process owner and backup owner are documented.
• Mandatory fields and publishing rules are clear.
• Pre-fair rehearsal or sample registration test has been conducted.
• Fair day exception channel (who, what time) is defined.
• End-of-season metrics and action list are stored.
• Roadmap features are not confused with live promises.

This checklist should not be reinvented for every event. It is embedded in a folder or season template; a new team member sees the same list in their first week. Maturity emerges in repeatability, more than in the number of tools.

Small touches that reduce the support burden

Half of the questions received by the info desk and call center are actually “where do I find it / how do I do it” questions. A help page, in-portal tips, and timely short SMS/email cut this burden. The same content base feeds assistants or AI features when they arrive; an assistant built on an empty knowledge base generates frustration.

Finally: you don't have to activate every new feature at once. First, fix the three workflows that generate the most tickets, measure, then move on to the next package. Disciplined simplicity in fair operations yields faster results than a pile of features.

In the seasonal review, records related to the exhibitor communication center are sampled and checked. In twenty randomly selected records, field integrity, publication status, and stakeholder visibility are examined. Found errors are transformed not into personal complaints, but into rule and template improvements. This sampling habit catches quality issues lost in large lists early and reduces hidden debt carried over to the next event. Sampling notes are stored in the folder; comparisons can be made when the same check is repeated a year later.

In the seasonal review, records related to the exhibitor communication center are sampled and checked. In twenty randomly selected records, field integrity, publication status, and stakeholder visibility are examined. Found errors are transformed not into personal complaints, but into rule and template improvements. This sampling habit catches quality issues lost in large lists early and reduces hidden debt carried over to the next event. Sampling notes are stored in the folder; comparisons can be made when the same check is repeated a year later.

In the seasonal review, records related to the exhibitor communication center are sampled and checked. In twenty randomly selected records, field integrity, publication status, and stakeholder visibility are examined. Found errors are transformed not into personal complaints, but into rule and template improvements. This sampling habit catches quality issues lost in large lists early and reduces hidden debt carried over to the next event. Sampling notes are stored in the folder; comparisons can be made when the same check is repeated a year later.

In the seasonal review, records related to the exhibitor communication center are sampled and checked. In twenty randomly selected records, field integrity, publication status, and stakeholder visibility are examined. Found errors are transformed not into personal complaints, but into rule and template improvements. This sampling habit catches quality issues lost in large lists early and reduces hidden debt carried over to the next event. Sampling notes are stored in the folder; comparisons can be made when the same check is repeated a year later.

In the seasonal review, records related to the exhibitor communication center are sampled and checked. In twenty randomly selected records, field integrity, publication status, and stakeholder visibility are examined. Found errors are transformed not into personal complaints, but into rule and template improvements. This sampling habit catches quality issues lost in large lists early and reduces hidden debt carried over to the next event. Sampling notes are stored in the folder; comparisons can be made when the same check is repeated a year later.

In the seasonal review, records related to the exhibitor communication center are sampled and checked. In twenty randomly selected records, field integrity, publication status, and stakeholder visibility are examined. Found errors are transformed not into personal complaints, but into rule and template improvements. This sampling habit catches quality issues lost in large lists early and reduces hidden debt carried over to the next event. Sampling notes are stored in the folder; comparisons can be made when the same check is repeated a year later.

In the seasonal review, records related to the exhibitor communication center are sampled and checked. In twenty randomly selected records, field integrity, publication status, and stakeholder visibility are examined. Found errors are transformed not into personal complaints, but into rule and template improvements. This sampling habit catches quality issues lost in large lists early and reduces hidden debt carried over to the next event. Sampling notes are stored in the folder; comparisons can be made when the same check is repeated a year later.

In the seasonal review, records related to the exhibitor communication center are sampled and checked. In twenty randomly selected records, field integrity, publication status, and stakeholder visibility are examined. Found errors are transformed not into personal complaints, but into rule and template improvements. This sampling habit catches quality issues lost in large lists early and reduces hidden debt carried over to the next event. Sampling notes are stored in the folder; comparisons can be made when the same check is repeated a year later.