State what you provide, what is separate, and what you do not offer. Use plain language and apply the same boundaries consistently.
Make boundaries specific
“Please be respectful” is reasonable but incomplete. Explain the practical limits: whether you accept requests, when you usually handle messages, and whether any services are outside the subscription. You do not need to publish private reasons for every limit.
Keep the wording close to the relevant decision. A subscriber should be able to understand the scope before paying for a service, not discover it deep in an unrelated post.
Write the difficult sentence in advance
Prepare a few short responses for common situations. “That is not something I offer.” “The subscription covers the feed; this request is separate.” “I cannot commit to that deadline.” These are original examples, not scripts that require an explanation or apology.
Do not add a long justification unless it helps resolve a genuine misunderstanding. A complicated explanation can accidentally make a firm boundary sound like an opening for negotiation.
Protect the working arrangement
When someone continues after a clear refusal, use the moderation and support options available on the platform. Keep relevant records and avoid escalating a dispute in public. You can be courteous without continuing a conversation indefinitely.
Review your own promotional language as well. If the bio implies unlimited access while your working practice is limited, the problem is partly in the offer. Align the description, welcome message, and actual service so that fewer people have to guess.
Put it into practice
- State scope before purchase.
- Prepare short, clear responses.
- Align promotion with actual availability.
A practical guide, not official platform policy. Confirm current account settings, offers, and requirements directly with the service. Read our editorial approach.