How to staff a help desk that resolves attendee problems on event day

Your entrance team is scanning tickets when someone arrives with the wrong booking date. Behind them, a buyer wants to discuss an access arrangement, an exhibitor needs a replacement badge, and another attendee says the session they paid for has moved. Each question needs a different answer. Putting them all in the admission queue makes everyone wait.

An event help desk needs people who can identify the problem, resolve the ordinary cases and reach someone authorised to handle exceptions. Give each unresolved issue an owner and tell the attendee what happens next. A friendly person behind a sign cannot do that work without access, information and decisions they are allowed to make.

The first thing you want to do is separate routine admission from longer support conversations. Then plan the desk around the problems your paying attendees are likely to bring, including those that continue after the opening rush. This guide explains the staffing, permissions and handovers that make that possible.

Decide what your help desk actually owns

Start with the questions from your previous events and the promises you've made for this one. Read attendee emails, refund requests and notes from the entrance team. Look for problems that needed someone to investigate or make a decision, rather than questions a clear sign could answer.

Your list might include a booking that cannot be found, an incorrect ticket category, an access request, a programme change or a complaint about something promised in the offer. Add event-specific problems, such as workshop allocations or equipment collection. A seated performance needs different support from a conference with several paid sessions.

Now decide where each issue goes. The help desk may resolve ordinary booking queries and coordinate other assistance. Medical care, safeguarding and security need their own competent people and agreed routes. The desk can help someone reach those services without attempting the specialist response itself.

Don't quietly add speaker management, exhibitor support and lost property to the same person's responsibilities. You can combine duties when the timing and workload allow it, but check what happens when those demands arrive together. A person walking a speaker backstage cannot also own a desk with a waiting attendee.

For a small event, the help desk might be one clearly identified position near the entrance. A larger event may need several support points and a central lead. The important distinction is who owns the problem, rather than how impressive the desk looks.

Our event staffing guide covers the wider team. Use it to identify the people your desk needs to reach, then agree the specific cases the desk handles and those it transfers elsewhere.

Separate quick questions from problems needing investigation

Give someone a way to greet people and find out what they need before they wait through a long conversation. During a busy arrival period, this might be a staff member near the support area. At a smaller show, the desk agent can do it when the queue permits.

Keep that first conversation brief and discreet. A person asking where the toilets are needs a direction. Someone whose booking appears missing needs a check. Someone reporting a safety concern needs the agreed reporting route immediately, regardless of their place in the ordinary support queue.

Don't ask people to explain sensitive details in front of everyone. Establish enough to choose the next action, then move the conversation to a suitable position. A private conversation should still follow your venue's safety arrangements and provide a workable way to contact colleagues.

Use plain descriptions when directing attendees. Tell them who will help and why. "The ticket support colleague here can check that booking" is more useful than sending them towards a department name they don't recognise.

The person directing the queue needs current information too. If they send every refund question to an agent who cannot authorise anything, they have moved the wait without moving the decision. Give them the same basic understanding of responsibilities as the desk team.

Check whether repeated quick questions reveal a wider information problem. If several people ask where a relocated session is, update the relevant sign and attendee message. Keeping another agent busy repeating directions leaves the underlying confusion in place.

Put the desk where people can find and use it

Walk the route as an attendee arriving for the first time. Can you see where to get help before you reach the scanners? Is it obvious after you're inside? People should not have to leave the event and rejoin the admission queue simply to ask a question.

Keep the waiting area clear of entrance lanes, exits and routes needed by other venue users. Britain's Health and Safety Executive guidance on crowd controls addresses queues, circulation and the information people need at different event stages. Agree the desk position and queue arrangements with your venue and crowd-management lead.

Choose a location where staff can hear an attendee without broadcasting their booking details. Think about stage sound, announcements and the opening rush. A desk beside a loudspeaker may be visible but difficult to use for the conversation you've put it there to handle.

Check access to the desk, the height and arrangement of the working area, and somewhere suitable for a person who cannot stand while waiting. Ask your accessibility lead to inspect the actual layout. An accessible entrance does not guarantee that the support point can be used comfortably.

Provide a way to get help without relying entirely on a phone or QR code. Someone may have a flat battery, limited signal or difficulty using the form. Digital contact can supplement the desk, provided someone monitors it and the attendee knows when to expect an answer.

Give floor staff the same directions you put in attendee information. If the desk moves, update both. A printed map and a confident usher giving different instructions can turn a short walk into another complaint.

Monitor messages without losing people between channels

Some attendees will contact you by email or an event form while others walk to the desk. Decide which channels you will monitor during the event and publish a clear expectation for each. An email address described as event-day help needs someone able to read it during the hours you advertise.

Route these messages into the same ownership process as desk conversations. A person who emails and then visits should not receive two different decisions. Ask enough to find an existing case, and make it clear which colleague is now handling the next action. You don't need to copy every message into every system.

Have someone watch for a wider pattern. Several reports of the same missing session link or changed room may need one correction and an approved announcement. Let the relevant operational lead verify the situation before the desk publishes a new instruction. A fast but incorrect message can send more people to the wrong place.

If you cannot monitor a channel promptly, say so and provide the working route for onsite help. Update that information when the desk closes. Leaving an unattended contact form open under a promise of immediate help gives attendees a reasonable expectation your staffing cannot meet.

Staff for the busiest support period, not average attendance

There is no useful universal rule saying one help-desk agent can cover a particular number of attendees. Demand depends on arrival patterns, the offer, the venue and how complicated the problems are. Estimate the work your desk will face during the busiest period.

Start with your own comparable events. How many people needed help around opening? Which questions took longest? Did a programme change create another rush later? If you have no history, walk through the likely cases with the people who know ticketing, access arrangements and the programme.

Here's a deliberately simple illustration. Suppose you expect 24 ordinary support conversations in an opening hour and estimate four minutes per conversation. That is 96 minutes of handling work arriving in 60 minutes. One agent cannot complete it within that hour, even before interruptions.

Two agents would provide 120 minutes in the hour on paper, leaving 24 minutes beyond the estimated conversations. That does not prove the staffing is adequate. Arrivals may cluster into a shorter period, and a complicated case may take one agent away. The calculation exposes a shortage; it doesn't promise a waiting time.

All those figures are invented planning inputs, not industry benchmarks. Use measured handling times where you have them, include the work needed to record and transfer a case, and check your assumptions during a rehearsal. Add separate allowance for breaks, supervision and the people you expect to leave the desk.

Plan relief that can actually take over. A spare volunteer may be able to direct people but lack permission to investigate bookings. Match cover to the job, and decide who can arrange more support if the queue or unresolved work grows beyond your plan.

Give agents decisions they can make without chasing you

Access to a booking record and authority to change an arrangement are different things. Before event day, decide which ordinary cases an agent can finish, which need a lead and which require another specialist. Then explain the boundary with examples from your event.

An agent might be able to explain the confirmed programme, locate a booking through the approved process and give the published response to an ordinary query. A ticket-category change, compensation request or disputed entry decision may need someone else. Choose the rules that fit your policies and the obligations that apply.

Avoid writing "manager approval required" without naming the manager on duty and a backup. Your event owner may be on stage, handling a supplier problem or away from their phone. If every exception waits for that one person, more desk agents won't necessarily improve resolution.

Set any spending or goodwill permissions in advance. Specify what the agent can offer, under which circumstances and how it is recorded. These are business decisions, not instructions to override refund rights, accessibility requirements or capacity limits when somebody is upset.

With Loopyah ticketing, you can add event admins and door staff without sharing your login, and give door staff check-in access for QR scanning on their phones. That lets scanning staff have access suited to their job. Assign the support role separately and verify that each person can perform the actions their responsibilities require.

Test the actual accounts before doors. Don't discover during a disputed booking that the designated support agent cannot see the information they need, while everyone has been borrowing an owner's account to compensate.

Include the commitments staff must preserve when offering a solution. Moving an attendee to another session depends on the place being available and the change being appropriate. A replacement ticket must not leave both the original and replacement usable unintentionally. Have the relevant ticketing or programme lead explain the correct process, then let agents practise it.

Explain how a difficult conversation reaches a supervisor without making the attendee start again. The agent can summarise what has happened and remain available for clarification. If somebody behaves abusively or threatens staff, follow the agreed staff-protection and security procedure. Resolving a complaint does not require leaving an agent alone with behaviour the event has decided is unacceptable.

Make those limits visible during the briefing. People should know which decisions protect a sold entitlement, which need a commercial review and which belong with safety or security. When those boundaries are clear, agents can spend more attention understanding the attendee's problem. When they are unclear, a polite response can still create an unauthorised commitment that another team must undo. Check that replacements and late starters receive the same explanation before they serve anyone, especially during the rush at opening.

Follow one awkward booking through to a result

Imagine an attendee at a paid conference says their ticket included a workshop, but the workshop team cannot find their name. They have already been sent back to registration. The session starts soon, and they are understandably frustrated about spending more of their event in a queue.

The desk agent first establishes which booking and workshop are involved through the approved checks. They look at what the attendee bought and any confirmed allocation. They do not promise entry to the room while those facts remain unclear. They also avoid asking the attendee to repeat every detail to another colleague without an explanation.

Suppose the booking does show the workshop allocation. The issue now needs the workshop lead to confirm the operational position and correct the mismatch. The desk agent sends the reference and the finding, explains that the session is approaching, and gets the lead to accept the case. The attendee hears where to wait and when the desk will update them.

If the record does not show an allocation, the next step is different. The agent checks the wording and confirmation the attendee received, then follows the agreed dispute route. There may be an error in the offer, a booking misunderstanding or another explanation. Those possibilities need investigation. Neither the desk nor the room team should create a new promise merely to end an uncomfortable conversation.

Now suppose the lead doesn't answer. This is why the backup matters. The desk supervisor uses the alternative contact and records who now owns the decision. If no immediate resolution is available, explain that honestly, including what follow-up will happen and who can decide any remedy. Don't tell the attendee that the workshop team will definitely sort it out when nobody has accepted the case.

When a decision arrives, communicate it back to the attendee and the people who must implement it. If they can attend, confirm that the room team knows the arrangement. If further review is needed, confirm the contact route and responsibility. The useful result is an agreed action that actually happens, rather than a closed note saying the attendee was referred elsewhere.

Prepare answers that match what you sold

Your desk needs a current event brief, the published ticket terms, confirmed programme and relevant access information. It also needs the final decisions behind exceptions you have already agreed. An attendee should not have to persuade a second person that your colleague made a promise yesterday.

Keep the instructions in a place the team can reach quickly. Organise them around ordinary questions rather than the departments that wrote them. For each common problem, explain what to check, what the agent can do and where an unresolved case goes.

Include the awkward cases. What if the booking is for another date? What if an attendee has a screenshot but the ticket has already been used? What if two people claim the same seat? Agree an investigation and decision route with the appropriate lead. Don't tell agents to admit someone simply to clear the queue.

Make changes easy to identify. When a session moves, publish the confirmed room and time, when the change was approved and who can answer exceptions. Tell the desk when attendee messages have been sent so they understand what the person in front of them has been told.

Keep the language natural. An agent should be able to explain the policy and the next step, rather than read a defensive paragraph while the attendee asks what happens now. A brief can support good judgment without trying to script every sentence.

Use your event team briefing to test understanding. Ask the team to work through a realistic query and explain who makes the decision. If their answers differ, resolve that before they give different promises to buyers.

Make assistance accessible and keep personal details private

Ask the attendee how you can help them communicate. Give them time to explain, and avoid assuming that a companion should answer on their behalf. Have your agreed communication support ready rather than requiring every person to use the same method.

For covered US organisations, the Department of Justice's guidance on effective communication explains that the appropriate aid or service depends on the nature, length, complexity and context of the communication, as well as the person's usual method. Brief staff on the arrangements that apply to your event and the relevant local requirements.

A simple written exchange may help with one short question. A complicated dispute may require different support. Check that staff know how to obtain it, who authorises it and where the conversation can take place. Don't treat the existence of a printed FAQ as a solution to every communication need.

Privacy matters in ordinary booking support too. Position screens so people in the queue cannot read them. Avoid calling out full contact details or displaying an attendee list for everyone to search. Confirm identity through the approved process before disclosing booking information or making a change.

Keep the case record proportionate. The UK's Information Commissioner's Office explains the data minimisation principle as keeping personal data adequate, relevant and limited to what is necessary. Where UK GDPR applies, that is a legal principle. Elsewhere, check the rules that apply to your operation.

For a routine operational handover, you may need a reference, the unresolved issue and the next owner. You usually don't need an attendee's full personal history copied into a general crew chat. Agree where sensitive information belongs and which authorised people need access before the team starts recording cases.

Hand a problem to a person who accepts it

"I've told someone" doesn't establish that the problem is being handled. A transfer needs a receiving person who understands the issue and accepts the next action. Until that happens, keep a clear owner at the desk.

Send the information the receiving person needs, using the appropriate channel. Explain the problem, what you've checked, what decision is needed and where the attendee is waiting. Avoid making them reconstruct the case from several forwarded messages.

Then tell the attendee what happens next. You might explain that the seating lead is checking the booking and the desk will update them at an agreed time. Promise a time for an update that your team can meet, rather than a resolution you don't control.

For a ticketed workshop that is about to start, the deadline matters. The lead needs to know whether the person will miss the session while waiting. That may change the urgency or the available remedy, but it doesn't give an agent permission to invent a place in a full room.

If the receiving person is unavailable, use the agreed backup. Don't keep sending the same message to an unattended channel. The desk lead should be able to move the decision to someone who can act or explain the remaining constraint honestly.

Keep the attendee informed even when the answer hasn't changed. Silence can make someone return to the queue and explain the problem to another agent, creating duplicate work and competing promises. A short, accurate update helps them decide whether to keep waiting or use an agreed follow-up route.

Keep urgent incidents out of the ordinary support queue

Your team needs to recognise when someone is reporting an immediate concern rather than asking for customer service. Use the venue and event procedures for medical issues, threats, safeguarding and other urgent incidents. The help desk should know how to summon the relevant support and give an accurate location.

Britain's HSE guidance on incidents and emergencies calls for planned procedures and tested communication systems. It also addresses coordination with emergency services and official public messages. Apply the arrangements agreed for your event and jurisdiction rather than allowing desk agents to improvise an emergency response.

Practise the first action. If someone says a companion needs urgent help, the agent should know the contact route and what information to pass on. They should not make the person complete an ordinary complaint form before alerting the appropriate team.

Decide who remains at the desk if an agent needs to accompany someone or assist a specialist. Otherwise one urgent case can leave the rest of the support area unattended. Your relief plan needs to work during the public event, not only at scheduled break times.

Separate safety reporting from promises about refunds or compensation. The immediate response protects people and follows the incident arrangements. Commercial questions can then reach the authorised person through the appropriate process. Don't let a dispute about a ticket delay necessary assistance.

For records, use your established event incident report process where the situation requires it. Keep access restricted appropriately and avoid duplicating sensitive incident details in an ordinary support list just because the desk first heard about them.

Rehearse the desk before the first attendee arrives

Walk through the whole interaction with the people who will actually work the shift. Start at the point where an attendee asks for help. Check the direction they receive, the booking lookup, the decision and any transfer to another lead.

Use a few cases that test different weaknesses. One can be a straightforward booking question, another a disputed ticket and another an access request. Add a situation where the usual decision-maker doesn't answer. You want to find out whether the backup can make the decision while there is time to change the plan.

Test the physical setup too. Can staff hear each other? Can the attendee use the desk? Do devices connect from that location, and can they stay charged? Does the waiting area obstruct another route? A rehearsal at the office won't reveal all the problems in the venue.

Agree a fallback for a device or connectivity failure with the relevant technical and ticketing leads. It should preserve appropriate booking checks and control of admission. A hurried export of the entire customer database onto several personal phones creates a different problem.

Confirm the end of each shift and the incoming person's preparation. Someone arriving after doors still needs the current brief, access and outstanding cases. Don't rely on the outgoing agent to explain the whole event while also serving the queue.

The HSE's guidance on managing an event highlights competence, information and appropriate supervision. For your support desk, make training practical enough that you can see people use the process, rather than treating receipt of a document as proof that they can handle an exception.

Keep a small desk useful without pretending it is a department

At a smaller paid event, you may combine the desk with another role during quieter periods. Choose duties the person can pause without abandoning someone else. Preparing a routine note may fit; escorting a performer through a distant building probably won't.

Keep the public support location clear even when the person steps away. Arrange named cover or an obvious, staffed way to reach them. A sign telling attendees to find an organiser doesn't help much when they cannot tell which lanyard belongs to one.

Protect the decision route as carefully as the desk itself. The event owner might handle exceptions, but they need a backup for the times they cannot answer. Explain the limits to whoever covers. You can run a modest operation with straightforward arrangements as long as the responsibilities and availability are real.

Finish the case and use the pattern to improve the event

A case is not finished simply because the attendee leaves the counter. Record the result or the next action, including who owns any follow-up after the show. If you promised an email or a refund review, put it into the process that will actually deliver it.

Before the desk closes, check the unresolved cases together. Make sure the next team has the information and access it needs, and tell attendees how to reach you once onsite support ends. Keep the published contact route monitored for the hours you promise.

Review the reasons people needed help. A large number of questions about one entrance may call for better directions. Repeated disputes about a ticket benefit may mean the offer needs clearer wording. Extra agents can help deliver service, but they should not become a permanent substitute for correcting misleading information.

Look at outcomes alongside speed. Fast handling is less useful if attendees return because the original problem wasn't resolved. Track how many cases were completed, transferred, left open or repeated, using definitions your team understands. Keep personal information out of the general review where it isn't needed.

Use what you learn to change one part of the next event's plan. Update the attendee message, revise an agent's decision permissions, or arrange cover at the point where the queue grew. Give the change an owner and check it at the next show.

Before you open, ask your desk team to explain what happens when an attendee brings them a problem they cannot finish. They should be able to name the next person, the contact route and how the attendee will hear back. Resolve any uncertainty while everyone still has time to prepare.