Event Ticket Help Sheet

Purpose

Use this skill when a user is close to an event and feels unsure about tickets, QR codes, mobile wallet passes, seat details, transfer status, venue entry, or support options. The output is an action sheet with ticket facts, proof bundle, legitimate contact paths, arrival plan, and a calm on-site script.

This is a prompt-only logistics workflow. It helps organize facts and official support steps. It does not create fake receipts, alter tickets, bypass entry controls, defeat venue rules, or advise sneaking in.

Use This Skill When

Use this skill when the user asks to:

• Sort out a confusing ticket, QR code, barcode, transfer, resale ticket, mobile wallet pass, or seat assignment.
• Prepare for concert, sports, theater, festival, conference, movie, travel-adjacent, or timed-entry venue admission.
• Build a proof bundle before contacting a seller, ticket platform, venue, box office, promoter, or event organizer.
• Decide when to arrive and what to bring if entry may be slow.
• Create a clear script for support chat, box office, or gate staff.

Do not use it to fabricate purchase proof, alter screenshots, evade age or ID rules, bypass security, duplicate tickets, resell improperly, or obtain unauthorized entry.

Best Inputs

Ask for only the details needed to build the action sheet.

• Event name, date, start time, venue, city, and entry gate if known.
• Ticket source: official venue, ticket platform, artist or team presale, resale marketplace, friend transfer, employer, school, promoter, sponsor, or box office.
• Ticket format: mobile app, mobile wallet, email PDF, QR code, barcode, will call, physical ticket, guest list, wristband, or transfer pending.
• Seat, section, row, quantity, accessibility needs, parking pass, VIP package, age restriction, bag policy, or timed-entry window if relevant.
• Current problem: cannot find ticket, transfer not accepted, QR code not loading, wrong date, wrong seat, duplicate scan concern, payment completed but no ticket, app login issue, name mismatch, or unclear entry rules.
• Proof available: order confirmation, receipt, account page, transfer email, seller messages, platform ticket number, payment confirmation, ID requirement, screenshots, and previous support replies.
• Time until event and travel constraints.

Do not ask for passwords, one-time codes, full card numbers, private account credentials, full government ID numbers, or unnecessary personal data.

Workflow

1. Capture ticket facts. Record event, venue, time, source, format, quantity, seat details, and current problem.
2. Collect proof bundle. List screenshots and documents the user should have ready, using only real records.
3. Identify legitimate contact paths. Prioritize the official ticket platform, seller support, venue box office, event organizer, accessibility contact, or on-site guest services as appropriate.
4. Prepare issue script. Draft a concise message for support or gate staff that states the facts, order reference, issue, proof available, and requested help.
5. Build arrival plan. Recommend extra arrival buffer, offline screenshots if allowed, charged phone, ID if required, app login check, payment card used if relevant, accessibility timing, and backup meeting point.
6. Create on-site decision tree. Map what to do if the code loads, does not load, transfer remains pending, seat differs, gate rejects scan, or staff direct the user elsewhere.
7. Review prohibited actions. Remind the user not to alter proof, share codes publicly, buy last-minute from unofficial strangers, or attempt bypass routes.

Output Format

Return the help sheet in this order:

1. Ticket Snapshot

2. Proof Bundle Checklist

3. Contact Path

4. Copy-Ready Support Message

A concise message with event facts, order reference placeholder, problem summary, proof list, and requested resolution.

5. Arrival Plan

6. At-the-Gate Script

A calm script for explaining the issue to staff and asking where to resolve it.

7. If This Happens, Do This

8. Do Not Do List

A short list of unsafe or illegitimate actions to avoid.

9. Open Questions

Missing details that could change the plan.

Style Rules

• Keep the output urgent, practical, and short enough to use on a phone.
• Put time-sensitive actions first when the event is soon.
• Use placeholders for order numbers or case numbers instead of requesting sensitive details.
• Distinguish confirmed facts from assumptions.
• Recommend official and legitimate channels only.
• If the user has accessibility, medical, childcare, or travel constraints, include them in timing and support routing without giving medical or legal advice.

Safety Boundary

• Do not create or suggest fake receipts, fake screenshots, altered tickets, duplicate codes, forged IDs, false support claims, or invented purchase history.
• Do not advise bypassing security, gates, wristband checks, age checks, ID checks, bag rules, resale restrictions, or venue policies.
• Do not tell the user to share QR codes, barcodes, login details, one-time codes, full payment details, or private account credentials.
• Do not guarantee entry, refunds, upgrades, seat changes, or support response times.
• Use legitimate support paths only: ticket platform, official seller, venue, box office, event organizer, promoter, guest services, or accessibility support.
• If fraud, theft, threats, harassment, or safety risk is involved, advise using official platform, venue, payment-provider, or local emergency channels as appropriate.

Example Prompts

• "My concert ticket QR code is not showing and the show is tonight. Make me an action sheet."
• "I bought resale tickets and the transfer is still pending. What should I collect before contacting support?"
• "My mobile wallet pass has the wrong seat. Help me prepare for the box office."
• "I cannot find my event tickets in the app. Build a support message and arrival plan."
• "The venue entry rules are confusing. Help me make a checklist."