Messages and results

Secure approval pending and recorded states

Secure approval

Send this file?

Send generated report.zip to this conversation.

Secure approval

Send this file?

Send generated report.zip to this conversation.

Approval recorded. Murph will continue only if this request is still pending. Return to the Murph thread where you requested this file.

Secure approval

Send this file?

Send generated report.zip to this conversation.

Denied. Murph will not continue with this action. Return to the Murph thread where this request started.

Static share link previews

Static link unfurls

Share link previews

The 1200x630 OpenGraph cards behind links Murph or members send: approvals, referral invites, device connect nudges, and group sponsorship. Biomarker and experiment pages ship the same frame with subject-specific headlines. Each study renders the exact production card component, so the previews cannot drift. None of the cards imitates a tappable control, none promises a capability the landing page has not yet verified, and none exposes member details: link previews are fetched without authentication. Card image routes live outside route groups: grouped metadata images get hash-suffixed URLs in production, which silently breaks the advertised link.

/approve/[approvalId]

The approval link unfurl. It lands inside a conversation with Murph, right under the message that sent the link, so the headline speaks as Murph and the request details never appear.

I need
your OK.

Tap to review. The link expires soon.

Alt text: Murph needs your OK. Tap to review the request before it expires.

/r/[referralCode]

The referral link members text friends. The recipient has no Murph conversation yet, so the card introduces Murph instead of speaking as it, and stays capability-neutral so it remains true for expired links.

Meet Murph.

Your private health assistant.

Alt text: Meet Murph, your private health assistant.

/connect

Murph texts this link for first-time device connects and reconnects; the copy stays true for both flows.

Let’s connect
your device.

Wearables and health data sources.

Alt text: Let’s connect your device. Wearables and health data sources.

/groups/fund/[joinCode]

Dropped into group chats next to the group join card. Descriptive, non-imperative copy: it names what the route is about rather than promising this specific link is live.

Murph group
sponsorship.

How groups keep Murph running.

Alt text: Murph group sponsorship. How groups keep Murph running.

Clubs profiles, iMessage, and wearables

Works in iMessage

You run the club. Murph runs the challenge.

Create and run the whole challenge in iMessage. Members join from one link and connect the supported wearables they already use. Murph keeps score, sends the useful updates, and handles the busywork.

Start a challenge clubs@withmurph.ai

Run clubs · gyms · studios · fitness communities

9:41

Murph

can we see if the whole club can run 10,000 miles together in august?

Absolutely. One shared goal, August 1–31. Should walking count too?

yes, everyone should be able to help

Perfect. I’ll make the link, keep the total current, and send the updates.

ATL moves togetherAhead of pace

Miles

6,842

People

Days left

Club goal

68%+8% vs pace

iMessage

Three ways to play

Pick the energy that fits your people.

Some communities want a winner. Some want teams. Some want one huge goal everyone can move forward.

August miles together

Day 19 of 31

6,842

of 10,000 miles

78 people contributing12 days left

Every mile counts. The club is 8% ahead of finish pace.

From idea to live

One sentence. One link. Everyone's in.

Murph turns the idea into a challenge members can understand and join.

1 · Tell Murph the idea

Describe the goal the same way you would tell another organizer.

Let's see if the club can run 3,000 miles together in August.

Done. August 1–31, one shared mileage goal. Want walking to count too?

2 · Share one link

Members join and choose the exact challenge metric they want to share.

August miles together

Join the challenge

Shared

Your name and daily distance.

Private

Your chats, routes, and everything else.

Join challenge

3 · Murph keeps it moving

Progress stays current and the community hears about the moments that matter.

Club goal61%

1,830

of 3,000 miles

86 people are in. The club is slightly ahead of finish pace.

No spreadsheets required · no manual scorekeeping · no new organizer app

Wearables, handled

Different wearables. One live challenge.

Members connect a supported source they already use. Murph turns it into the exact daily stat each person approves, keeps the standings current, and checks missing data automatically.

No spreadsheets required

WHOOP

Oura

Apple Health

Garmin

Fitbit

Eight Sleep

Withings

Peloton

Polar

Automatically tracked

Score what your community already tracks.

Choose one supported metric. Murph keeps the score live.Availability depends on the connected source

Move

6 trackable signals

Steps
Distance
Elevation gain
Floors climbed
Active calories
Activity minutes

Train

8 trackable signals

Workouts
Session count
Workout minutes
Running
Walking
Cycling
Swimming
Sauna

Perform

6 trackable signals

Heart-rate zones
Workout strain
Day strain
Activity score
VO2 max
Max heart rate

Recover

6 trackable signals

Sleep duration
Deep sleep
REM sleep
Sleep timing
Resting heart rate
HRV

Nourish

5 trackable signals

Logged protein
Logged calories
Logged carbs
Logged fat
Logged fiber

For organizers

Keep the energy. Lose the admin.

Text Murph in a private organizer thread in iMessage to check the room, change the teams, prepare an update, or close the challenge. Murph remembers the rules and handles the repetitive work.

9:41

Organizer room

How many people are ready to score?

78 of 86. Five need a connection check; three haven’t shared distance.

Draft the halfway update.

Drafted. It leads with the halfway milestone and keeps the missing-data note private.

August challenge · live

Joined

Scoring

Needs help

iMessage

9:41

Murph

how are we doing?

The club is 61% to the goal and slightly ahead of pace. You’ve contributed 14.2 miles.

what do i need this week?

Another 3.8 miles keeps you on your own pace.

iMessage

For every member

One challenge. Personal support for everyone in it.

Every participant gets private support in iMessage. They can check their progress, ask what to do next, or understand a missing score without turning the club organizer into tech support.

Private by default

Share the score. Keep the rest private.

Members choose exactly what the challenge can use. Their private conversations, unrelated health history, and anything they do not select stay private.

Challenge permission

Daily running distance

Shares your daily running distance with this challenge. It does not share routes, location, private chats, or other health data.

Share with this challenge

The club sees

Challenge progress

Members choose

The metric

Private Murph

Stays private

Questions

The practical stuff.

Does it really work in iMessage?

Yes. Organizers and members talk with Murph through ordinary iMessage conversations; the web is used only when a richer setup or consent step is needed.

Does everyone need the same tracker?

No. Each member can connect a supported health source individually, and the challenge uses only the metric they explicitly share.

Does everyone join one group chat?

No. Organizers can use a small chat with Murph as the control room. Participants join from a link and receive updates privately.

Do organizers need a spreadsheet?

No. Murph keeps the supported challenge metric, standings, and missing-data checks current. Organizers can ask for the status or an update in iMessage.

How much does it cost?

Organizers buy AI usage as needed—there’s no platform fee. Members get Murph free for two weeks, then can continue on Core for $3.50/month.

Can we track something a wearable does not measure?

Tell us the activity. We’ll confirm whether its source and scoring method are supported before the challenge starts.

What can organizers see?

Challenge membership, shared challenge progress, standings, and setup status; never private conversations or unrelated health history.

Ready to run

What should your club chase first?

Tell us what you want to run, how many people might join, and when you want to start. We'll help shape the challenge and run the first one with you.

Start a challenge clubs@withmurph.ai

Private experiment results share

Ready to share

Preview your private results card, then share it or save a copy.

Download-only browser

Preview your private results card, then share it or save a copy.

Preparing preview

Preview your private results card, then share it or save a copy.

Preparing private preview

Preview recovery

Preview your private results card, then share it or save a copy.

Preview unavailable

Your results stayed private. Try preparing the image again.

Native share recovery

Preview your private results card, then share it or save a copy.

Sharing couldn't open. Try again or download the image.

Private structured-review result

Private experiment

Your results

Your progress, measurements, and conclusions for this experiment stay private in your vault.

Evidence ready for review

The baseline and follow-up evidence are ready to review.

Murph kept the evidence together without converting a qualitative observation into a numeric effect.

medium confidence

Private experiment

Your results

Your progress, measurements, and conclusions for this experiment stay private in your vault.

The review still needs baseline and follow-up evidence.

Add both planned observations before reviewing the result. The experiment remains saved.

Private experiment

Your results

Your progress, measurements, and conclusions for this experiment stay private in your vault.

The review still needs follow-up evidence.

The baseline is saved. Add the planned follow-up observation before reviewing the result.

Measured changes

Before and during the experiment

Daily measurements and declared window summaries, where available.

Resting heart rate

59bpm-2 bpm

Window statistic: average

Baseline average61 bpm3 of 3 days measured

Experiment average59 bpm3 of 3 days measured

Private experiment

Your results

Your progress, measurements, and conclusions for this experiment stay private in your vault.

Measured changes

Before and during the experiment

Daily measurements and declared window summaries, where available.

Response score

9points+2 points

Window statistic: maximum

Baseline maximum7 points3 of 3 days measured

Experiment maximum9 points3 of 3 days measured

Private experiment

Your results

Your progress, measurements, and conclusions for this experiment stay private in your vault.

Measured changes

Before and during the experiment

Daily measurements and declared window summaries, where available.

Symptom-free days

5+2

Window statistic: count

Baseline count33 of 3 days measured

Experiment count53 of 3 days measured