GoWeBa Communication Guide
This guide defines the tone, voice, and communication best practices for anyone representing GoWeBa — whether in official writing, customer support, social media, or marketing.
Brand Voice
GoWeBa speaks like an experienced and supportive colleague who simplifies the complex. Not a salesperson. Not a robot. An ally.
The 4 Pillars of Our Voice
| Pillar | Description | Example |
|---|---|---|
| Clear | We avoid jargon. We explain simply. | "GoWeBa manages your contacts and emails" — not "omnichannel relationship management solution" |
| Warm | We're friendly. We encourage. We celebrate wins. | "Awesome! Your first contact has been created 🎉" |
| Honest | We don't oversell. If a feature is in development, we say so. | "This feature is coming soon — we're working on it!" |
| Actionable | Every communication should guide toward a concrete action. | "Click here to create your first contact" |
Informal vs Formal Tone
GoWeBa uses an informal, friendly tone across all communications:
- ✅ "Create your first contact"
- ❌ Overly formal or corporate language
Exception: Legal documents (terms of use, privacy policy) use formal language by legal convention.
Tone by Context
| Context | Tone | Example |
|---|---|---|
| Onboarding | Enthusiastic and encouraging | "Welcome! We're happy to have you 🙌" |
| Documentation | Informative and precise | "To create a contact, click + New Contact" |
| Error/Bug | Empathetic and solution-oriented | "Oops, something didn't work. Try again or reach out to us." |
| Marketing | Inspiring and concrete | "35 AI experts who never sleep — that's WEBA." |
| Support | Patient and detailed | "No worries! Here's how to fix this, step by step." |
| Social Media | Casual and engaging | "Your CRM that thinks ahead 🧠✨ #GoWeBa #CRM #AI" |
WEBA — The AI Personality
WEBA has its own voice within GoWeBa:
| Trait | Detail |
|---|---|
| Name | WEBA (always in uppercase) |
| Gender | Neutral (we say "WEBA", not "he" or "she") |
| Tone | Professional yet warm |
| Style | Friendly, short sentences, moderate emoji use |
| Pronouns | "I" when WEBA speaks about itself: "I created the contact for you" |
| Limitations | WEBA never lies. If it doesn't know, it says so: "I don't have that information." |
WEBA Message Examples
- ✅ "I've created the event in your calendar for tomorrow at 2 PM ✅"
- ✅ "I couldn't find that contact. Would you like to create one?"
- ✅ "Here's a summary of your 3 most recent unpaid invoices."
- ❌ "ERROR: Contact not found in the database." (too technical)
- ❌ "Of course! I'm here to help you, dear valued customer!" (too formal + over-the-top)
Writing Rules
Punctuation
- Exclamation marks: Maximum 1. Never "!!!"
- Ellipsis: Avoid. Prefer a period or a dash.
- Emojis: Used sparingly. 1-2 per message maximum.
Preferred Terminology
| ✅ Say | ❌ Avoid |
|---|---|
| Platform | Software, application |
| Module | Feature (when referring to a full module) |
| Credits | Tokens, units |
| Organization | Account, tenant |
| Member | User (in a team context) |
Multilingual
GoWeBa is available in 3 languages:
| Language | Code | Primary Market |
|---|---|---|
| French | FR | Québec, French-speaking Canada |
| English | EN | Rest of Canada, international |
| Spanish | ES | Future expansion |
Rules:
- French is the primary language and must always be updated first
- Translations must be natural, not literal
- Proper names are never translated (GoWeBa, WEBA, Webabox, MyAtlas)