Home / Work / SMS drafting desk

An SMS drafting desk for a jewelry brand

The brand's SMS copy arrives overnight. By the time the team is awake, each message is already built in Attentive as a draft, waiting for a person to check and schedule it.

ClientA jewelry brand, name withheld
WhenJuly 2026 to now
My partDesign and build of the system
PlatformAttentive, Playwright, Claude

The problem

The brand's copywriter posts SMS copy at about four in the morning, Manila time. The team that builds the messages is asleep. They used to wake up, wait for the copy, then build each message by hand in Attentive.

Copy once came weekly. It became daily, and one sample week had 20 messages.

How it works

1

Watch

A watcher checks for new copy every five minutes, read-only.

2

Join

The copy doc gives the words. The planning sheet gives times, audiences and links, and wins any disagreement.

3

Build

Shorthand becomes exact segment names. Late sends get the quiet-hours exclusion. The link goes in once, tracked.

4

Draft

Attentive has no API for creating drafts, so a browser fills the composer, one container per send date.

5

Read back

Every saved message is checked against a fixed list, then it stops at "save and close".

What it will not do

  • Schedule or send. The brand's team does that.
  • Touch a draft a person has edited. Edited fields are read-only to it.
  • Guess. A missing link, an unknown segment or unfinished copy is a hold, with the gap flagged.
  • Repair blind. Fixes check the message's status first and stop if it is scheduled or sent. Audience fixes only add, and run dry before they apply.
  • Work over a teammate. If a person claims the day, it pauses.

The record so far

93send days drafted since 20 July 2026
20 / 20messages parsed in the first test week
24hand repairs logged, 1 Oct to 18 Nov

The third number is here on purpose. The desk does not run clean every day. Most repairs were audience matching: the platform holds 947 saved segments, and a planning-sheet shorthand does not always point to exactly one. Others were a login that expires after about twelve hours, a link missing its scheme, and a message name that did not save.

Each repair is logged and turned into a rule or a check. The first fully unattended multi-day run was on 4 September 2026, with 11 messages.

Next: a website for a session singer

Read it →