James La (@jamesla) header
James La (@jamesla) profile picture

Founder, Q Digital Media — I build AI systems that answer your customers when you can't | 25 yrs enterprise sales · 2 exits | Montreal

Canada
Joined February 2009
Week 3 — Day 19 of building YouTube channels to monetization with AI: 6 new faith channels branded, Spanish channel launched (Ep 1 live), 13-episode sleep library built. Scoreboard: 10 channels · 60 episodes · 1,409 views · 30.6h watch What would you test next?
8
The attachment is often the actual request. A message that says 'can you help with this?' with a photo of the damage underneath isn't missing a description — the photo is the description. My workflow reads the file first now, and says out loud what it can't read, early.
11
Every approved answer in my system now has an expiry date. One was perfect when I wrote it — right price, right policy — and eight months later it was still drafting, word for word, and wrong. Nothing broke. It expired. Free mini-audit: forms.gle/WDjU52gv5BVgYefLA
18
A customer got the same reminder twice, eleven minutes apart. Nothing was wrong with either message — they made the business look careless. The fix wasn't smarter. It was a receipt: one job ID, checked before sending, written the moment a send happens. No receipt, no retry.
25
1/ A long thread doesn't need a longer reply. It needs a memory. The thread was fourteen messages long — dates changed twice, a price answered in message three and asked again in message eleven, one key detail buried in the middle.
1
26
2/ The draft answered the first version of the request, not the current one. So threads past a few exchanges get a memory first: what was asked, what was agreed, what changed, what's still open.
1
19
3/ The draft is then written against that memory, not the raw pile. Most 'the AI forgot what we discussed' problems aren't model problems. There was simply no step in the workflow whose job was remembering.
10
My automations have a bedtime. A reminder once went out at 11:40 PM — perfect wording, wrong hour. Routine sends now queue until business hours. Drafting never sleeps. Sending does. Fast is not the same as respectful, and a system doesn't know that unless you build it in.
14
Sent is not the same as done. A confirmation in a spam folder isn't a confirmation. A reminder nobody replied to didn't work. My systems now keep a job open until the other side proves it landed — a reply, a tap, a confirmed booking. Sending is step one, not the finish line.
1
19
1/ One customer contacted a business three times in four hours this week: a form in the morning, a DM at lunch, an email that evening asking if the first two arrived. Each door worked. Each started a separate thread.
1
27
2/ The hard job isn't answering a message. It's recognising three messages are one conversation. My system checks new inquiries against the open list first — and flags likely matches for a human to confirm, never merges them automatically.
1
17
3/ Once confirmed: one thread, one owner, one next step. Most 'impatient customer' problems are really 'we never told them we heard them' problems, multiplied by every extra door the business added.
7
I stopped returning calls cold. Before any callback, a short packet pulls the thread together: what they asked, what we replied, what's still open. The call is still mine. What changed is the first minute — I open with their situation, not my reconstruction of it.
17
When someone corrects a draft, that correction is the build. For years I used the edit once and threw it away. Now it goes back into the approved answers or the examples — so one corrected sentence helps every draft after it, not just that one send.
9
1/ The first message a customer sends is rarely the real request. It's the careful version — short, polite, missing the deadline, the budget, or the mess the last person left. The real detail usually arrives second.
1
27
2/ So my first reply isn't built to close anything. It's built to earn that second message: one real answer, one easy question, nothing that feels like an interrogation.
1
25
3/ And when the second message lands, it jumps the queue. That's the start of the real job — not a follow-up to handle in order. Judge a first reply by whether it earns the honest second one.
14
Before I automate a message, it has to pass three questions: does it really repeat, is there an approved answer, and what happens when it's wrong? If a wrong send costs money or trust, the system routes it to a human. Free mini-audit: forms.gle/WDjU52gv5BVgYefLA
11
I deleted an automation last week — not paused, deleted — and the work got faster the same day. It copied every inquiry into three places and sent notifications I never opened. Every system charges rent. If turning it off breaks nothing, it wasn't helping.
1
21
I stopped counting replies and started counting resolutions. A fast reply that doesn't finish the customer's job just starts a longer thread. A thread counts when the booking is confirmed, the question is answered, or it's handed to a human with full history.
21