You sent the sample. Where is the video?
Every seeding programme reaches the point where nobody can say which creators still owe you something, so the ones worth chasing get chased last. This is one queue that answers it: delivered past the window, still silent, biggest seller first. Take the source, give the prompt below to your agent, and you have your own running today, populated with invented creators until you say go.
- USPSUPSEvri
01
A sample goes out
Product, value, carrier and tracking against one creator. The cost of the programme, itemised.
- deliveredday 7: overdue
02
Delivery starts the clock
Not dispatch. The posting window runs from the day it landed, because that is what you agreed.
- $86.4K$72.1K$19.8K
03
The queue ranks by size
Overdue and silent, biggest seller first. A 33-day silence from an $86K creator is not a $5K problem.
- draftdraftdraft
04
Chases you read first
Tick rows, pick an escalation, and each message renders against that creator's own product and dates.
- First check-in→Second check-in→Final notice
the log picks the next template
- publication
- 15%
- reply rate
- 33%
05
The log has a memory
Marking a row replied is what moves the next message on, and what the publication and reply rates are drawn from.
On demo data
Every screen below is the App as it arrives, before anyone has typed anything into it. The creators, agencies and products are invented, the addresses sit on a reserved.exampledomain, and the video links resolve to nothing.




Run your own
Give this to your agent
Download the source first, then send this with the zip attached. It builds the App, leaves the demo rows in, and stops before anything costs you.
Build me a TikTok Shop sampling desk from the sampling-desk-app-template.zip I am attaching. Unpack it, read README.md and setup/01-build-the-app.md, and follow them: create the App, provision its database, copy app/. into the checkout, replace the placeholder app id and hosting slug, then push a draft and send me the link. Never run SQL by hand - db/migrations applies itself, and the last file seeds 14 invented creators and 24 samples so the work queue has a real backlog on the first open. Leave those rows in. Then stop. Do not import anything real, do not create the workflows, and do not set CHASE_WEBHOOK_URL. Ask me whether to start loading our own creators and samples.
What is in the zip
- app/
- The complete Next.js source, with db/migrations. Copy it into a Kylon App checkout.
- setup/
- Five short docs: the build, the draft-card button, where creator numbers come from, loading your own data, and a room guideline.
- workflows/
- Three automation briefs, each with an honest note on what it costs to run.