Community Help – Standard Escalation Language Library
This document defines the approved escalation language that may be used across all BUSATX Community Help content.
Its purpose is to maintain consistent tone and positioning, avoid sales language or calls to action, protect legal, architectural, and commercial boundaries, and clearly signal when professional assistance may be appropriate.
All Community Help articles must use only the language patterns defined below.
1. Escalation Philosophy
Community Help exists to educate, not to sell.
Escalation language should:
- Be factual and neutral
- Reference complexity, not capability
- Avoid urgency or pressure
- Never imply obligation
The reader should feel informed — not marketed to.
2. Approved Escalation Section Title
Every article that includes escalation language must use exactly one of the following titles:
- When to Consider Professional Assistance
- When Professional Assistance May Be Required
No other escalation headers are permitted.
3. Approved Escalation Language Blocks
Only the following escalation statements are approved for use. Content authors may select the most appropriate block but may not alter wording.
Block A — General Complexity
For more advanced use cases, professional configuration or development may be required.
Block B — Scale or Growth
Organizations with more complex requirements or growing operational scale often engage professional support to ensure systems remain stable and maintainable.
Block C — Cross-Module or Automation
Workflows that span multiple modules or rely on automation typically require professional configuration or development.
Block D — Performance or Stability
Performance, scalability, or reliability concerns are often best addressed through structured professional review.
Block E — Security or Governance
Environments involving sensitive data, multi-company operations, or audit requirements often require professional security and governance design.
4. Prohibited Escalation Language
The following are not allowed in Community Help content:
- Calls to action (e.g., Contact us, Schedule a call)
- Promotional phrasing (e.g., Best in class, Industry leading)
- Urgency language (e.g., Critical, Immediately, Don’t risk)
- Pricing or service references
- Named packages or offerings
If escalation language sounds like marketing, it must be removed.
5. Placement Rules
- Escalation language must appear only once per article
- It must appear at the end of the article
- It must not be embedded mid-paragraph or inline
This ensures escalation is informative, not disruptive.
6. Consistency Enforcement
All Community Help content must be reviewed for:
- Correct escalation header usage
- Approved language block usage
- Proper placement
Articles that deviate must be revised before publishing.
7. Authority
This escalation language library is authoritative.
No alternative wording, paraphrasing, or additions are permitted without explicit approval.
End of Community Help – Standard Escalation Language Library
<p>Related: <a href="/forum/community-help-3/community-help-154">Community Help</a>, <a href="/forum/community-help-3/community-help-publishing-contribution-rules-155">Community Help – Publishing & Contribution Rules</a>.</p>