Set a support promise that fits a solo author business

A solo author's support promise should tell buyers where to ask, when to expect a first reply, what help is included, and what happens when an issue needs more investigation. Build that promise around the time you can consistently provide, then make it visible before purchase and easy to find afterward.

You do not need to imitate a staffed help desk. You do need a dependable way to handle the questions and problems created by the offer you sold.

For a paid companion to a nonfiction book, support might include finding the starting instructions, clarifying a step in the method, or reporting an output that contradicts those instructions. Personal coaching, reviewing a whole project, and providing professional advice are different services. A clear support page helps readers understand that distinction without having to negotiate it in every message.

Start with one primary support channel. It might be a dedicated email address or a form you actually check. Name it consistently in the offer, purchase materials, and help page. Test that a reader can find it and that messages reach the right place.

Avoid inviting support through every social account simply because readers already follow you there. If a question arrives elsewhere, direct the reader to the support route kindly. Do not make them reproduce a long history if you can move the relevant context yourself with appropriate care.

A service-business owner, u/laughterwithans, described “a hard stop rule with customer service that it starts and stops inside our working hours.” That is one owner's practice, not a universal schedule. The useful principle is making availability part of the service rather than letting each incoming message define it. Read the account.

“Within two business days” can mean very different things to an author and a reader. Does it promise an acknowledgment, a useful answer, or a completed fix?

Say which one you mean. A first reply might answer a simple question, request a missing detail, or explain the next investigation step. It should not imply that every issue can be resolved within the same interval.

Support tools make similar distinctions. Help Scout's documentation defines first response and resolution as separate targets, and permits measurement in calendar or office hours. Your business does not need that software to state the difference clearly. Help Scout's target definitions.

Also define business days and time zone. A reader should not have to infer whether a Sunday message starts the clock immediately or on Monday.

The following example is fictional. Elise is an author who teaches researchers to prepare clear interview guides. Her paid companion helps structure questions around a research purpose. It does not conduct interviews, obtain consent, assess research ethics, or replace specialist review.

The schedule and channel below illustrate a completed promise. Replace them with your actual arrangement before publishing; this is not Skillfully's support policy.

Help with the interview-guide companion

Where to ask: Use the support form linked in your purchase confirmation and on the companion's help page. I monitor that form for product questions. Social messages are not a support channel.

When I reply: My support days are Monday through Friday, 9am–5pm, America/Toronto time, excluding holidays listed on the help page. I aim to send a first human reply by the end of the second support day after your message arrives. A message received outside support hours is treated as arriving on the next support day.

What the first reply means: I will answer, ask for the information needed to investigate, or explain the next step. It is not a guarantee that the issue will be solved within two support days. If investigation continues, I will give you a date for the next update.

Included: Help locating the instructions, clarification of the documented method, and investigation of reported problems with the companion's promised task.

Not included: Personal review of complete research projects, live coaching, conducting interviews, ethical approval, legal advice, or support for unrelated software.

What to send: The step you were attempting, what you expected, what happened, and a short invented or redacted example if useful. Please do not send participant names, interview recordings, passwords, payment-card details, or confidential research material.

If access or billing is involved: Say which part failed and include the order reference where available. I will identify whether I can resolve it or direct you to the verified provider support route. I cannot promise another provider's response time.

If the reply date passes: Reply in the same conversation with “Follow-up” at the start of the subject. I review overdue conversations at the beginning of each support day. There is no separate emergency or after-hours service.

Planned absences: I will place changed support dates on this page and in the support acknowledgment. Existing open conversations will receive a specific update about their next response.

This template contains real obligations for its fictional author. The form, holiday list, acknowledgment, overdue review, and absence notice all have to exist if you use equivalent wording. Remove unsupported promises rather than leaving reassuring sentences that nobody can fulfill.

Suppose Elise reserves thirty minutes on each of five support days: 150 minutes per week. She allows thirty minutes of that total for reviewing open issues and updating help material, leaving 120 minutes for conversations.

If an average conversation requires fifteen minutes across all replies, that allowance covers eight conversations: 120 ÷ 15 = 8. It does not mean eight new messages every day, and it does not guarantee that every conversation takes fifteen minutes.

These are illustrative assumptions. A week with twelve such conversations requires 180 minutes, plus thirty minutes of review, for 210 minutes total. That is sixty minutes beyond the planned allowance. One complicated issue could create the same problem.

Track actual handling time and unresolved work for a few weeks. If the queue repeatedly exceeds capacity, improve confusing instructions, add qualified help, reduce the service scope prospectively, or limit new sales while you restore delivery. Quietly ignoring the excess does not make the support promise sustainable.

In a creator discussion, u/Ginnabean described keeping replies “short and focused on direct answers to questions” when conversations became overly chatty. Their broader approach includes delaying conversational replies; you need not adopt that tactic to use the distinction between product help and unlimited personal conversation. Read the comment.

A clear boundary can still be warm: “I can explain how the question-ordering step works. A review of your complete study is outside this product's support. For this step, could you share a short invented example of the question you're unsure about?”

If the reader reports an in-scope failure, do not hide behind exclusions. Investigate it. For an agent companion, test the reported task and record whether the instructions or behavior need correction. A boundary defines the service; it does not excuse failure to deliver that service.

More buyers, a new supported task, or a period of travel can change the work required. Review the support page before the mismatch becomes a backlog. Communicate changes clearly and account for promises already made to existing customers.

Keep a simple weekly note: new conversations, unresolved conversations, oldest unanswered request, actual time spent, and repeated sources of confusion. First-response speed alone is insufficient if readers keep returning because the answer did not help.

Draft your support promise and test its capacity with plausible numbers. When you are ready to discuss a paid application of your book's method, bring that promise and a sample reader task to Skillfully and choose Book onboarding.