Team Chat on a Phone System: Presence and Call Rules

Tom Reed · Updated 20 October 2026

Team chat works best when it sits in the same app as your phone calls and everyone follows a few shared rules. Agree what each presence status means and when to show as busy. Send a short chat before you ring a colleague, unless the matter is urgent or a customer is waiting. Keep the team directory and shared address book tidy so people can find the right person first time. And move a chat to a call as soon as it starts going round in circles. The rest of this guide turns those rules into something a small team can adopt this week.

This is a practical playbook for a business phone system with team chat, not a product comparison. SessionPBX is used as the worked example, and its Teams Phone and Teams Business plans are SessionPBX plans, not Microsoft Teams.

Why run team chat and calls in one app?

Most small teams already chat. The problem is where: quick questions spread across personal messaging apps, texts and email, while calls happen somewhere else. Nobody can see whether a colleague is free before they ring.

Putting team chat and calling in one app fixes three things:

• One place to look. People check one app for messages, missed calls and voicemail instead of four.
• Presence before contact. You can see who's available before you message or ring, so you interrupt less and wait less.
• A short path from chat to call. When a chat needs a conversation, the person is one tap away in the same app.

That combination is what people usually mean by unified communications: calling, messaging and presence working together. If you already run a hosted phone system, check whether its apps include messaging and presence before adding another tool. Our guides to the PBX phone system and the cloud-based phone system cover how the calling side works.

On SessionPBX, for example, the apps "keep direct messages, group conversations and file sharing alongside your calls", and the page describes the aim as to "bring voice and video calling together with direct messages, group chats and presence."

This guide is about the day-to-day rules inside that one app. If you need a wider plan for how a remote or hybrid team communicates, including response windows, handoffs and meetings, our guide to remote team communication for small businesses covers that.

What should presence status mean on your team?

Presence status only helps if everyone reads it the same way. Agree a short meaning for each status your app shows, and map your rules to the labels your app actually uses.

Available should mean "you can message me and I'll see it soon, and you can ring me if it's urgent." It shouldn't mean "I'm at my desk" or "my laptop is open".

Busy should mean "I'm focused or on a call. Message me, but don't expect a fast reply, and only ring if a customer is affected."

Away should mean "I'm not at my desk or not working right now. Message me and I'll pick it up when I'm back."

Then agree when people should show as busy:

• On a customer call or in a meeting. If your app doesn't change status during a call, set it yourself.
• Doing focused work that needs no interruptions, such as month-end, a proposal or a tricky support case.
• Covering the phones for a queue or a busy period, where a chat interruption could mean a missed caller.

Busy isn't a way to hide from work, and it shouldn't stay on all day. If you've been busy for most of the day, tell your team why so they can reroute work.

Presence also has a calling side. If someone is busy, their calls still need somewhere to go. On SessionPBX you can "forward calls when you're busy, don't answer or need all calls sent elsewhere", choosing an internal destination or an external number. Set that up for each person so a busy status never means a lost caller.

Presence etiquette table

It describes team habits, not features of any particular app.

Two habits make presence work: keep your status honest, and look at presence before you contact anyone.

When should you chat before you call?

Unplanned calls between colleagues interrupt people. A short chat first lets the other person choose when to answer and usually gets you a better answer.

A simple chat-before-call rule covers most situations:

1. Check presence. If the person is busy or away, chat and wait unless it's urgent.
2. Send one clear message. Say what you need, why and by when. "Can you confirm the delivery date for the Patel order? The customer's on hold for a callback this afternoon" is better than "Got a sec?".
3. Ask before you ring. If you think a call would be quicker, ask: "Can I give you a quick call about the Patel order?" Let them reply when they're ready.
4. Ring straight away only when it's urgent. A customer on the line, a live problem, or anything that can't wait for a reply.

Some calls should never wait for a chat. If a customer is on hold and you need a colleague, ring them or transfer the call after speaking to them first. Our guide to warm transfer vs blind transfer covers that handover. The chat-first rule is for internal questions, not for keeping customers waiting.

Avoid the empty "hi" message. Put the question in the first message so the other person can answer straight away.

Use direct messages and group chats for different jobs:

• Direct messages for questions to one person, private matters and anything that only needs one answer.
• Group chats for a team, project or customer account, where several people need the same information.

Read receipts help both sides. On SessionPBX you can "follow delivery and read receipts". Agree that "read" doesn't mean "done": if you can't act yet, a quick "seen, will reply this afternoon" stops the sender ringing to check.

How should your team use the directory and shared address book?

Chat and presence only help if people can find the right person quickly. That's the job of the team directory and the shared address book.

The team directory lists your colleagues. On SessionPBX you "find colleagues in the team directory and keep business contacts in a shared address book." Make the directory useful by agreeing:

• Display names people recognise. First name and surname, not initials or old nicknames.
• A role or team in the name or profile where your app allows it, so a new starter can tell sales from support.
• Short, logical extensions. SessionPBX gives "your team familiar, short extensions", and our guide to phone extension numbering plans explains how to lay them out.
• Removing leavers promptly, so nobody chats or rings someone who has gone. Our phone system leaver checklist covers the steps.

The shared address book holds business contacts everyone needs: key customers, suppliers, contractors and services. Treat it like any shared record:

• One owner. Someone keeps it tidy and removes duplicates.
• A naming rule. For example, "Company – Person – Role", so searches find the same entry every time.
• No personal contacts. Personal numbers stay on personal devices.

Call history ties the two together. On SessionPBX you can "review incoming, outgoing and missed calls in the app or portal to follow up on conversations." Agree that missed calls from customers get a follow-up, and that whoever follows up notes it in the relevant group chat so two people don't ring the same customer back.

For people who move between desks, sites or home, the directory and presence should follow the person, not the device. On SessionPBX, "the same account works across all four platforms, and message history syncs automatically." Our guide to the hot desking phone system covers the wider setup for shared desks.

When should a chat turn into a call?

Chat is good for quick questions, updates and anything people need to read later. It's poor at untangling confusion, handling emotion or making a group decision.

Chat or call decision table

Use these signals as team guidance. They're judgement calls, not hard limits.

The three-message rule is a useful default: if a thread has gone back and forth three times without a clear answer, one of you should offer a call. "This is getting long, can I ring you?" is enough.

Before you switch, check presence. If the other person is busy, suggest a time instead of ringing. When the call ends, post a one-line summary back in the chat: what you agreed, who does what and by when.

For more than two or three people, a quick group call often beats a long group chat. Our guide to conference calling for small businesses covers the options when you need everyone on the line at once.

Video helps when tone matters or you need to see the same thing. SessionPBX includes voice and video calling in its apps, so a chat can move to a voice or video call in the same app.

How do you set team chat rules without overloading people?

Team chat can create as much noise as it removes. A few simple limits keep it useful.

• Name group chats by purpose. "Sales team", "Support – Patel account", "Office move". Avoid vague names that attract off-topic messages.
• Mute what isn't yours. Only the chats tied to someone's role should notify them.
• Keep files with the conversation. On SessionPBX, file sharing sits alongside direct messages and group conversations. Share the file where the discussion is, so nobody has to hunt through email for the latest version.
• No customer data in casual chats. Keep sensitive details to the systems your business uses for them, and share only what a colleague needs.
• Respect working hours. A late-night message shouldn't demand a reply. If something is urgent outside hours, ring the person on call.

Keep the rules to one page and pin them in a team group chat.

How do you roll out team chat on your phone system?

A small team can roll out these rules in a few steps:

1. Check what your apps include. Confirm your phone system's desktop and mobile apps cover chat, group chats, presence and the directory. If you're using SessionPBX, these are part of the apps on Windows, macOS, iOS and Android.
2. Write the one-page rules. Use the presence etiquette and chat or call tables above as a starting point.
3. Tidy the directory and address book. Fix display names, remove leavers and agree the address book owner.
4. Set call forwarding for busy and no answer. Make sure each person's calls go somewhere sensible when they're busy or away.
5. Create a few group chats. One per team and one for the whole business. Resist creating more until people ask for them.
6. Move work chats over from personal messaging apps once the new app is ready.
7. Review the rules with the team after the first few weeks.

Presence and chat only work if the whole team is on the same app, so get everyone set up on desktop and mobile before you switch.

Team chat and presence on SessionPBX

SessionPBX is a hosted PBX with native apps for desktop and mobile and one portal to manage it. Calling, team chat and presence sit together: the apps "keep direct messages, group conversations and file sharing alongside your calls", and you can "see who's available, follow delivery and read receipts, and keep message history in sync across devices." People "find colleagues in the team directory and keep business contacts in a shared address book", and you can call colleagues and customers from Windows, macOS, iOS and Android.

Teams Phone covers "everyday calling, messaging, voicemail, team contacts and app provisioning, with SIP trunks for external calls." Teams Business adds ring groups, call queues, visual call flows with IVR and business hours, recording and supervision tools. Teams Phone and Teams Business are SessionPBX plans, not Microsoft Teams.

Internal team calls are included. For external calls, SessionPBX is bring-your-own SIP trunk: "external calls use your own SIP carrier, which bills you directly for numbers and calls." SessionPBX doesn't supply numbers or lines. Both plans include a 14-day free trial, with no setup fee or long-term contract. Compare plans and try team chat and calling together on the SessionPBX hosted PBX page.

FAQ

What is team chat on a business phone system?

It's messaging built into the same app you use for calls. On a business phone system with team chat, you can send direct messages and group chats, see who's available, and switch to a call without changing apps.

What does presence status mean?

Presence status shows whether a colleague is available, busy or away. It only helps if your team agrees what each status means and keeps it up to date, so write those meanings down.

Are SessionPBX's Teams plans different from Microsoft Teams?

Yes. Teams Phone and Teams Business are SessionPBX plans, not Microsoft Teams. SessionPBX is a hosted PBX with its own desktop and mobile apps for calling, team chat and presence.

Should we always chat before calling a colleague?

For internal questions, yes, unless it's urgent. Ring straight away when a customer is waiting or something is going wrong right now.

Is unified communications only for large businesses?

No. For a small team, unified communications simply means calls, chat and presence in one app. If your hosted phone system already includes them, you can start with the rules in this guide.