Fan account chat concierge for loyalty and membership questions
Problem
Supporters who want to know their loyalty points balance, renewal date or seat allocation cannot get an answer outside office hours, and even during office hours the answer means a supporter services agent opening three separate screens, the CRM record, the ticketing account and the loyalty ledger, to piece one reply together. Simple questions arrive by email or a webform and sit in a queue for a day or two before anyone replies. Around renewal periods and after a run of good results, the queue backs up further and the same three questions, points balance, renewal date, seat details, make up most of the volume, crowding out the enquiries that actually need a person.
Product idea
A chat window in the app and on the website that answers from the supporter's own account rather than from a general help page. Ask how many points sit in the loyalty balance, when membership renews, or what seat is booked for Saturday, and the answer comes straight from the record, not a script. Anything the record cannot settle, a dispute, an accessibility request, a complaint, is handed to supporter services as a structured ticket with the conversation attached, so nobody has to explain themselves twice. It does not process payments, issue refunds or change a booking. Those stay on the existing checkout and account management flows.
Who it is for
Supporter services agents answering the routine share of enquiries, the CRM manager who owns the underlying record, and the Head of fan engagement or digital product manager who would sponsor it.
Possible first version
A chat widget in the app and web account area, backed by a read-only export of loyalty balance, renewal date and seat data loaded from a CSV during the prototype rather than a live feed. It covers three question types: points balance, renewal date and seat lookup. Anything else routes straight to a supporter services email queue as a structured ticket. There is no live connection to the CRM or ticketing system in version one, no payment handling, and no ability to change a booking or redeem a reward through the chat itself.
- Build classification
- Workflow application
- Rough effort
- 4-6 week first release
- Roles involved
- Supporter services lead, CRM manager, Head of fan engagement, Digital product manager
- Relevant to
- Professional club, Women's league, Venue & stadium operator, League office
- Systems in play
- CRM platforms, Ticketing systems, Loyalty and rewards tools, Mobile apps
- Product framing
- Voice or chat interface
Questions we get asked
Isn't this just another inbox for supporter services to check?
It removes the routine, repeatable share of the queue rather than adding to it. Points balance, renewal date and seat lookup make up most of the simple enquiries, and those get answered without a person touching them. What lands in the supporter services queue afterwards is what could not be answered from the record: a dispute, an accessibility request, a genuine complaint. If nobody is checking that escalation queue promptly, the tool has just moved the backlog rather than reduced it, and that ownership question needs answering before build starts.
Does this replace our CRM or ticketing system?
No. It reads from them and writes nothing back in version one: the customer record, the ticket and seat data, and the loyalty ledger stay exactly where they are, owned by the systems you already run. What this adds is a front end that can answer a personalised question in the moment instead of a supporter services agent doing the same lookup by hand. If those source systems are unreliable or out of date, the chat will repeat whatever they say, so the answers are only as good as the records behind them.
What happens if a supporter asks it to redeem a reward or change their seat?
It says it cannot do that and points them to the normal account or checkout flow, or to supporter services if the request is unusual. Redemption and seat changes touch money, availability and sometimes a physical ticket reissue, and getting any of that wrong is expensive to unwind. Version one is deliberately read-only: it can tell a supporter what they are entitled to, not act on it. Adding write access is a separate, later decision, not an assumed next step.
What data does it need on day one to be useful?
A read-only export covering three fields per supporter: loyalty points balance, membership renewal date and current seat or ticket allocation. That can start as a CSV pulled manually from the CRM and loyalty platform while the prototype is tested, rather than a live connection. The narrower the starting scope, the easier it is to check that the answers are actually correct before anyone trusts it with a wider set of questions.
Is this your workflow?
Tell us one sports workflow that still runs on paper, spreadsheets, WhatsApp or an outdated system. We will map it and show you what a simpler product looks like.
Tell us about itMore in Fan engagement & personalisation
- After-hours membership cancellation save lineA phone line that answers membership cancellation calls after hours, offers a pause or downgrade, and hands anyone who still wants to leave to a retention specialist with the reason already recorded.
- Email and push opt-out spike diagnosis assistantAn assistant that checks a campaign with an unusually high unsubscribe rate against past sends and shows which shared trait is the likely cause.
- Fan drop-off root-cause assistantAn assistant that checks a recurring campaign or renewal drop-off against the conditions present in similar past drops, and shows the specific instances behind the pattern instead of a guess.