Studio data
Scheduling · Bookings · Attendance · Credits · Payments · Satisfaction
The GE2studio platform
Your studio’s day-to-day, finally connected.
GE2studio is progressively bringing scheduling, bookings, members, credits and payments together. The pilot foundation, features in preparation and future developments remain distinct. Each activation is configured, tested and approved with the studio.
Manager architecture
One product. Three depths.
Essential reduces everyday noise. Smart is designed to prioritise, explain and prepare decisions. Advanced will open up detailed analysis. Data and business features stay the same.
Understand the Manager modes The initial V1 targets Essential as well as the foundations and first Smart components. Full Smart is in preparation; full Advanced remains on the roadmap.
How GE2studio intelligence worksSmart uses the same data
Smart uses the same data
as daily operations.
The Manager Copilot is designed to explain a situation and prepare a decision using authorised data. Essential, Smart and Advanced are three depths of the same product, in the same studio workspace, with the same data and permissions. Smart is the planned default mode.
Rules, calculations and indicators
Rules · Permissions · Calculations · History · Provenance
Copilots
GE2studio
The planned Smart journey: spot, explain, simulate, quantify, decide. After the decision, measure the result.
01 — Scheduling & bookings
A schedule that is easy to keep up to date.
Operator view
Fictional product scene · illustrative data
Schedule
Week of 24 August
Time
Class
Coach
Occupancy
Reformer Flow
Camille
10/12
Mat Pilates
Lou
8/14
Reformer Power
Camille
12/12
Vinyasa Yoga
Nora
14/16
Reformer Flow
Camille
11/12
Advanced scheduling rules
In preparation
An exception for one class without recreating the series.
Rules in preparation will allow a setting to be specified for the studio, an activity, a series or a session. The activity retains its identity.
-
01
Activity template
Reformer
The shared descriptive framework.
-
02
Series
Wednesday · 17:00
The recurring schedule.
-
03
Session
Wednesday 2 September
The exception and its history.
-
01
Conflicts before publication Room, coach, capacity and availability must still be checked before opening the class for booking.
-
02
Rule sources The intended system retains the rule version and the level from which each value originates.
-
03
Consequences explained The intended system shows the classes and settings affected before activation.
02 — Offers, credits & payments
Sell an offer. Track its use.
The catalogue, credits and their history are integrated in a controlled environment. The complete journey, per-offer rules, payments and reconciliation remain in preparation until validated.
Pilot
Catalogue and credits
In preparation
Journey & rules
The purchased price and rule remain clear.
Passes, class cards, credits and subscriptions retain their price, currency, taxes, validity, restrictions and sale version.
A balance that is easy to check.
Every purchase, allocation, debit, recredit or expiry leaves a record. A correction adds a compensating entry without erasing history.
From payment to reconciliation.
The intended system distinguishes payment authentication, success, failure, retry, refund and reconciliation. Purchased access would only become available once the required status is confirmed.
A subscription with a consistently clear status.
Renewal, late payment, reminders, grace periods and suspension must remain tracked with a consistent status.
Per-offer rules
In preparation
Each offer can have its own rules.
The same class may have different booking conditions depending on the product held, with the consequences visible before confirmation.
Catalogue, credits and history
Pilot
Integrated foundation; activation, studio configuration and testing are still required.
10 credits
- Places per booking
- Up to 3 places
- Validity
- Fictional example
- Consumption
- 1 credit / place
1 place per class
- Use
- Named member only
- Cycle
- Monthly
- Renewal
- Automatic
03 — Member experience · designed for mobile
Buy, book and track credits.
The mobile journey is designed to let members buy, book, cancel and track their credits. It remains in preparation and must be tested end to end before being described as available.
In preparation
Mobile purchases and bookings
In preparation
See the conditions before paying.
The planned journey makes relevant conditions visible before payment, then connects the purchase to the entitlements obtained, the booking and the history.
-
01
Understand The offer
-
02
Check Price · validity · restrictions
-
03
Buy After reading the rules
-
04
Receive The entitlement obtained
-
05
Book With the consequences visible
-
06
Track Credits · subscription · history
Before payment Price, validity, restrictions, cancellation and compatibility.
04 — Communications & operations
The right message, at the right time.
The roadmap includes a GE2studio notification centre and transactional email. SMS and WhatsApp would only be evaluated after the provider, consent, costs and fallback solution have been validated.
Trajectory- Contextual notifications Confirmations, cancellations, waitlist updates, changes and payments should remain linked to their business event, without duplicate messages.
- Supervised actions Sensitive operations should still require human confirmation.
- Role-based visibility Each person would access what they need, according to their permissions.
- Visible incidents Payment and notification failures should remain identifiable and actionable.
05 — Member request tracking
Every request has an owner.
Every request has an owner.
Sensitive actions still require approval.
These scenes describe future developments and display their status. No third-party connector is presented as already operational.
Member request tracking
Trajectory
One request, one owner and a history.
The planned development brings together relevant context, assigns an owner and retains human approval before any sensitive action.
Email
WhatsApp
Instagram
Studio
Connectors to validate · manual entry possible depending on scope
- Conversation
- Member
- Owner
- Status
- History
- Last message
- Summary
- Proposed action
Human approval
Proposing is not executing.
Suspensions, refunds, credits and scheduling remain subject to permissions, confirmation and audit.
Waitlist
In preparation
Automate without losing the studio's rules.
The intended system provides a controlled, explained place offer, without processing the same event twice. Response windows and cut-off times must still be validated with the studio.
-
1
Place released The event is checked
-
2
Eligible member Entitlement and rule checked
-
3
Place offer Confirmation or decline according to the rule
-
4
Next member Once only, with no duplicate debit
06 — Switzerland, payments & connectors
Integrations
Integrations
with an explicit status.
Swiss payments & integrations
Check every integration before activation.
No payment method or third-party connector is presented as available until its operation, permissions and tests have been validated.
Payments
Payments undergoing integration and testing; no production activation announced.
Technical approach and Swiss scope to validate.
Method, receipt and reconciliation to define before any commitment.
Connectors
To review if the studio already uses this service at launch; contract and technical access to confirm.
Conversation tracking and sender identification to validate.
Only through official mechanisms, with confirmed consent and feasibility.
Access permissions, coach agreement and terms of use to define.
07 — Critical operations
The details that prevent disruption.
The interfaces, rules and figures shown are fictional examples. They describe no real customer and do not demonstrate availability. Only the displayed status and confirmed contractual scope are authoritative.
Scheduling & exceptions
Recurrences, conflicts, cancellations and replacements follow explicit transitions.
Members & waitlists
The intended system must connect profiles, consent, place offers and history. Waitlist automation remains in preparation.
Identity & access
Accounts, roles, consent and access permissions are separated for Managers, Coaches and Members.
Payments & refunds
Failures, retries, refunds and reconciliation are not treated as the same event.
Event-linked messages
In the intended system, every message originates from a business event and retains its status.
Attendance, satisfaction & follow-up
Depending on the validated rule and activation of the pilot foundation, attendance status can trigger a short questionnaire. Rating, reason, optional comment and callback consent must remain separate and traceable.
See the satisfaction journeyAdministration, search & exports
Search, manual interventions, action history, exports and reports remain restricted to authorised roles.
Backup, recovery & monitoring
Frequency, retention, recovery tests, monitoring and incident procedures are checked and documented before go-live.
Onboarding & support
Configuration, onboarding and support are defined in the offer; channels, hours, escalation levels and responsibilities are confirmed before go-live.
One product.
The right depth at the right time.
Explore the scheduling examples and rules in preparation. The illustrative data helps explain the journey; it does not describe any real studio.
Revisit the scheduling example