Capabilities, arranged by the work

Make the next wellness decision easier to see.

Smoozen brings discovery, planning, coordination, operations, governance, and integration patterns into one calm layer for client teams. Pick the slice that fits your operating model; expand only when ownership and evidence are ready.

Bounded toolkitTenant-, role-, and entitlement-aware
Capability principle

Advisory by design

Suggestions and plans remain reviewable proposals, never final canonical records.

Capability principle

Human review ready

No-match, stale, denial, and safety-sensitive states route to accountable people.

Capability principle

Approval gated

Integrations, payments, messaging, and cross-client visibility require separate configuration and approval.

A connected toolkit

Clear capability without a crowded control room.

Every surface is tenant-, role-, and entitlement-aware. AI may assist with suggestions, but authenticated code and client-owned workflows remain authoritative.

01

Discover

Tenant-scoped directories, approved provider profiles, services, venues, and availability with freshness visible.

02

Plan

Bounded wellness requests become advisory options that client teams can review, adjust, and explain.

03

Coordinate

Programmes, groups, workplace planning, and handoffs keep accountable owners in the loop.

04

Operate

Dashboards, readiness views, usage summaries, and controlled imports make day-to-day work easier to see.

05

Govern

Entitlements, audit, consent boundaries, safety routing, and human-review states keep capability proportional to authority.

06

Integrate

Credential-safe patterns support embedded, client.smoozen.com, and server-to-server experiences when separately approved.

Progressive adoption

Start with one workflow. Grow with confidence.

  1. 01
    Choose the slice

    Begin with a directory, planner, programme, or dashboard that has a named client owner.

  2. 02
    Prove the boundary

    Confirm tenant scope, consent, freshness, safety routing, and the client system of record before enabling more.

  3. 03
    Expand deliberately

    Use plan entitlements and approval gates to add capability without turning one pilot into a bespoke tenant app.

Capability boundary: Payments, WhatsApp, safety decisions, canonical bookings, identity, consent, and final records are never enabled by a tier label alone. They require the applicable client-authoritative workflow and separate approval.

Compare plansSee the workflow