A creator messaged on day nine asking where her sample was. It had shipped on day one, cleared customs on day five and been signed for on day eight — by someone else in her building. Nobody had told her any of it. From her side the parcel had been missing for over a week, and the video she was excited about on the day she applied had quietly become a favour she owed. Four sample notifications would have prevented all of it.
That is not a logistics failure. It is a sample notifications failure, and it costs more than a delayed post, because the doubt lands exactly when the creator’s enthusiasm is highest.
This is written for the small team sending twenty to sixty samples a month across ten to thirty creator accounts — US, Indonesia, Thailand, Vietnam — where one person owns the sample spreadsheet and also owns everything else. At that size nobody is going to remember to send four updates per parcel by hand, which is the whole argument for automating them.
Four moments worth a message, and the ones teams skip
Most sample communication happens at two points: the request and the chase. The four points that actually decide whether a video gets made sit between them.
Shipped sets the expectation. A creator who knows a parcel left the warehouse on Tuesday will wait until the following week without worry; a creator who was never told starts counting from the day she applied and assumes the worst by day seven.
Delivered closes the loop and starts the clock. It is also the point where a signature counts as receipt even when the parcel went to a neighbour, a front desk or a building manager — the single most common reason a creator says she never got it.
Due is the one almost nobody sends. A message two days before the agreed posting date, phrased as a reminder rather than a demand, recovers a meaningful share of creators who simply lost track. Without it, the only contact after delivery is the chase, which arrives late and reads as pressure.
Sold is the one teams leave out because it feels like bragging. It is the only message in the sequence that treats the creator as a partner rather than a supplier, and it is the reason the second sample gets accepted faster than the first.
| Moment | What the creator needs to hear | What silence costs |
|---|---|---|
| Shipped | It left, here is the rough arrival window | She starts counting from her application date |
| Delivered | It arrived, and here is who signed | Signature disputes after the shoot date passes |
| Due | Two days left, anything you need from us | The first contact after delivery is a chase |
| Sold | Your video did this number | The next sample request feels transactional |
Why the shipped message matters more than the delivered one
Delivered is the message teams remember to send, because it is the one that ends their admin. Shipped is the message that changes creator behaviour, because it moves the wait from open-ended to bounded.
A creator sitting on an unbounded wait does one of two things: she asks, which costs your team a reply, or she mentally deprioritises the product, which costs you the video. Both outcomes are avoided by a single line on day one. The arithmetic is not close — one automated message against a queue of status questions that all arrive in a different time zone. Sending that one message unprompted is the entire job of sample notifications.
There is a second effect that only shows up over months. Creators talk to each other, and in most categories the ones working with the same shops know each other. A shop whose parcels arrive with no updates gets a reputation for slow, even when the parcels are fast. The updates are the evidence.
What automation actually changes, and what it does not
Setting the four moments to fire on their own removes the memory problem, which is the reason most of these messages never get sent. It does not remove the judgement, and there are two places where judgement still belongs to a person.
The first is tone at the due point. A reminder that reads like a deadline gets a defensive reply; the same reminder phrased as availability gets a “shooting tomorrow”. Templated wording is fine as long as it is written once by someone who has read a creator’s reply before, not generated fresh each time.
The second is what happens after the due point passes. No notification rescues a creator who has decided not to post, and pretending otherwise wastes weeks. That case needs a human deciding whether to re-brief, replace or release.
DAMI’s push events cover shipped, delivered, fulfilment and order, and fire on their own against the creator in the sample workspace, so the four messages arrive whether or not anyone remembered to send them. In practice the change is not that creators get more messages; it is that the status questions stop arriving at 9am in a batch.
Where this stops being worth it
Below roughly fifteen samples a month, a person with a calendar reminder can hold four moments per parcel, and automation buys you nothing but a setup afternoon. DAMI does not change that arithmetic; it only removes the remembering. The break-even is not about volume alone; it is about whether the same person also answers the follow-up questions. Once the status questions and the chase both land on one desk, the notifications pay for themselves in recovered mornings.
FAQ
Won’t four automated messages feel like spam to a creator?
Four messages across three weeks is less contact than the average chase sequence, and each one carries new information. The version creators dislike is a chain of “just checking in” messages that repeat the same question.
What if the creator never received the parcel but the tracking says delivered?
That is the delivery dispute, and it is worth a template of its own: ask for a photo of the doorstep, offer to reship once, and record the outcome against the creator. DAMI keeps that outcome on the creator record, so the same address does not produce the same dispute twice. Without a record, the same address produces the same dispute twice.
Should the sold notification go out on every video?
Only on the ones that beat the creator’s own average. A sold message on a weak video reads as flattery and cheapens the ones that matter. One honest number at the right moment is worth more than a monthly summary nobody opens.
Take the last twenty samples you shipped and count how many of the four moments got a message. Most teams find the shipped step is the gap, and it is the one worth fixing first. Getting the plan into the creator’s chat covers the message that precedes all of this, and building a habit around replies that arrive at 2am covers the other side of the same time-zone problem. The DAMI sample workspace is where the parcel, the creator and the four sample notifications sit together, or you can create an account and wire the first sequence up this week.
