The TWIMCO notebook
Field notes.
Useful observations from inside the work.
For people building a better way.
385 notes

If the agent wrote it, put a ticket id on the write
The CRM row changed at 1:12 a.m. The agent log says it meant to help. Support cannot find which conversation authorized the edit.
Read the note ↗︎
You rotated the webhook secret while events were still in flight
Security asked for a new signing secret by Friday. You flipped it at noon. The retries from 11:50 still signed with the old one. By evening the dead letter looked like an outage.
Read the note ↗︎
A shared inbox without a route is just a pile
Everyone can see the mailbox. Nobody owns the thread that came in at 4:55. By morning three people replied and two customers got different answers.
Read the note ↗︎
When Google's AI points to the official page, is it yours?
Google is testing a spot at the top of its AI answers for the one or two official places to get something done. If someone asks how to renew a permit or start a return, would your page be the obvious pick, or one of three?
Read the note ↗︎
They denied push. You still owe them a path
The permission prompt came too early. They tapped Don't Allow. Now every feature that mattered was hiding behind a bell they will never see.
Read the note ↗︎
Validate the public form before the clerk inherits the mess
The resident hit submit. Required fields were empty in the payload. The portal showed a green check. Three days later a clerk is calling about a blank address line.
Read the note ↗︎
Sellers need an evidence pack before the dispute clock runs out
The marketplace opened a case at 9 a.m. Tracking says delivered. The buyer says empty box. Your seller has screenshots in three chats and nothing the portal will accept.
Read the note ↗︎
The carrier cutoff beat the promise date you printed
Checkout said arrives Thursday. The carrier's last pickup was 3 p.m. and the wave finished at 3:40. The box was on time for your system and late for the truck.
Read the note ↗︎
The packing slip SKU is not the label SKU
The slip says blue mug. The label says blue mug. The tote has the black one. Three systems agreed on a string and still packed the wrong unit.
Read the note ↗︎
Tranthor review: retention that starts from the customer moment
Tranthor launched October 11, 2026 as an autonomous CRM for ecommerce retention. It finds the repeat-purchase moment, drafts the play, and sends only inside limits you approve. Here is the buying read.
Read the review ↗︎
Attio hybrid CRM review: SQL for agents, humans still own the deal
Attio's October 2026 launch puts SQL, live Postgres connectors, and agent-scale records into the CRM. Worth a look if your revenue team already runs agents—and you can name who approves writes.
Read the review ↗︎
Your agent checkout works. Your shipping answer doesn't.
Shopify switched the agent tools on for you, and most readiness checkers will call your store ready. Ask it what shipping to Boston costs, or whether an order can be canceled tomorrow, and the answer usually comes back empty.
Read the note ↗︎
The inventory hold expired while they were still checking out
They had the item. Payment was open. The hold timer died first. Another buyer took the unit, and checkout discovered sold out after payment authorization had already started—a race you can rehearse before the next drop.
Read the note ↗︎
An exception queue without an owner is just a parking lot
The bot did its job: it parked what it could not finish. Without a named human, a first-touch clock, and authority to act, that queue is storage—not operations.
Read the note ↗︎
A deep link that dumps a logged-in user at login is broken
They were already signed in. The email link opened your app and dropped them on the login screen anyway. That is not caution—it is a broken handoff between intent and session.
Read the note ↗︎
When the vendor kills the feature, can you leave with your data
Sunset emails arrive politely. The workflow you built on that feature does not. Before you accept the migration webinar, ask whether you can export what you need—and whether leave is still possible if the replacement is wrong.
Read the note ↗︎
The quote expired in the system and is still open in email
ERP says the wholesale quote died Tuesday. The buyer still has Thursday's PDF in their inbox and a sales rep who does not want to be the bad news. Until expiry is visible in every place the price was promised, you will keep honoring ghosts.
Read the note ↗︎
Say we received it before the SLA clock starts
Applicants refresh the portal wondering if the packet landed. Staff start the clock when someone finally opens the queue. If acknowledgment and SLA start are the same silent event, you will keep losing arguments about days elapsed.
Read the note ↗︎
Let the agent propose the catalog change before it writes live
Merchandising agents that can pin, boost, and rewrite collection rules are showing up in demos everywhere. The useful pattern is not clever chat—it is a dry run the merchandiser can reject before anything customer-facing moves.
Read the note ↗︎
The return reason CS typed is not what the bench opens
Customer service picks Damaged from a dropdown. The warehouse opens a sealed carton and finds the wrong size. Until the reason the bench sees matches the reason the customer said, every RMA is a small argument waiting to happen.
Read the note ↗︎A familiar problem? Let’s look closer.
Tell us where you want to go. We’ll find the first thing worth changing.
Tell us about it ↗︎