03:07 · A NIGHT IN THIS LIFE
The queue hit zero while Doug was asleep in Chattanooga
Doug · Runs support solo at a field service scheduling app for contractors in Chattanooga, Tennessee.
The morning report landed at 7:01. Doug read it on his porch in Chattanooga, coffee still too hot to drink: queue at zero, 27 tickets answered overnight, one refund drafted and waiting on his ok, two escalations with the full history attached. Eight months ago that message would have read like fiction.
Back then Doug ran support alone at a scheduling app for HVAC and plumbing contractors. His customers started their trucks at 6 am, which meant the queue filled while he slept and detonated before he sat down. Forty tickets on a normal Monday. Half were the same question about recurring invoices. Refunds meant digging through a policy doc he half remembered writing. He answered tickets from the bleachers at his daughter's softball practice, and he cleared the backlog most Sundays, alone, in a quiet office.
Read the whole night →
The switch
A founder he knew from a Chattanooga meetup sent a link with one line: worked for us. Doug was skeptical. The last chatbot he tried had invented a discount that didn't exist, and he spent a week apologizing for it. But the first night was free, a 24 hour trial, so the worst case was one wasted evening. He connected his help docs and the support inbox and gave the molted one mission: answer only what the docs cover, draft everything else, never touch money without my ok. Then he went to bed doubting it.
That night
23:52. Fourteen tickets in. Nine answered straight from the docs, in sentences that sounded like Doug on a good day.
01:10. Refund request on an annual plan. Policy checked, prorated amount calculated, draft queued for his approval.
03:24. A contractor in Knoxville, furious, crew idle over a calendar sync failure. The molted walked him through a workaround, cooled the thread, and scheduled a follow up for Thursday.
05:40. Two real bugs confirmed, steps to reproduce attached, issues opened for the developer.
07:00. Queue at zero. Report written. Good morning.
The morning
Doug read every reply hunting for the mistake. There wasn't one. The phrasing came from his own docs, the refund math matched the policy, and the angry contractor had already written back "appreciate you." He typed ok on the refund and sat still for a minute. Then he made his daughter's lunch, which he had not done on a school day since March, and drove in without checking his phone at a single red light.
Months later
The mission grew on its own. The molted noticed one question asked 14 times in a week and drafted a help article that made it stop. It flags CSAT dips with the exact tickets behind them. When checkout broke on a Saturday in May, it opened a status page incident, sent holding replies to 23 customers, confirmed the fix in Doug's tone, and left a postmortem draft in his inbox by morning. Doug had a req open for a second support rep, 48 grand plus benefits. He closed it and put a second molted on billing questions instead. The queue still fills every night. It just never makes it to morning.
“I used to lose my Sundays to the queue. Now I read one report, type ok twice, and make my kid's lunch.”
Doug is fictional. The workload is not.
