Projects

All projects01 / 05Membership club chain

Leads, calls, messages and retention in one platform on top of the ERP

The platform was built for a club chain and runs on top of the ERP. Leads, calls, messenger chats, client retention and the trainer workspace are gathered in one place, while memberships and sales stay in the system of record.

Scale
36 screens, 11 menu sections
Roles
8 roles: database administrator, manager, CFO, club manager, marketing, sales team, club administrator, trainer
Channels
Telephony, messengers, website
Records
Memberships and sales stay in the ERP

CRM · LeadsA pipeline kanban: leads from calls, messengers and the website, each with its source, club, priority, owner and unread messages.

Context

As the business scaled, the club chain ran short of tools for day-to-day management of its client base and sales. We split the company's IT landscape: the ERP kept its role as the back end for financial accounting, billing and account control. The entire operational workflow — traffic handling, omnichannel lead processing and KPI tracking for the employees responsible for communication — was moved to a single specialized platform.

Constraints

  • Leads lost at intakeInquiries were left “hanging” between disconnected communication channels before anyone picked them up.
  • Late churn signalThe system did not track a drop in visit frequency as it happened. Lost clients surfaced in closed monthly reports, when it was already too late to save the deal.
  • Overloaded systemBecause of deep in-house customization, the core corporate system became too heavy for frontline staff. The unintuitive interface slowed down lead processing and critically increased the time needed to train new employees (time-to-productivity).

How it was

Every step was carried out, but between steps the lead waited until someone transferred it by hand. An owner appeared only after the lead was entered into the ERP, and a pause in visits was noticed in the month-end results.

Hypothesis

If calls, messages and website requests are gathered in one pipeline with an owner and a next contact date, and the trainer sees who has dropped out of their visit routine, an inquiry reaches payment more often and the client comes back sooner. The ERP remains the system of record.

Operation model

The lead stages follow a person's path to payment; after payment the platform watches the visit routine. A client's usual interval is calculated from their visits over 120 days. If the pause is longer than two intervals and longer than three weeks, but no more than 90 days, the client goes into the trainer's queue with a reason and a next contact.

Call or messagephone, messengers, website
Administrator's noteon a phone or on paper
Lead spreadsheetfilled in each evening
ERP recordafter payment
Call to the clientfrom memory
Monthly reportwho stopped coming
the lead awaits transferAdministrator and trainer workspaces
01Newcall, messenger, website
02In progressowner and next contact
03Moved to ERPclient found or created
04Convertedpayment in the ERP
05Visit routinethe client's usual interval
06Retentionreason and contact

Interface

Administrator and trainer workspaces

  1. A pipeline kanban: leads from calls, messengers and the website, each with its source, club, priority, owner and unread messages.

    1. 1An unassigned lead has a red dot; the “Unassigned” filter counts them
    2. 2Lead held by the sales team, with a timer
    3. 3Channel and club on every card
    4. 4The assistant sees the open screen and answers based on it
  2. Everything about the person and their request is on the left, messenger chats are on the right; the stage bar and the handover to an employee, another club or the ERP are in the header.

    1. 1Tags under the name: stage, club, channel, priority, owner
    2. 2Reassign to an employee or a club, move to the ERP
    3. 3The client's calls from telephony
    4. 4Messages next to the card
  3. The retention queue: who to call and why, the client's value, what to offer and how the contact ended.

    1. 1Four queue states: to process, waiting, returned, not returned
    2. 2The reason the client is in the queue
    3. 3Client value and an offer that fits the reason
    4. 4Call and messenger in one tap
  4. On the phone, the trainer sees their clients who have dropped out of their routine and marks the reason with one tap; the tabs sit under the thumb.

Specification for the technical team

Based on the code of the live platform. The client's data, credentials and brand are not carried over into the public copy.

Data sourcesERP: API and file exchangeTelephonyMessenger aggregatorWebsite, webhooksLanguage model
Operations layerAPI /api/*Pipelines and stagesVisit routine and retentionWebhook logs
Roles and devicesManager and CFOClub managerMarketing and sales teamClub administratorTrainer, phoneDatabase administrator
Interface
React 19, TypeScript, Tailwind 4. A web app with a manifest and a service worker, push notifications.
API
A single layer of server requests at /api/*, a cookie session, 112 methods: inquiries, clients, visits, retention, the specialist workspace, administration.
Data
Employees and roles, clients and their events, inquiries, calls, conversations, visits, loss reasons, retention contacts, tasks, notifications, webhook logs.
Integrations
The system of record through an API and file exchange, telephony, a messenger aggregator, website webhooks, cloud media storage, sign-in with an external account, an external language model for the AI agent.
Roles
Database administrator, manager, CFO, club manager, marketing, sales team, club administrator, trainer. Permissions are set in a matrix: sections, data and actions for each role; the trainer has a separate workspace.
Screens
36 screens in 11 menu sections: leads, clients, messages, calls, sales, visits, RFM, trainer workspace, analytics, team, integrations.
Trainer interface
On the phone, the workspace screens are tabs at the bottom and the rest is under “More”; the app installs to the home screen, and push notifications arrive right away.
Access
Screens and actions by role. Keys and credentials are kept in the cloud secret store; none are in the code.
Records
Sales and account transactions stay in the system of record; the operations layer reads them through the integration.

What changed in how the operation runs

The changes are described qualitatively. Figures are published once the client approves them.

  • 01One pipelineCalls, messages and website requests land in one pipeline, and every lead has an owner and a next contact date.
  • 02ERP stays in placeA lead is moved to the ERP through a client search; memberships and sales stay in the system of record.
  • 03Visit routineThe trainer sees who has dropped out of their usual routine, marks the reason with one tap and gets back to the client on time.

Metrics

  • Share of inquiries that reach a visittracked
  • Time to first replytracked
  • Regular clients who returnedtracked
  • Loss reasons by channeltracked