Needs attention
Customers and work waiting on somebody here.
My work
Recent customer activity
The latest across memberships, enquiries and calls.
OneFit Central reads live customer data and records every action against your name. Sign in with your OneFit staff account.
Customers and work waiting on somebody here.
The latest across memberships, enquiries and calls.
Leads, callbacks and follow-ups that need you, most time-sensitive first.
Your moves through the pipeline this month.
The time shown is when the appointment was set, not when it takes place.
Your calls today.
Today, against yesterday.
Open work across the club, most urgent first. Urgency follows OneFit's rules.
The sales pipeline, calls, memberships and open work, today.
Every OneFit SalesTrail phone, today.
Sale exceptions, failed membership payments and tasks that are still open.
Membership sales and trials from Glofox, counted by the Sales Dashboard rule.
Which SalesTrail user, ClubPlanner seat and Glofox staff account belongs to each member of staff. A link decides whose leads, calls and sales a salesperson sees. An exact email match is proposed for you; everything else waits for your confirmation, and anything ambiguous cannot be linked at all.
Whether appointments are available, and the locations, appointment types and hosts they use. Nothing here books or shows an appointment, and nothing is filled in unless you choose a starting point.
Low-level identity diagnostics. Record pairs the earlier resolver flagged but never merged. Central has never combined two humans on inferred evidence, and a rejection is honoured forever. ClubPlanner mapping is no longer decided here.
Real ClubPlanner CRM records evaluated against the live Glofox population, with SalesTrail call activity attached by phone identity. Every suggestion shows the evidence behind it and the values each system actually holds. Nothing here is confirmed automatically: HIGH CONFIDENCE is a suggestion, not a decision.
An operational diagnostic, not a product screen. Three separate facts are reported for every system: what the provider’s API supports, what OneFit can actually reach today, and what Central has implemented. They are never merged into a single “connected” badge, because a provider supporting something does not mean we can do it. No credential value is ever shown here, only where the credential lives.
Central searches and profiles from its own read model, refreshed from each provider by bounded, checkpointed syncs. Every run is recorded against the person who started it. A provider that is down keeps its last successful sync, labelled with its age. It is never shown as “no data”. Nothing here writes to a provider.
Read-only analysis. Nothing here confirms or merges anything. Every figure is labelled Sample, Partial or Complete, so a partial scan can never be read as the whole population.
Enquiries whose customer could not be decided automatically. An enquiry that matches exactly one member is associated without anyone being asked, and an enquiry that matches nobody is a prospect rather than a problem. Neither appears here. What is left is the small number of cases that genuinely need a person to look.
Who can sign in to OneFit Central, and what each of them can do. A role decides access: there are no per-person permissions to set here. Changing somebody’s role, setting a new password or disabling their account signs them out of Central straight away, and every one of those actions is recorded against your name.
How OneFit Central is running, and the tools that change it. This is an operational diagnostic, not a product screen. Staff working with customers never need anything on this page.
Per-source connection state from the last sync, with real record counts from the read model. “Degraded” means the last sync was partial or is stale; data shown elsewhere is still the last successful read.
Configuration and data-integrity states that are deliberately kept off every staff screen: sources that are not configured, never synced or behind, and the identity questions still waiting on a decision.
What Central is currently permitted to change in Glofox. Two separate controls decide it: a global switch, and a list naming each approved action. Turning the global switch on enables nothing on its own.