Events
Event Guest Communication: A Practical Guide
Design attendee communication that preserves ticket state, total price, accessibility and safety while giving every exception an accountable owner.
Event Guest Communication: A Practical Guide begins with a controlled operational boundary. It does not assert a configured LumiTalk capability, integration, compliance state, ticket inventory, price, fee, refund, accessibility feature, response time, language coverage, attendee result or business outcome.
Use this decision framework
| Attendee need | Administrative response | Owner |
|---|---|---|
| Event or ticket facts | Use current event, venue and ticket inventory | Ticketing owner |
| Price, fee or refund | Use authoritative transaction and policy state | Finance or authorized seller |
| Accessibility | Describe verified seating and services; provide effective communication | Accessibility owner |
| Emergency or security | Use approved local emergency route and venue command | Emergency services and venue incident owner |
Map the attendee journey
Event communication begins before a ticket is offered and continues through purchase, transfer, arrival, entry, occupied venue, schedule change, cancellation, refund and post-event complaint. Define which promoter, venue, primary seller, reseller, payment provider and production team controls each state. A message is not a ticket, a transfer request is not accepted ownership, and a ticket scan does not resolve every access issue. Publish exact state language, system of record, owner, deadline, backup and attendee expectation for every step.
Keep price and fee answers authoritative
The FTC fee rule covers businesses that offer, display or advertise live-event tickets. Use the current authoritative ticket total for the event, section, quantity, seller, currency and selected options. Qualified reviewers must determine treatment of taxes, optional items and other charges. Do not quote a stale face value, hide mandatory fees, call a required charge optional or imply identical prices across primary and resale channels. Preserve the offer, total, components, source and expiry so a discrepancy can be reconstructed.
Explain changes, cancellation and refunds
State the event and seller policy version attached to the actual order, including postponement, venue change, cancellation, transfer, resale, credit and refund paths. Do not promise a refund because a request was received or because another seller handled a similar event differently. Identify the merchant and authorized decision owner. When weather, public safety, accessibility, artist, venue or production facts may trigger a policy review, preserve the attendee’s words and transaction evidence, then give a concrete next expectation without prejudging the outcome.
Make accessibility information usable
ADA ticketing guidance addresses sales, prices, available accessible seating, companion tickets, transfer, secondary markets and hold-and-release rules. Maintain verified seat, route, entrance, restroom, communication, sensory and service facts by venue and event configuration. Provide effective communication and a human path. Do not infer needs from a disability, require unnecessary medical detail, or release accessible inventory outside approved policy. When a feature or temporary configuration is uncertain, obtain an accountable venue answer instead of guessing from a seating map.
Separate emergencies from service questions
Publish immediate routes for fire, smoke, medical danger, violence, severe weather, structural concern and other local emergencies. Attendees should contact 911 or follow onsite emergency officials when immediate danger exists. Support staff must not diagnose a condition, direct re-entry or contradict venue incident command. FEMA special-event planning and CISA mass-gathering resources emphasize coordinated planning with public safety stakeholders. Distinguish emergencies from urgent access, lost-person, credential, conduct and routine information issues, each with a primary owner, backup and accepted handoff.
Protect identity, credentials and payments
Treat a phone number, email, order reference or screenshot as a signal, not sufficient proof of authority. Apply risk-based verification before disclosing attendance, changing names, transferring tickets, reissuing credentials, changing refund destination or discussing payment. Never request passwords, one-time codes or full card data in open messaging. Use approved PCI-scoped payment flows. Suspected account takeover, counterfeit credentials, seller impersonation or redirected payment requires a separate security route and independently verified contacts.
Clarify seller, venue and platform boundaries
Promoters, venues, primary ticket sellers, resellers, payment processors and event producers may control different information. Build a responsibility matrix for inventory, fees, tax, refunds, accessible seats, transfer, entry, safety, privacy, complaints and records. Do not bounce an attendee with “contact the platform” unless the workflow identifies the actual owner and next step. Preserve cross-system order and event identifiers without exposing internal notes or other attendees’ data. Escalate conflicting records instead of choosing whichever version appears easiest.
Test complete journeys
Run synthetic scenarios for a total-price quote, accessible seat, companion ticket, ticket transfer, duplicate order, changed venue, postponement, cancellation, refund request, compromised account, payment diversion, failed barcode, inaccessible entrance, relay call, severe weather, medical emergency and platform outage. Score event accuracy, ticket state, price evidence, accessibility, identity, privacy, payment boundary, emergency routing, human acceptance and closure. Reconcile the ticketing, CRM, payment, messaging, credential and incident systems before expanding traffic.
Primary authorities and related event guides
Use current official authorities as the factual floor, then apply qualified review to the event, venue, seller, promoter, merchant, jurisdiction, attendee, channel and configured workflow. FTC: Rule on Unfair or Deceptive Fees FAQ · FTC: BOTS Act Compliance Refresher · FTC: Protecting Personal Information · FTC: Data Breach Response Guide · ADA.gov: Ticket Sales · ADA.gov: Effective Communication · FEMA: Special Events Contingency Planning · CISA: Mass Gathering Security Planning Tool · CISA: Commercial Facilities and Public Venue Resources · PCI SSC: Small Merchant Guide to Safe Payments
Continue through the Events and Hospitality hubs, review the commercial service route, and use sibling guides for the next distinct decision. Events editorial hub · Hospitality industry hub · Events services · Event Answering Service: Buyer Checklist · Event Registration and Ticketing Workflow · After-Hours Event Attendee Support Playbook
Scope and evidence boundary
This editorial framework is not legal, safety, accessibility, privacy, payment or emergency advice. Applicability requires event- and venue-specific review. Product claims use verified-product, verified-business, owner-confirmed-pending-artifact, verification-needed or contradicted. Missing evidence creates a research task—not a verdict about LumiTalk.
Quick answers
Frequently asked
What is event guest communication?
It is the governed system connecting attendees to accurate event and ticket facts, secure actions, accessible service and accountable human owners.
How should ticket fees be communicated?
Use the current authoritative total and qualified application of the FTC fee rule; do not improvise from face value or stale screenshots.
Can support promise a refund?
Only the authorized seller or event owner can decide under the actual order and policy; support should preserve the request and next step.
What should happen in an emergency?
Direct immediate danger to 911 or onsite emergency officials and activate the venue incident route without contradicting incident command.
Design a governed event attendee workflow
Map one event journey, its ticket and safety boundaries, owners, evidence, tests, fallback and exit before expansion.
