Turn Your Busy-Season Phone Questions Into a Quarter of Posts

The same seven questions, over and over

Sit in a Lima accounting office in the middle of a filing crunch and listen to the phone. The calls that break your concentration are almost never complicated. Do you handle Ohio municipal returns? What should I bring to a first appointment? Do you do bookkeeping, or only taxes? Roughly what does a small business return cost? Each one is a two-minute answer you have given four hundred times. Each one also costs you the thread of the return on your screen.

Here is the part worth noticing: those are not interruptions. They are prospects deciding whether to hire you, and they are the exact content your social accounts should be publishing.

That is the use case. Not "post more." Build one content engine out of the questions you already answer.

• Spend an hour listing the questions you actually get — front desk notes, voicemail, email.
• Answer each one out loud into your phone's recorder, three sentences, the way you'd say it to someone standing in your lobby. Don't write it. Talk it.
• Those recordings become your voice sample. A generation pipeline drafts a quarter's worth of posts from them, in your phrasing rather than a chatbot's.
• A calendar maps them onto your real year: extension season, third-quarter estimates, year-end planning, W-2 and 1099 season.
• You review once a week, in one batch. Fifteen minutes to approve, kill, or fix.

The approval gate is the whole product

The Journal of Accountancy ran guidance this month on writing an AI policy that actually holds up, and it maps cleanly onto a social pipeline: keep a maintained list of approved tools, require human review before anything AI-produced goes out, and document who did the reviewing. The same article notes that only 16% of firms in a 2025 PCPS survey felt very confident about adapting to AI. That gap is mostly missing process, not missing technology.

For an Ohio licensee there's a second reason to build that gate in. Your posts are advertising. Ohio Administrative Code 4701-11-09 treats promoting your services in a misleading way as a discreditable act, and names two failure modes that AI writing hits easily: misrepresenting facts, and creating a false or unjustified expectation of favorable results. A drafter that cheerfully offers to "maximize your refund," or invents a phase-out threshold, isn't a typo. It's licensing exposure.

So the spec sets limits before the first post is ever generated. AI writes about what you do, who you serve, and how you work. It never asserts a tax outcome, a dollar figure, or a code section you haven't verified against primary guidance — the same standard you already apply to client work. One more line worth having: if you ever put a fully AI-generated person in a paid ad, say so. New York's synthetic performer disclosure law, the first in the country, took effect June 9, 2026. Ohio hasn't followed, but for a firm that competes on being local and known, your own face was always the better bet.

What you actually get out of it

Three deliverables, and they're deliberately unglamorous: a social automation spec (voice rules, approved topics, hard prohibitions, named approver), a content calendar built around your filing season instead of a generic marketing year, and a generation pipeline that drafts, queues, and publishes after your sign-off.

Be honest about the payoff. This won't flood you with leads. It moves two specific numbers. A prospect who has read three of your posts before calling doesn't need the ten-minute qualifying conversation — they call to book. And when Friday's scheduled post spells out which documents you need for extended returns and when they're due, some share of your clients send them in without being chased individually. Not all of them. Enough to feel in September.

The mistake is starting with the tool. Start with the questions — you've been answering them by phone all year, and they're already in your voice.