# Mom Alarm Clock beta recruiting — approval draft

**Status:** Review only. Nothing in this packet authorizes posting, mailing a tester group, or describing the Android install link as live. Prepared 2026-10-01. The Android opt-in instructions below are staged for the first verified closed-test release. The iPhone invitation likewise needs a fresh capacity/build check before publication.

## One message for owned social pages

Still going back to your child's room to wake them up? Mom Alarm Clock puts the alarm on their phone and the controls on yours. Set or change the alarm from your phone. To stop it, they hold a button, answer a question, play a quick game, or scan a printed code. If they're not up after the wait you chose, your phone is told.

We're looking for U.S. parents to test real mornings with two phones. This is a test build: keep a backup alarm for anything that matters. The parent's result can sometimes be slow to appear after the child finishes a wake-up check. Please stay in the beta for at least 14 days and tell us what goes wrong through Help & feedback in the app or momalarmclock@gmail.com. Please don't share a child's name or email in comments.

**Android closed beta — use an Android phone for you and one for your child.**
1. Join the tester group: https://groups.google.com/g/momalarmclock-beta
2. Then opt in and install on each phone with the same Google account that joined the group: https://play.google.com/apps/testing/com.momclock.momalarmclock

Each testing phone needs a Google account in the group, including the child's phone. If the second link says the app is unavailable, check that step 1 was completed using the account signed in on that phone.

**iPhone beta:** https://testflight.apple.com/join/j28Ec4ZB

Tag a parent who has had to make the same trip back to the bedroom. Questions are welcome; please keep children's details private.

## Platform cuts

### Facebook page and parent groups where self-promotion is allowed

Use the full owned-page post above. In a parent group, first check its rules and identify the poster as part of Mom Alarm Clock. Suggested opener: “I work on Mom Alarm Clock, and we're asking U.S. parents with two Android phones to test real mornings. Moderators, please remove this if beta invitations are not allowed here.” Then use the same Android two-step instructions, beta caveat, and feedback route. Do not post in groups that prohibit promotion, repeat the invitation in the same group, or solicit children's details.

### Instagram and TikTok caption

Still walking back to your child's room after their alarm? Set their alarm from your phone. Their phone rings; they finish a wake-up check by holding a button, answering a question, playing a quick game, or scanning a printed code. Your phone reports if they aren't up after the wait you chose.

U.S. parents with two Android phones: join the closed beta in this order. (1) https://groups.google.com/g/momalarmclock-beta (2) Opt in and install on **each** phone with its joined Google account: https://play.google.com/apps/testing/com.momclock.momalarmclock

iPhone beta: https://testflight.apple.com/join/j28Ec4ZB

Please test real mornings for at least 14 days, keep a backup alarm, and report problems through Help & feedback in the app or momalarmclock@gmail.com. The parent's result may appear slowly after a wake-up check. Tag a parent who could use this. Please don't put children's details in comments.

**Publishing note:** Some apps do not make caption URLs tappable. Before approval, verify the exact profile link or pinned comment takes people to a page showing **both Android steps in order** and the iPhone link. Do not publish a caption with an inaccessible install path.

### X thread (four posts; publish together only after approval)

1/4 Still going back to wake your child? Set their alarm from your phone. The alarm rings on their phone. We're looking for U.S. parents to test real mornings with two phones. This is a test build; keep a backup alarm for anything that matters.

2/4 To stop the alarm, the child holds a button, answers a question, plays a quick game, or scans a printed code. It keeps ringing until the check is done or an allowed snooze is used. If they aren't up after the wait you chose, your phone is told.

3/4 U.S. Android parents with two phones: 1. Join https://groups.google.com/g/momalarmclock-beta 2. With a joined Google account on each phone, opt in and install: https://play.google.com/apps/testing/com.momclock.momalarmclock

4/4 iPhone beta: https://testflight.apple.com/join/j28Ec4ZB Please test real mornings and stay at least 14 days. The parent's result can be slow after a wake-up check. Help & feedback in app or momalarmclock@gmail.com. Please don't put children's details in replies.

**X constraint:** Each raw draft post is under 280 characters; still check the final composer and link previews before posting. Keep both Android steps together and in this order.

### YouTube Community and video description

Use the full owned-page post. In a video description, put the Android group link and opt-in link on separate numbered lines near the top, followed by the iPhone link. A video is **not** approved by this copy packet; its exact media file needs Rob's separate review.

## Beta landing page draft

**Headline:** Set your child's alarm from your phone. See whether they actually got up.

The alarm rings on your child's phone. You set or change it on yours. To stop it, your child holds a button, answers a question, plays a quick game, or scans a printed code. If they aren't up after the wait you chose, your phone is told. The app does not read messages or show ads.

**Android closed beta — U.S. parents with two Android phones**

1. Join the tester group: https://groups.google.com/g/momalarmclock-beta
2. Opt in and install on each phone using the same Google account that joined the group: https://play.google.com/apps/testing/com.momclock.momalarmclock

Each phone needs a group-joined Google account, including the child's phone. The install page may say the app is unavailable if you skip step 1 or open it under another account. Please stay opted in and in the group for at least 14 days, and use the app for real mornings on both phones.

**iPhone beta:** https://testflight.apple.com/join/j28Ec4ZB

This is a test build. Keep a backup alarm for anything that matters. We're investigating a delay before the parent's phone sometimes shows that the child finished a wake-up check. Send problems through Help & feedback in the app or email momalarmclock@gmail.com. Please do not post children's names, email addresses, or schedules in public comments.

Privacy policy: https://robosecure.github.io/mom-alarm-clock-legal/privacy.html. To request deletion of an Android account and its data, email momalarmclock@gmail.com with the subject **Delete my account**. Details: https://robosecure.github.io/mom-alarm-clock-legal/delete-account.html.

## Group / email copy, held for actual Android release

### Welcome to the closed beta

Subject: Your Mom Alarm Clock Android beta steps

Thanks for helping us test real mornings. This is a test build, so keep a backup alarm for anything that matters.

1. Join the tester group with the Google account used on each phone: https://groups.google.com/g/momalarmclock-beta
2. On each phone, sign in with that same group-joined account, then opt in and install: https://play.google.com/apps/testing/com.momclock.momalarmclock

Please stay in the group and opted in for at least 14 days. Test with a parent's Android phone and a child's Android phone. After the child finishes the wake-up check, the parent's result can sometimes be slow to appear; please report when that happens. Use Help & feedback in the app or write to momalarmclock@gmail.com. Please don't email us a child's name, email address, or schedule.

### Day-three check-in, only to consenting tester-group members

Subject: How did your first Mom Alarm Clock mornings go?

Have you tried setting the alarm from your phone and using the wake-up check on the other phone? If something failed, please use Help & feedback in the app or email momalarmclock@gmail.com with the two phone models, app build, and what happened. Do not include children's names or schedules. Please remain in the group and opted in through day 14 if you can. Keep a backup alarm while this is a test build.

## Private reply templates (never request child identity)

**“App not available”:** “Thanks for checking. The Android beta has two steps. First join https://groups.google.com/g/momalarmclock-beta with the Google account on that phone. Then, while signed into that same account, open https://play.google.com/apps/testing/com.momclock.momalarmclock and opt in. Repeat on the second testing phone with its group-joined account. If it still fails, email momalarmclock@gmail.com with the error text and phone model; please leave out children's names and account addresses.”

**Slow parent result:** “Thanks for reporting it. We know the parent's phone can be slow to show the result after the wake-up check. Please send the app build, two phone models, and the approximate delay through Help & feedback or momalarmclock@gmail.com. Please keep a backup alarm during the beta.”

**How to leave/delete:** “You can leave the beta and opt out at any time, though staying for 14 days helps us complete the test. For Android account and data deletion, email momalarmclock@gmail.com with subject ‘Delete my account.’ Details: https://robosecure.github.io/mom-alarm-clock-legal/delete-account.html.”

**Child phone cannot join group:** “Thanks for telling us. Please email momalarmclock@gmail.com with the phone model and whether its Google account is supervised; leave out the child's name, email address, and schedule. We are checking which two-phone account setups the closed beta supports. Please don't change a child's account settings just to join the test.” This infers the brand support address from Rob's stated feedback route because his last instruction ended at “ask them to email”; if he supplies a different destination or procedure, replace this exact draft before posting.

## Approval and launch checks

1. Rob reviews the exact wording and channel placements; any changed copy gets another review.
2. Android owner confirms actual closed-test release, linked Google Group, opt-in and install on **both** phones, the correct build, group account requirements, feedback route, and U.S. availability. Group joining alone does not count as a Play opt-in. Do not call the install link live from unauthenticated redirects alone.
   **Family Link conflict:** Google's [Groups help](https://support.google.com/groups/answer/1067205?hl=en) says an account set up for a child under 13 cannot join a group; its [add-member help](https://support.google.com/groups/answer/2465464/add-people-to-your-group) says a child account cannot be added by any method. Rob's two-phone instructions may therefore exclude some target families. Engineering must document a supported, policy-safe setup for those families, or the final invitation must clearly narrow eligibility. Do not suggest changing a child's account or bypassing supervision.
3. iOS owner confirms the TestFlight group is open, newest intended build is offered, link capacity and feedback route. Current 2026-10-01 readback shows build 18 in the group and dated public-link metrics of 7 views / 3 acceptances for Sep 1–Oct 1; those figures are neither active tester count nor two-phone proof.
4. Verify the public page, platform profile links, tap targets, and each final character-limited post. No video goes out without its separate exact-media approval.
5. Track Google Group joins, Play opt-ins, concurrent opted-in days, actual two-phone tests, reported issues, and iPhone beta acceptances separately. The internal recruiting target is **40+ Android participants** to sustain **at least 12 concurrently opted in for 14 days**; no reward or paid tester service. No claim that any count is achieved until the console shows it.
6. The statement “no ads” and the exact two-phone/group-account setup are from Rob's current brief and require shipping-build / two-phone confirmation before publication. The latest brief is deliberately alarm-focused; older general campaign reminders copy has not been imported into this packet.

**Not included:** outbound posting schedule, paid promotion, public comments or direct outreach authorization, Android launch date, or claims of active tester counts. The child-account reply is a conservative draft pending Rob's missing words and engineering's supported setup.