Skip to content
IZI

Support Tone of Voice

Published: · Updated: (12 days ago)· IZI Team

Support Tone of Voice

Section titled “Support Tone of Voice”

Support communication should reduce uncertainty for the club. A support agent does not have to resolve every issue independently — but they are responsible for the communication chain: gather information, identify the next step, route to the right person, get a timeline, and return to the chat with a clear status. IZI’s CRM records every session and club action, giving support the context needed to open with facts rather than questions.

1. Calm and to the point

Section titled “1. Calm and to the point”

Support does not panic, does not argue, and does not write emotionally. Every reply should make the situation feel more understood and more manageable.

Write:

Got it, we will check this now.
I can see the issue on PC12 — investigating the cause.

Do not write:

That's strange.
I have no idea what happened.
Everything is broken.

2. Formal address

Section titled “2. Formal address”

Write to clubs and their clients formally and respectfully, even when the internal team uses casual language. Consistent courtesy signals professionalism and keeps escalations from feeling personal.

Write:

Please send a screenshot of the error.
Please do not restart the PC yet — we are still investigating.

3. No ALL CAPS

Section titled “3. No ALL CAPS”

Capital letters read as shouting and raise tension in already-stressful moments.

Do not write:

URGENT DO NOT RESTART THE PC

Write:

Important: please do not restart the PC yet — we are still investigating.

4. Acknowledge first

Section titled “4. Acknowledge first”

The club needs to know their message was received and that work has started — before any diagnosis or solution is given.

Write:

Got it, we are on it.
I can see the issue on PC12. Checking the cause now.

Skipping acknowledgement forces the club to send follow-up messages (“are you there?”), which clogs the chat and wastes time on both sides.

5. One concrete next step

Section titled “5. One concrete next step”

Do not ask clubs to “try something.” Ask for a specific action or a specific piece of information.

Write:

Please restart PC12 and let us know whether the status changes.
Please send a photo of the error message on the screen.
Tell us the PC number and the time the issue first appeared.

Vague requests (“try rebooting things”) create back-and-forth loops. One precise request moves the investigation forward in one exchange.

6. Do not promise what you cannot control

Section titled “6. Do not promise what you cannot control”

If you do not control the timeline, do not state one.

Do not write:

We will fix this right now.
Everything will be ready in five minutes.

Write:

We are checking the cause and will report back with results.
We have passed this to the responsible specialist and are confirming the timeline.

7. Support as process owner

Section titled “7. Support as process owner”

When an issue cannot be resolved independently, support does not go silent and does not abandon the chat. The job is to drive the chain to a clear status.

The correct escalation chain:

1. Collect information about the issue from the club
2. Determine whether it can be resolved without escalation
3. If not — go to the project manager or relevant specialist
4. Obtain a deadline or the next concrete step
5. Return to the club chat and report the status and timeline
6. If the deadline falls within the current shift — monitor it personally
7. If the deadline falls on another shift — create a tracked task with the responsible agent assigned

This process ensures no issue falls through the gap between shifts or between team members.

8. Keep the chat moving

Section titled “8. Keep the chat moving”

Even when a problem is not immediately solvable, the club must see progress. Two hours of silence is always wrong.

Poor:

[no reply for two hours]

Good:

We have done an initial check. The issue requires input from the project manager.
We are confirming the timeline and will update you shortly.

A mid-investigation status update costs one message and removes the club’s anxiety about whether anyone is working on it.

Quick formula

Section titled “Quick formula”

Every support message can be structured around five elements:

Acknowledged → what we see → what we are doing or who we have escalated to → expected timeline → who is responsible

Not every message needs all five, but every message should move the conversation at least one step along this chain.

See also

Section titled “See also”

Frequently asked questions

What is the goal of every support message to a club?

To reduce uncertainty. Every message should leave the club with a clearer picture of what is happening and what comes next — even if the problem is not yet resolved.

Should support agents use all caps for urgent warnings?

No. All-caps reads as shouting and increases panic. Use 'Important:' as a plain-text prefix instead.

What if support cannot solve the issue on their own?

Support is the process owner, not the only problem solver. Escalate to the project manager or specialist, get a deadline, then return to the club chat with a clear status update.

How quickly should support acknowledge a club message?

Acknowledgement should come before a solution. Even a short 'Got it, we are looking into this' keeps the club informed and prevents follow-up messages.

What if the deadline falls on a different shift?

Create a task in the task tracker (e.g., Todoist) with the responsible agent assigned. Do not leave resolution to memory or informal handoffs.

Can support promise a fix within five minutes?

Only promise what you control. 'We will investigate and report back' is honest; 'fixed in five minutes' is a promise that may not hold.