Customer Workflows

How real Nestlings customers get things done, split by where the work happens — the mobile app (daily, hands-on) or the web dashboard (setup, records, reports).

📱 App workflows (mobile)

Getting a family connected

Real world: Sunny Days Home Daycare enrols a new child, Maya. The provider needs Maya's mom linked to the app so she can see daily updates.

sequenceDiagram
    participant P as Provider
    participant G as Maya's mom
    participant App as Nestlings App

    P->>App: Add Maya, generate invite code
    App-->>P: Invite code: 7F3-K9Q
    P->>G: Text the code
    G->>App: Sign up, enter code
    App-->>G: Maya's day appears — meals, naps, photos
    App-->>P: Mom shows up as Maya's guardian

A new educator joins the team

Real world: Sunny Days hires a second educator, Priya, for the toddler room.

sequenceDiagram
    participant O as Owner/Director
    participant S as Priya (new educator)
    participant App as Nestlings App

    O->>App: Invite staff — role: educator
    App-->>O: Invite code
    O->>S: Share code
    S->>App: Sign up, enter code
    App-->>S: Joins with scoped access — no billing, no settings

A child's day, recorded and shared

Real world: Priya logs Maya's lunch, nap, and a diaper change between 12:00 and 2:30pm. Maya's mom sees each entry the moment it's saved — no end-of-day summary to wait for.

flowchart LR
    A[Educator opens Maya's day] --> B[Log lunch, nap, diaper]
    B --> C[Attach a photo]
    C --> D[Save]
    D --> E[Parent gets a push notification]
    E --> F[Parent sees it live in the Today tab]

Check-in, check-out, and fixing a mistake

Real world: Priya forgets to check Maya out at pickup. She catches it 20 minutes later and corrects it — Nestlings allows two corrections before the entry locks, so the record stays trustworthy for licensing.

flowchart TD
    A[Child arrives] --> B[Educator checks in]
    B --> C[Child picked up]
    C --> D[Educator checks out]
    D --> E{Mistake noticed?}
    E -->|Yes, within 2 corrections| F[Undo + re-enter]
    E -->|No| G[Record stands]
    F --> G

🖥️ Dashboard workflows (web)

Centers and agencies manage child and guardian records from the dashboard — the app shows the same roster read-only. This keeps one source of truth when multiple staff touch the same records.

Enrolling a child (center or agency)

Real world: Sunny Days' director enrols Maya from the dashboard: profile, room assignment, allergies, emergency contact, and her mom's contact info as guardian — all in one form, done before Maya's first day.

flowchart TD
    A[Director opens Children → Add] --> B[Profile: name, room, schedule]
    B --> C[Allergies, medical notes, health card]
    C --> D[Emergency contact]
    D --> E[Add guardian: Maya's mom]
    E --> F[Guardian gets invite code]
    F --> G[Child appears in app roster — read-only for staff]

An agency onboards a new day home

Real world: Little Nest Agency oversees a dozen licensed day homes. They add a 13th home run by a new operator, Fatima, who's never used Nestlings before.

flowchart TD
    A[Agency adds a new day home] --> B[Agency mints operator invite code]
    B --> C[Fatima downloads the app]
    C --> D[Fatima enters the code]
    D --> E[Fatima runs her home day-to-day in the app]
    E --> F[Agency manages Fatima's enrolled children from its own dashboard]

A child moves to a different home

Real world: A family relocates across the city. Their agency transfers the child's file to a day home closer to their new place — nothing is lost, and the same parent login keeps working.

flowchart TD
    A[Open child profile] --> B[Transfer to another home]
    B --> C[Reason required: relocating]
    C --> D[Old home: enrollment withdrawn, history kept]
    D --> E[New home: fresh enrollment, profile copied over]
    E --> F[Guardian re-invited at new home]
    F --> G[Same parent account, same login, new home's feed]

Month-end reporting

Real world: It's the first week of the month. Sunny Days' director pulls attendance for a licensing inspection and, in February, prints tax receipts for every family's income-tax claim.

flowchart LR
    A[Reports tab] --> B{Which report?}
    B -->|Licensing| C[Monthly attendance — Print/PDF]
    B -->|Subsidy| D[CWELCC summary — claim numbers + CSV]
    B -->|Tax season| E[Annual tax receipts — one per family]
    B -->|Program review| F[Activity report — per child, CSV]

Why the split? Daily, hands-on work — attendance, daily sheets, messaging, billing a family — happens on the phone, where staff already are. Setup, records, and reporting happen on the dashboard, where a bigger screen and keyboard make data entry and printing easier. See Getting Started for the full role breakdown.

← InvitesBilling →