# zAgile Brand Voice

> Professional, utility-driven, and focused on the seamless movement of data between teams.

## Positioning
zAgile provides integration and collaboration software for businesses using Salesforce, Jira, Slack, and Confluence. It is designed for support, engineering, and marketing teams who need to eliminate silos and improve cross-functional productivity.

## Voice principles
*   **Functional:** Focuses on the "how" and "what" of the software without excessive marketing fluff.
*   **Efficient:** Uses active verbs like "integrate," "accelerate," and "empower" to describe business outcomes.
*   **Reliable:** Emphasizes technical stability and high-quality customer support through professional, straightforward language.
*   **Interconnected:** Highlights the relationship between different tools and teams using bridge-related metaphors.

## Tone by context
| Context | Tone |
|---|---|
| Marketing Hero | Direct and benefit-oriented, focusing on productivity and team alignment. |
| Customer Testimonials | Enthusiastic and appreciative, highlighting support quality and ease of use. |
| Educational/Resources | Informative and authoritative, addressing technical factors and coordination. |
| Call to Action | Low-friction and inviting, offering trials and evaluations. |

## Lexicon
- **Use:** Seamless, integration, collaboration-focused, top-notch, bridge, empower, accelerate, cross-team alignment, curate, visibility.
- **Avoid:** Disconnected, manual entry, silos, complex setup (use "minimal amount of configuration" instead).

## Messaging do's and don'ts
*   **Do:** Emphasize the connection between Support and Engineering teams.
*   **Do:** Mention specific software ecosystems (Salesforce, Jira, Slack, Confluence) to ground the value.
*   **Do:** Use the word "Seamless" when describing the flow of issues or threads.
*   **Don't:** Use overly casual slang or "tech-bro" jargon.
*   **Don't:** Focus only on the tool; always mention the "Teams" or "Processes" being improved.
*   **Don't:** Overcomplicate the installation narrative; keep it focused on "minimal configuration."

## Evidence
- "Integrate Teams, Processes, and Tools"
- "Seamless Thread for Issues"
- "Improve customer support productivity, collaboration with engineering and other teams"
- "Accelerate efficiency and empower cross-team alignment"
- "Installation requires a minimal amount of configuration"