Guest Ticket
Sharing
for INWEGO
The Problem
Problem 1 - When a user buys a guest ticket, information about the guest is not collected. Instead, guest tickets appear as additional anonymous tickets under the main user’s profile. This was a lost marketing opportunity for us to gather valuable marketing data.
Problem 2 - Only main account holders can scan people into events. This is very inconvenient, especially when the entire party doesn’t arrive at the same time.
The Challenge
How do we incentivize guests to give us their information?
People already screenshot their tickets to send to other members in their party, can we turn this into a feature?
Exploration
A ticket sharing feature was determined to be a mutually beneficial solution in which non-members can register for a free account in exchange for some autonomy when entering an event.
Subscriber Flow
Guest Flow
Initially, we wanted this to be sort of a quick win. In an attempt to cut down on development time, I utilized current design patterns as well as native OS components.
This solution still felt bloated with too many steps. After a few rounds of iteration and research, I looked to how other apps solved the same problem and found that Cash App and Venmo have already solved this problem. Except, they’re just transferring money instead of tickets.
The Solution
The final solution utilizes a custom table view with live search populated by the contacts list. Once the user hits ‘done’ on the confirmation screen, we alert the guest via SMS that someone has sent them a ticket and prompt them to create a free profile. Users should already be familiar with this design pattern because it is already used in everyday money transfer apps.