Connected systems, honest boundaries

Know what connects— and what is still in review.

CoachOS connects supported payment, booking, acquisition and health journeys. Every provider below is labelled by its current production status so an implemented integration is never mistaken for general availability.

PaymentsBookingHealth
CoachOS wearable health screen showing generic recovery, strain and sleep data
CoachOS integrations screen showing WHOOP connected and Apple Health permissions
Client controlledConnect, permit, disconnect

Health connections

Use the right source—with the current access limit visible.

Apple Health and Health Connect bring in supported device records from iOS and Android. WHOOP supplies its own coaching signals for approved test members while production approval remains pending. Availability always depends on the source, device and client permissions.

WHOOP

Direct OAuth · production approval pending

Recovery, strain, HRV, sleep and workout context for approved test members while WHOOP reviews production access.

Limited access

Apple Health

Device permission required

Supported health and activity records, such as steps, when the client grants access on their iPhone.

Available on iOS

Health Connect

Device permission required

Supported health and activity records from compatible Android apps, subject to the client’s permissions.

Available on Android

Business connections

Available, limited, in review and planned are different promises.

CoachOS names the useful boundary for each provider. Provider approval, account configuration and final acceptance checks can limit access even after the underlying code has shipped.

Stripe

Payments · 0.5% CoachOS platform fee on processed payments

Coach subscription billing and supported coach offers and client payments. Stripe processes card details; CoachOS does not store them.

Available

Google Calendar & Meet

Per-coach OAuth · not generally available yet

Free/busy checks, CoachOS booking-event sync and Meet link generation are implemented. General access is pending Google’s sensitive-scope review.

In provider review

ManyChat

Integrated boundary · no native social inbox or broadcasts

Inbound lead capture and selected lifecycle flow triggers are implemented. A real connected-account inbound and outbound smoke is still required.

In acceptance review

Transactional SMS

Platform notifications only · no campaigns or coach numbers

Consent-based booking notifications are implemented with caps, quiet hours, opt-out and delivery telemetry. Twilio toll-free verification is approved; the final opted-in live-handset and signed-callback acceptance run remains.

Carrier approved · acceptance pending

GoHighLevel

Limited provisioning model

An admin-managed connection supports configured PartnerPro and CoachOS accounts. It is not a self-serve integration for every subscriber.

Configured accounts

Zoom & Outlook

No available-now claim

These integration paths are not available in production today. They remain future work rather than included-plan capabilities.

Planned

Permission before data

The client stays in control of the connection.

CoachOS only receives supported records after the client connects a source and grants the relevant access. Permissions can vary by device and provider, and the client can change or revoke them later.

  • 01
    The client connectsWhere the provider is available to them, they sign in or approve access on their device.
  • 02
    The source supplies recordsCoachOS receives only the supported data that is available and permitted.
  • 03
    The client can disconnectAccess can be withdrawn without asking the coach to change it.
CoachOS client integrations and health permission controls
Optional sharing Only the client can change it.

Extra context, including cycle sharing where supported, remains an explicit client choice.

Context, not conclusions

See the signal beside the plan.

A metric can add useful context, but it does not tell the whole story. CoachOS keeps connected data close to training, nutrition, progress and communication so the coach can ask a better question.

01

Recovery

A daily WHOOP recovery signal when available.

02

Sleep

Sleep context supplied by the connected source.

03

Strain

WHOOP strain alongside the client’s training week.

04

HRV

Heart rate variability from a supported source.

05

Steps

Device activity data when the client shares it.

06

Workouts

Imported workout records from supported connections.

The connected workflow

From source to useful conversation.

  1. 01
    Connect

    The client chooses an available provider or their supported device health source.

  2. 02
    Permission

    The client approves the supported records they want to share.

  3. 03
    Review

    CoachOS presents recent signals with the client’s wider coaching context.

  4. 04
    Coach

    The coach asks, interprets and decides. The metric never replaces the person.

Questions, answered

Integration and connected-health questions

Which health connections does CoachOS support?

Apple Health on iOS and Health Connect on Android are available with client-controlled permissions. WHOOP is implemented for approved test members while production access remains under provider review.

Which business integrations are generally available?

Stripe is available for supported billing and payment journeys. Google Calendar and Meet remain in provider review; ManyChat remains in acceptance review. Transactional SMS has carrier approval and awaits its final opted-in live-handset acceptance run. GoHighLevel is limited to configured accounts; Zoom and Outlook are planned.

Who decides what a coach can see?

The client controls the connection and the permissions available on their device. They can disconnect a source or change supported permissions later. Optional cycle sharing is also controlled by the client.

Do Apple Health and Health Connect provide the same data?

Not necessarily. Apple Health is the supported device health source on iOS, while Health Connect serves the equivalent role on Android. What CoachOS receives depends on the records available from compatible apps and the permissions the client grants.

What does WHOOP add?

For approved test members, a connected WHOOP account can provide recovery, strain, HRV, sleep and workout context. General member access depends on WHOOP approving CoachOS for production.

Does CoachOS make medical decisions from this data?

No. Connected health data is presented as coaching context. It is not a diagnosis, medical advice or a substitute for professional healthcare. The coach remains responsible for their coaching decisions.

Why might a recent value be missing?

Sync timing and record availability depend on the external provider, the client’s device, connectivity and permissions. CoachOS shows the source and recent sync context where available, but cannot create records the provider has not supplied.

One connected coaching picture

Bring useful context into the conversation.

Connect supported health sources with client-controlled permissions, then review those signals alongside the work already happening in CoachOS.