Staging · iMessage · 2 September 2026
Emma Automations Staging Test
Twelve scenarios that walk the new Automations feature the way a creator would: text Emma, see what she sets, see what fires, see what she stays quiet about. Each one says exactly what to send, what to expect, and what to write down.
Two rules. Send the messages exactly as written, including the casual wording; the point is that Emma understands normal speech. Note the clock time to the second when you hit send, because several checks are about timing. If Emma ever asks a question, answer it naturally and note what she asked.
Before you start
- Open the Emma Staging thread in Messages. Confirm the header says "Emma Staging", not "Emma".
- Send: what time is it for me and confirm Emma answers with the right local time and timezone. If she has no timezone, send i'm in dublin first.
- Send: what reminders do i have. Note anything already there so you can tell new ones apart.
Part 1 · Reminders
ATwo-minute reminder
2 min wait
The basic promise: say it once, get it back on time.
Send
remind me in 2 mins to check the whoop deal
short ack, then a confirmation naming a time
Expect
- Emma confirms with a clock time. That time is your send time plus 2 minutes, rounded to the minute.
- A reminder text arrives within 2 minutes 10 seconds of your send. Wording is Emma's own, mentions the whoop deal.
Record: send time to the second, the time Emma quoted, the time the reminder arrived.
BReminder at a clock time
Absolute times must land in the creator's timezone, not UTC.
Send
remind me at 6pm today to send the invoice to glossier
Expect
- Emma confirms 6pm in your local time (Dublin). Not 5pm, not 7pm.
- If it is already past 6pm, she asks whether you mean tomorrow, or sets it for tomorrow and says so. She does not silently set a time in the past.
Record: the exact time she quoted. You do not need to wait for this one to fire unless it is convenient.
CRecurring reminder
6 min wait
The same request should produce one recurring rule, not several one-offs.
Send
every 3 minutes remind me to drink water
Expect
- Emma confirms a repeating reminder.
- Two water reminders arrive about 3 minutes apart. Timing within 30 seconds of the schedule is fine; it runs on a scheduler, not a stopwatch.
- The list shows the water reminder once, plus anything from A and B still pending. No duplicates.
Record: arrival times of both water reminders, and a screenshot of the list.
DChange, pause, resume, delete
4 min wait
Managing a rule by describing it, never by an ID.
Send, one at a time, waiting for each reply
make the water one every 4 minutes instead
pause the water reminder
turn the water reminder back on
actually delete the water reminder
Expect
- Each message gets a plain confirmation. Emma never asks you for a number or code to identify the reminder.
- While paused, no water reminder arrives. Wait through one full interval to check.
- After delete, the list from what reminders do i have no longer shows it, and no further water texts arrive.
- Fail if any water text arrives after the pause or after the delete.
Record: Emma's four replies, and whether anything arrived during the pause.
Bad input should get a question, not a broken reminder.
Send
remind me 10 minutes ago to call sarah
- Emma asks when you actually want it, or says she can't set one in the past. She does not claim it is set.
Record: her reply, word for word.
Part 2 · Notification rules
"Too many pings" is ambiguous. Emma must ask, not guess, and must not switch everything off.
Send
ugh too many pings from you today
- Emma asks one short question about what to cut, or offers two or three concrete options.
- Fail if she says she has turned notifications off, or says nothing useful.
Then answer
nah it's fine, keep them coming
- She acknowledges and changes nothing.
Record: the question she asked.
GExplicit rule, then a real email
up to 10 min
The rule is saved in the creator's own words, then applied to real inbound mail.
Send
don't tell me about inbound management deals, only brand deals
- Emma confirms she'll keep management pitches out of your notifications.
Then, from another mailbox, send two emails to the staging-connected Gmail, five minutes apart
Subject: Representation
Hi Jake, I'm Dana at Apex Talent Management. We work with creators in your space and would love to represent you. Are you open to a call this week?
Subject: Paid post, need a yes by tomorrow
Hi Jake, Priya from Nike here. We'd like to book one Instagram post from you next week, budget is 5,000 euro, but we need a yes by tomorrow morning. Can you confirm?
Expect
- No text about the Apex email. Wait 10 minutes to be sure.
- A text about the Nike email, within 10 minutes of it arriving.
- Fail if the management pitch produces a text, or the brand deal produces nothing.
Record: send time of each email, and whether a text arrived for each, with its time.
Part 3 · Email rules
HA rule that must block a send
Standing instructions apply at the last moment before an email leaves, even if you approve.
Send
from now on always check with me before emailing anyone at nike
draft an email to priya@nike.com saying yes to the post and asking for the brief
- Emma shows the draft as a preview with recipient, subject, and full body, and asks whether to send.
- Because your rule says "check with me", a fresh explicit yes counts as the check. She sends it and says so. Either that, or she asks one more time. Both pass.
- Fail if she sends without ever showing you the preview, or says it sent when it did not.
Then send
always sign my emails off with "cheers, jake" from now on
draft a quick email to dana@apextalent.com saying no thanks
- The preview ends with "cheers, jake". If it does not, she should say the sign-off rule needs a different draft rather than sending it anyway.
Record: screenshots of both previews and what she said after "yeah send it".
Part 4 · Scheduled work
IEmma does a job later, not just a nudge
3 min wait
A reminder repeats your words. Scheduled work makes her actually do something.
Send
in 3 minutes suggest 3 brands i should pitch this week
- Emma confirms it is scheduled, not done.
- About 3 minutes later a text arrives with three brand suggestions, drawn from real outreach data, not a copy of your request.
- Fail if the text just says "suggest 3 brands" back to you.
Record: the text she sent and the time.
JA recurring job set for later
Send
every weekday at 8am send me my outreach numbers
- Emma confirms weekdays at 8am, in your timezone.
- what reminders do i have shows it as a weekday 8am routine.
- Gone from the list. Do this so it does not fire tomorrow.
Record: the confirmation wording.
Part 5 · Voice and honesty
Across every scenario above, watch for internal language.
- Fail if Emma ever mentions a worker, a task, a tool, a session, an automation ID, or a "system notification".
- Fail if a reminder text arrives twice for the same moment.
- Fail if Emma says something is set or sent and it later turns out it was not.
Record: any message that looked machine-generated or exposed internals. Screenshot it.
Reporting
One message per scenario is enough. Use the letter, a pass or fail, the timestamps, and a screenshot where asked. If a scenario blocked you from continuing, say which one and carry on with the rest.
| Scenario | Result | Times | Notes |
|---|
| A · 2-minute reminder | | sent __:__:__ · quoted __:__ · arrived __:__:__ | |
| B · 6pm reminder | | quoted __:__ | |
| C · every 3 minutes | | 1st __:__:__ · 2nd __:__:__ | |
| D · change / pause / resume / delete | | anything during pause? __ | |
| E · nonsense timing | | | |
| F · vague complaint | | | |
| G · rule + real emails | | apex sent __:__ text? __ · nike sent __:__ text __:__ | |
| H · email rules | | | |
| I · scheduled job | | arrived __:__:__ | |
| J · weekday 8am | | | |
| K · nothing leaks | | | |
If something looks wrong, keep going and note it. Every step of this is logged on our side, so a timestamp is enough for us to find exactly what happened.