KoltrixSignatures and tone for shared mailboxes: a team agreement
Personal or team sign-off? What goes in a signature? How five people sound like one team? A FAQ for agreeing on signatures and tone in shared mailboxes.
On this page(12 sections)
- Should we sign with our own names or the team name?
- What belongs in a shared mailbox signature?
- How do five people sound like one team?
- What greeting should we use?
- How formal should we be?
- When should someone switch from team voice to personal voice?
- What about sign-off phrases?
- Do we put the team name in the From field?
- What about new hires and contractors?
- How do we enforce this without being annoying?
- A starter agreement
- Bottom line
When five people reply from support@, customers notice the differences before they notice the answers: one person writes "Cheers!", another signs with a full legal disclaimer, a third doesn't sign at all. None of these is wrong on its own. Together they make the team look disorganized.
A short team agreement on signatures and tone fixes this without turning everyone into a script reader. Here are the questions teams usually need to settle, with suggested answers and examples.
Should we sign with our own names or the team name?
Sign with your own first name, from the team address. This gives customers a human to talk to while keeping replies attached to the shared mailbox.
Signing as "The Support Team" can feel faceless, and customers often respond more warmly to a name. It also makes accountability clearer inside the team: everyone can see who answered.
The exceptions:
- Automated messages (auto-acknowledgments, status notices) should sign as the team, since no person wrote them.
- Very sensitive situations, such as dealing with an abusive sender, where some teams prefer the team name to protect individuals. That's a reasonable choice; just make it consciously.
Example:
Priya
Support, Example Analytics
What belongs in a shared mailbox signature?
Less than most people think. A good signature contains:
- First name (and last name if your team prefers)
- Role or team
- Company name
- One useful link, such as your help center or status page
What to leave out:
- Phone numbers nobody answers
- Several social media icons
- Inspirational quotes
- Long legal disclaimers, unless your legal advisor genuinely requires one
- Large image logos, which often show up as attachments or blocked images
Keep everyone's signature identical in structure, so only the name changes.
How do five people sound like one team?
You don't need identical writing. You need a few shared habits that make replies feel consistent. Agree on a short list, for example:
- Answer the question in the first paragraph.
- Use plain language; no internal jargon or feature codenames.
- One apology at most, and only when something actually went wrong.
- Always say what happens next, and when.
- Contractions are fine ("we're," "you'll"); slang isn't.
Five habits like these do more for consistency than a long brand-voice document. Post them where people write, such as the top of your snippet library.
What greeting should we use?
Pick a default and stick to it. "Hi [first name]," works for most SaaS teams. A few guidelines:
- Use the name the customer signed with, not the one in their email address. If they sign "Liz," don't write "Hi Elizabeth."
- If there's no name, "Hi there," is fine. Avoid "Dear Customer."
- Match formality upward: if a customer writes "Dear Sir or Madam," a slightly more formal reply is appropriate. If they write "hey," you don't have to match downward to "hey."
How formal should we be?
Default to friendly-professional: warm, clear, not chummy. Adjust for context:
| Situation | Tone |
|---|---|
| Everyday questions | Friendly-professional |
| Enterprise or procurement contacts | More formal, fewer contractions |
| Upset customer | Calm, specific, no jokes |
| Long-time customer you know well | Can be more relaxed |
| Security or account-access issues | Plain and precise |
When should someone switch from team voice to personal voice?
A shared mailbox reply speaks for the team. Sometimes a personal note is the right call:
- The customer has worked with one person repeatedly and the relationship is personal.
- A significant mistake happened, and a personal apology from the person responsible (or a lead) carries more weight.
- A founder or senior person steps in on an escalation. Having them say so explicitly ("I'm one of the founders, and I wanted to reply myself") signals that the issue is being taken seriously.
When switching, make the handoff clear. If you take over a thread from a colleague, say so: "Hi Dana, I'm picking this up from Sam."
What about sign-off phrases?
Choose one or two acceptable sign-offs and let people pick between them. "Thanks," and "Best," cover most situations. Avoid sign-offs that can read oddly in certain contexts, such as "Cheers!" on a refund denial, or "Warmly" from a team address.
Do we put the team name in the From field?
Usually the From name should show both the person and the team, for example "Priya at Example Analytics." It tells the customer which company the email is from, even in a crowded inbox, and still feels human. Whatever you choose, make it consistent across everyone who sends from the address.
What about new hires and contractors?
Give them the agreement on day one, along with a handful of real replies that show it in practice. Examples teach tone faster than rules. For the first week or two, have someone review their replies before they go out, with feedback focused on the shared habits rather than personal style.
Contractors and temporary help should follow the same signature format as everyone else. Customers can't tell who is on contract, and they shouldn't have to: a reply from support@ should look and sound like the team, whoever wrote it.
How do we enforce this without being annoying?
- Make the defaults easy: set up signatures centrally if your tool allows it, or give everyone a copy-paste version.
- Review a few replies in your weekly meeting, focusing on clarity and helpfulness, with tone as part of that.
- Lead by example. If founders and leads ignore the agreement, nobody else will follow it.
- Revisit it twice a year. Tone norms evolve as the team and customers change.
A starter agreement
SIGNATURES
- Sign with first name + "Support, [Company]" + help center link.
- From name: "[First name] at [Company]".
- Auto-replies sign as "[Company] Support".
GREETINGS AND SIGN-OFFS
- "Hi [name the customer signed with]," or "Hi there,".
- Sign off with "Thanks," or "Best,".
TONE HABITS
- Answer first. Plain language. One apology max.
- Always state the next step and when.
- Contractions fine, slang not.
SWITCHING VOICE
- Say so when taking over a thread.
- Founders/leads introduce themselves on escalations.
Bottom line
Agree on a simple signature, a default greeting, a couple of sign-offs, and four or five tone habits. Sign with your own name from the team address, adjust formality to the situation, and make handoffs between people explicit. That's enough for five writers to sound like one team without anyone sounding like a template.
Start with Koltrix
Your domain, one inbox, and an API that sends.
A team inbox where AI sorts and drafts (nothing is sent without your click), plus the transactional API and SMTP relay your product sends with. 7 days free, no card.
