Build the help center first
Every repeated question becomes a Notion help page. Link it from onboarding. If you answer the same thing three times, you failed to document it.
Use Grammarly to keep support tone calm. Angry customers escalate when you mirror chaos.
Assistants with boundaries
Lindy or similar agents can draft replies and book calls. They should not invent refunds or policies. Keep a human approval step for money and access.
Macros are fine. Pretending to be personal while pasting the wrong name is not. Merge fields are a loaded weapon.
Office hours beat endless chat
Offer a weekly office hour for paying users. Batching support protects deep work. Infinity chat is how founders vanish from the roadmap.
Running tip: tag tickets by theme monthly. The top tag is your next product fix or your next article.
Field notes
Field note: great support is product marketing in disguise. Every calm, clear reply teaches the customer how to talk about you. Every chaotic reply teaches them to warn a group chat.
When you do not know the answer, say so and give a time you will return. Silence is louder than honesty.
Operator checklist
Operator checklist: publish a small help center covering setup, billing, and the top three how-tos. Link it in onboarding.
Create macros for common replies and a rule that money decisions need a human. Draft with tools; decide with judgment.
Hold one office hour or batch window. Protect deep work from infinite chat, or the roadmap dies politely.
How to run it this week
Publish response-time expectations. "Within one business day" beats silent anxiety.
Escalate product bugs to a public status note when relevant. Hidden outages breed conspiracy theories.
Fire customers who abuse support. Not every revenue dollar is cheap.
What good looks like
What good looks like: a help center, macros with boundaries, and a batched support window. Speed without drowning is the goal.
Common failure mode: infinite chat that eats the roadmap. Support should inform the product, not replace it.
Series bridge
Series bridge: this chapter sits between growing the list and measuring what matters. If you skipped here, go back one part and finish the checklist first. The playbook only compounds when each layer is real — research under offer, offer under site, site under product, product under distribution.
Keep a single Notion page titled Kingdom OS and paste the outcome of this part at the bottom before you leave. Date it. Future you will skim twenty dated notes faster than twenty open browser tabs. That page becomes the operating system the last chapter asks you to run daily.