It's Thursday Night and Your Phone Won't Stop

You launched three months ago. Things are going well (sort of). Customers are signing up. Customers are also messaging you at 11 PM asking why their login doesn't work.

You're the CEO, the developer, the marketer, and the entire support department. You have maybe 1-2 hours a day for support before it starts eating into the time you need for everything else.

This playbook is for you.

Time Budget

Be honest about how much time you can spend. If support takes more than 2 hours a day, it's cannibalizing product development, sales, and your sanity. The goal is to get that number under 1 hour while still giving customers good experiences.

Track your support time for one week. Count every minute spent reading messages, writing responses, looking up information, and thinking about customer issues. Most founders underestimate by 50%. "I spend maybe 30 minutes a day" is usually an hour.

Triage: Not Everything Needs Your Attention Right Now

Set up a priority system. Not all messages are equal.

Urgent: Customer can't access the product, payment failed, data loss, or anything that blocks them from working. Respond within 1 hour during business hours.

High: Billing questions, order issues, bugs that affect the customer's workflow but don't block them completely. Respond within 2-4 hours.

Normal: Feature questions, how-to questions, non-blocking bugs. Respond within 4-8 hours.

Batch: Feature requests, general feedback, partnership inquiries. Respond once daily in a batch.

Most founders treat every message as urgent, which means they're constantly context-switching. A "how do I export my data?" question at 10 AM doesn't need an immediate response. It can wait until your daily support block.

The Daily Support Block

Pick a time. 9-10 AM works for many founders. Check your inbox, respond to overnight messages, handle the batch. Then close the inbox and work on other things until your next check (maybe 3-4 PM).

The worst pattern: checking messages every 15 minutes throughout the day. You never get deep work done and you never clear the inbox. It's the worst of both worlds.

Two focused blocks per day (morning and afternoon, 30-45 minutes each) beats twelve quick checks that fragment your entire day.

What to Automate First

Order status and tracking. If you sell physical products, this alone cuts 25-30% of your volume.

Password resets and login issues. Automated password reset emails handle 90% of access problems. The remaining 10% need a manual look.

Business hours, pricing, and basic FAQ. Set up auto-responses for the five questions you answer most often. Most AI support tools can handle this with 15 minutes of setup.

Return and refund eligibility checks. Customers asking "can I return this?" just need your policy applied to their order date. Straightforward to automate.

At $0.20-0.30 per AI-handled message (Supp's pricing), automating 100 messages/month costs $20-30. That buys back 5-10 hours of your time.

When to Hire Your First Support Person

Track two numbers: messages per day and time per message.

If you're getting 20+ messages/day and your average response takes 5+ minutes, you're spending nearly 2 hours daily on support. That's enough to justify a part-time person.

Your first support hire should be a part-time contractor or virtual assistant (VA), not a full-time employee. Start at 10-20 hours/week. Give them a simple decision framework: handle X types of messages directly, escalate Y types to you.

Good places to find support VAs: Belay, Time Etc, or a support-specific contractor from a customer service freelancer platform. Budget $15-25/hour depending on the skill level needed.

Templates Save Sanity

Write templates for your top 10 message types. Not corporate-sounding templates. Your-voice templates. Read them aloud. If they sound like you talking to a friend (a friend you're being professional with), they're good.

Update templates monthly. Your product changes, your answers change. Stale templates create stale experiences.

The Emotional Toll

Nobody talks about this part. Being the solo support person means you personally absorb every customer frustration. Every "this is broken" and "I'm canceling" and "your product sucks" lands on you, the person who built the thing.

Set boundaries. Don't check support messages before bed. Don't respond to non-urgent messages on weekends (set auto-responders for weekends). If a message makes you angry, wait 10 minutes before responding.

It gets better. As your product matures, support volume shifts from "this is broken" to "how do I do X?" The emotional weight decreases. And once you automate the repetitive stuff and hire your first support person, you get your evenings back.