A welcome list,
ready for your review.
See how a repeat job becomes a reusable AI employee: give it a subscriber snapshot and welcome history; get a checked list of who needs your attention.
Fictional example · No messages sentWho still needs a welcome?
Each time new people subscribe, someone needs to compare the subscriber list with prior welcomes, check the times, and prepare the next messages.
Give it the source.
This sample includes 10 made-up people, when they subscribed, known welcome status, and the first outgoing-message time for those already welcomed.
Snapshot: September 24, 2026, 4:00 p.m. Pacific. The sample marks both the roster and message evidence complete.
Give it your wording.
The AI employee keeps the supplied welcome message intact. Natalee’s included message is a teaching example; your own AI employee needs wording you approve.
Missing welcome status needs evidence. A blank field alone does not prove a message was never sent.
Inspect the exact fictional inputs
All times below are Pacific, in 2026. “Not sent” is an explicit sample status.
| Subscriber | Subscribed | First outgoing welcome |
|---|---|---|
| Mara Bellweather | 09-24 06:00 | Not sent |
| Ellis Northwood | 09-24 10:00 | Not sent |
| Cleo Hartwell | 09-24 14:00 | Not sent |
| Tessa Meadowbrook | 09-22 16:00 | Not sent |
| Nolan Ashford | 09-23 10:00 | Not sent |
| Rowan Finch | 09-24 08:00 | 09-24 10:00 |
| Avery Hollis | 09-23 14:00 | 09-24 08:00 |
| Quinn Marlow | 09-22 09:00 | 09-23 15:00 |
| Theo Linden | 09-22 11:00 | 09-22 15:00 |
| Iris Vale | 09-20 10:00 | 09-21 16:00 |
A short list you can act on.
The result separates five people waiting from five already welcomed. It puts the three still inside 24 hours first, then the remaining two in oldest-first order.
- Source match checked. Names, times, counts, ordering, and welcome wording match the sample.
- Timing checked. Three of the five completed sample welcomes arrived within 24 hours: 60%. This is a fictional calculation.
- Missing evidence tested. Unknown status, incomplete sources, and inconsistent message times are rejected.
Read the exact supplied welcome message
You review. You send.
Review the person and message before sending. With your own verified sources, the AI employee can prepare the working list; you handle the conversation.
What you can try here
Open the working example and copy the sample welcome. Its profile button explains that fictional people have no live profiles to open.
What confirms a welcome
A fresh, verified outgoing-message time. Opening a profile or copying text does not move anyone into the welcome log.
Keep the job, the steps, and the checks.
The included Welcome AI employee keeps its purpose, example, process, context, quality checks, and work record together. Next time, open the AI employee’s folder in Codex or Claude Code and type Start.
For your own first AI employee, the Chief of Staff starts with a repeated task and a real sample, shows you a result to review, then builds and checks the reusable AI employee after you accept the example.
This portable edition works from supplied local data. Live Substack access and automatic sending are not part of this example.
Start with one useful job.
This walkthrough shows one bundled example. It demonstrates the local Welcome workflow and its checks. It does not measure a buyer’s results or show a completed setup-training course.
Explore the AI Chief of Staff Kit