Block and report (event app)

The moment an app lets strangers message each other, it needs block and report — not as legal cover, but because unwanted contact reliably happens at scale. The common cases are mundane: over-persistent salespeople messaging everyone, recruiters spamming a competitor's staff, the occasional attendee who won't take silence for an answer. Rarer cases are serious, including harassment that overlaps with code-of-conduct violations and sometimes with things that happened physically on site. Blocking handles the mundane tier instantly and without confrontation, which is exactly why it must be easy to find — two taps from any message or profile, no justification required, and invisible to the blocked party. Reporting handles the serious tier, and this is where organizers rather than vendors carry the weight: a report needs a defined owner, a response-time target measured in hours during the live event, and a decision path that connects to your code of conduct and, when needed, on-site security. The common mistake is assuming the vendor handles reports — most platforms only route them to a queue the organizer is supposed to be watching, and an unwatched queue during a live event is a genuine liability. One honest nuance: block rates are quiet quality data. A spike in blocks against one exhibitor's team tells you about behaviour that will never appear in a satisfaction survey.