A safety-first guide to how Humanly Held should explain a no without shaming the person, weakening the category, or suggesting an unsafe request might pass later.
Answer first
Humanly Held should explain a denied request by naming the boundary directly, avoiding negotiation or shame, and closing the loop without coaching the request into something that still does not fit the category.
2026-06-14 · 4 min read
Audience: Operators, cautious adults, companions, and reviewers who want denial language to stay clear, calm, and boundaried.
This guide describes the intended operator standard. It does not claim a live support team, a universal referral network, or already-approved moderation capacity at scale.
Operators who need a repeatable way to say no without creating confusion.
Companions who do not want emotional cleanup or pressure pushed onto them after a denial.
Cautious adults who trust a service more when its no is clear and respectful.
Reviewers checking whether the product protects the category even when demand does not fit.
Not a fit
Denial messages that sound apologetic enough to reopen an unsafe request.
Language that shames the person instead of naming the category boundary.
Responses that invite private-home, off-platform, romantic, sexual, clinical, or crisis-adjacent workarounds.
Workflows where the companion has to manage the refusal alone.
What should a denial explanation do first?
It should make the boundary legible. A denial is not only about ending the request; it is also about protecting the category from being stretched by ambiguity, urgency, or politeness.
The strongest first sentence is usually the simplest one: the request does not fit Humanly Held's adult-only, fully clothed, platonic, trusted-space scope.
What should the message include?
A useful denial should name the relevant boundary, keep the tone calm, and make clear that the no is based on fit, not punishment. It should not over-explain or create false hope.
If clarification was already attempted, the explanation can briefly say that the request still does not fit the service after review.
What should the message avoid?
It should avoid flirting with a maybe, avoid offering off-platform alternatives, and avoid language that teaches someone how to rewrite the request just enough to sneak through later.
Humanly Held should not soften sexual, romantic, clinical, crisis, or private-home intent into something that sounds reviewable when it is not.
When can it point someone elsewhere?
If the request clearly belongs to a different category, Humanly Held can say that the service is not equipped for that need and that the person may need a different kind of support or regulated service.
The company should not pretend to be a triage desk or make professional recommendations it cannot safely own. The goal is honest scope, not improvised redirection.