CRM & Member 360
A CRM whose data comes from activity, not from manual entry
Every payment, check-in and purchase writes itself to the member profile. Nobody re-enters data, and no report is assembled from scratch.
Talk to usHow this differs from an ordinary CRM
A general CRM is an empty space you have to fill, and its quality depends on how disciplined the person typing is. FanHub has no member-entry form, because profiles are built from transactions that already happened: dues paid, a QR scanned at the meeting point, an order in the club shop. What you are looking at is a record, not a claim.
One member's record
- Member number
- Tier and season
- Attendance
- Points balance
- Spend
- Contact (masked)
- Tags and notes
- Consent
Written when dues clear, not when a form is submitted. Active or lapsed is derived from the season, so there is no marking work to do and no two officers holding different versions of the list.
The 360° member profile
Membership history by season, verified attendance, points balance, order history and messages sent. On one page, drawn from the same ledgers finance reads.
Segments from real behaviour
Build segments from signals that record themselves: tier, membership status, attendance count, last check-in, points, purchase history and internal labels. A segment stores its filter. Never a list of people. So who matches is recomputed every time it is used.
Import your old list without creating fake accounts
Upload your member spreadsheet; the contacts land as staged data, not accounts. Members claim themselves through an invitation and a verified login, and consent is captured at that moment. So your list stays made of real people.
Renewals that close the loop
The system knows who has not renewed into the new season and how many times they have already been reminded. One button turns that list into a segment, then into an announcement, through the same quota and record-keeping as everything else.
What legal usually asks
- Data resides in Indonesia (Jakarta), per UU PDP.
- Your organisation is the data controller; FanHub is the processor.
- Every staff access to personal data is logged, with the name of whoever opened it.
- Consent is separated by purpose, appearing in a directory is not agreement to receive promotions.
- Full export at any time, on any plan. The data belongs to your organisation.
Common questions
Does this replace the CRM we already use?
For membership and activity data, yes, because it is sourced from transactions that happen inside FanHub. For a corporate sales pipeline or a support-ticket queue, no; that is different work and we do not pretend to do it.
How many members can it hold?
There is no limit, on any plan. Member count is never a basis for billing at FanHub, and exporting that data is never locked behind a plan either.
What if we want to move platforms later?
A complete CSV export is available to the account owner at any time, contacts included. We treat leaving easily as part of the reason to arrive.
Who can see member data?
Only staff in roles you grant access to, and every time they open it the access is logged. Staff cannot change a member's consent. That belongs to the member.