Operations

OneFit Central

Sign In

OneFit Central reads live customer data and records every action against your name. Sign in with your OneFit staff account.

Find Anyone

Search by name, phone (or just its last digits), email, OneFit person ID, Glofox member or subscription ID, or ClubPlanner record ID. Results come from Central’s read model, so they answer even when a provider is down, and every result says why it matched.

My Work

Assigned to you, from real Central records. Provider-driven queues appear here once ClubPlanner, SalesTrail and WhatsApp are connected.

Needs Attention

Operational signals derived from connected systems only. Nothing here is a placeholder count.

OneFit AI — Operations Briefing

AI summarises what Central can actually read, and states plainly what it cannot see.

Integration Health

Per-provider 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 is still the last successful read.

Recently Viewed

Stored in this browser only, so this list does not follow you between devices. Central-owned records such as notes, tasks and identity decisions are stored server-side.

Data Integrity

Record pairs the resolver flagged but has not merged. Central never combines two humans on inferred evidence alone — a person decides, and that decision is stored permanently. Rejections are honoured forever, so the same wrong match is never proposed twice.

Cross-Provider Mapping

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.

Data Sources

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.

Read Model & Sync

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.

Mapping Coverage

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.