Event Ticket Name Transfer Support Workflow Builder

Build a support workflow for event ticket name transfers, attendee substitutions, identity checks, deadlines, fraud controls, and organizer handoffs.

Prompt Template

You are an event ticketing support operations lead designing a workflow for attendee name transfers and ticket holder changes.

Event type: [conference, festival, workshop, theatre, sports, fundraiser, training, expo]
Ticket types: [general admission, reserved seat, VIP, student, group pass, sponsor, waitlist, credentialed]
Transfer policy: [allowed, not allowed, deadline, fee, organizer approval, one transfer only]
Identity requirements: [ticket purchaser, attendee name, ID check, company email, membership, age restriction]
Ticketing platform: [Eventbrite, Ticketmaster, Universe, Tixr, custom, spreadsheet, venue box office]
Common requests: [wrong name, gift ticket, employee substitution, resale, typo, illness, travel issue, group admin change]
Event timing: [weeks out, same week, day before, at door]
Systems available: [ticketing admin, CRM, payment processor, badge printer, access control, helpdesk]
Fraud risks: [chargeback, duplicate QR code, resale scam, stolen account, high-value VIP pass]
Escalation teams: [organizer, box office, security, finance, registration desk, legal/compliance]
Customer tone: [clear, calm, policy-led, premium, friendly]
Constraints: [nonrefundable tickets, tax invoices, credential rules, accessibility, privacy]
Success metrics: [first-contact resolution, transfer completion, door issues, fraud escalations, CSAT]

Create:
1. Triage decision tree by ticket type, request timing, policy, and verification status.
2. Verification checklist that protects purchaser and attendee privacy.
3. Agent workflow for typo correction, attendee substitution, group transfer, gift transfer, and denied transfer.
4. Customer macros for approved transfer, missing info, deadline passed, policy exception review, and at-door escalation.
5. Internal handoff template for organizer, box office, security, or finance.
6. Fraud and abuse red flags with neutral language and escalation paths.
7. Badge, QR code, access-control, and resend checklist after a transfer.
8. Help center article outline and pre-event email copy to reduce transfer tickets.
9. Accessibility and name privacy considerations.
10. Metrics dashboard and QA checklist.

Do not expose full ticket codes, payment details, or another attendee's personal data. Do not override event policy without the approved owner.

Example Output

Transfer Triage

1. Confirm the requester is the purchaser, group admin, or authorized attendee.

2. Check ticket type and transfer deadline.

3. If transfer is allowed, update attendee name, invalidate the old QR code if the platform requires it, resend the ticket, and log the audit note.

4. If deadline passed, route only approved exceptions to organizer review.

5. Escalate VIP, age-restricted, credentialed, or suspected resale cases.

Approved Transfer Macro

Hi [Name], the attendee name on ticket [ticket reference] has been updated to [new attendee]. We have resent the ticket through the official ticketing system. For security, the old ticket link should no longer be forwarded or used.

Internal Note

Requester verified, ticket type, transfer deadline, old attendee, new attendee, QR invalidated yes/no, resend timestamp, exception owner if any.

Tips for Best Results

  • 💡Ask for requester authority before changing attendee details.
  • 💡Resend tickets through the official platform instead of copying QR codes into chat.
  • 💡Separate simple typo fixes from true transfers because the risk and policy may differ.
  • 💡Have a day-of-event escalation path for registration desk and access-control problems.