Most small firms on Microsoft 365 settle into the same shape. Clients write by email, and colleagues talk in Teams. That’s a sound way to run a firm, and you don’t need to change it. The work that needs care is the thread between: a client asks something, a colleague has the answer, and the reply has to get back to the client. This page walks that crossing. It also covers the day a client messages you in Teams, or asks to join your team. Every Microsoft behavior described here was checked on Microsoft’s own pages on October 4, 2026.
Clients on email, colleagues on Teams
The split holds up because each side gets the tool it already uses. Your clients have an inbox and expect a reply there. Your team has Teams, where a quick question gets a quick answer. Neither group has to learn the other’s habits.
Most threads sort themselves. A thread with a client in it lives in email. A quick question between two of you lives in Teams. The full test for a thread that could go either way is in which one a thread belongs in.
The threads that need both are where the care goes.
Carrying a client’s question to a colleague, and the answer back
A client emails you. You need a colleague’s view before you reply. Here’s the round trip that keeps the client’s thread whole.
- Bring the email into Teams. Share it to a channel or a chat, or forward it to the channel’s address. The original stays in your mailbox. How each route works is in sending email to a Teams channel.
- Talk it over in Teams. This is what Teams is good at. Three quick turns settle what a day of email would.
- Name who replies. One line does it: “I’ll answer her.” Without it, two people reply, or nobody does.
- Reply in Outlook, to the client’s original email. The answer lands in the client’s own thread, from your own address.
- Close the loop in the channel. A short “answered” tells the team the question is done.
Step 4 is the one that catches people. Replying to the shared email inside Teams feels like answering the client. It doesn’t reach them. Microsoft’s page on emailing a channel says so directly:
“Replying to the post in Teams doesn’t send an email reply to the original sender.”
So the team’s reply stays inside the firm. The client still sees an open question until somebody answers in Outlook.
One more care on the way back. If you turn a channel post into an email, Teams sends the whole conversation, colleagues’ asides included. What goes out, and how to check it first, is in what Share to Outlook sends. For a client, it’s usually cleaner to write the reply fresh and keep the team’s talk in Teams.
When a client messages you in Teams
Some clients use Teams at their own firm. They can find you and send a chat message, the same way a colleague does. Microsoft calls this external access. Microsoft’s overview of guest and external access says “By default, external access is enabled.”
Here’s what that chat can and can’t do, from Microsoft’s comparison table:
- You can chat and call each other.
- You can add the client to a group chat, or invite them to a meeting.
- You can’t share files with them in that chat.
- They can’t see your teams or channels.
A one-to-one chat is between the two of you. Your colleagues don’t see it unless you add them to a group chat.
A quick answer in that chat is fine. Anything with weight belongs in email: a fee, a deadline, a document, a decision you’d want to find by date later. A light way to move it is to answer in the chat with “I’ll send that by email so it’s on file,” then send it. The client’s email thread stays the one place the work lives.
If a client messages while you’re away from Teams, Microsoft may email you about it. How to tell a real notification from a fake one is in Teams notification emails.
When a client wants to join your Teams
Sometimes a client asks to work with you inside Teams. A long project, a shared set of files, a team on their side who live in Teams. Microsoft offers three ways in, and they differ in what the client can see.
| Way in | What the client needs | What they can see | Files |
|---|---|---|---|
| External access chat | Their own Teams, at their own organization | Only chats and meetings they’re added to | Not in the chat |
| Guest in a team | Any business or consumer email address | Every standard channel in that team | Yes |
| Shared channel | Their own Microsoft 365 organization, set up to connect with yours | Only that one channel | Yes, in that channel |
Each one asks something of your admin. Guests need guest access turned on. Shared channels with outside people need both firms to set up cross-tenant access in Microsoft Entra ID. Microsoft’s shared channels page says “Each organization that you want to share channels with must also complete this configuration.” For a small firm, that last one depends on the client’s IT as much as yours.
Guest access is the one most small firms can actually use. Microsoft’s guest access page says “Anyone with a business or consumer email account, such as Outlook, Gmail, or others, can participate as a guest in Teams.” It also says guest access works with Microsoft 365 Business Standard, Enterprise and Education plans with “No extra Microsoft 365 license.”
Before you add a client as a guest
A guest added to your firm’s main team can read your firm’s channels. This is the one place the split costs something if you get it wrong. Standard channels are open to every member of the team, and guests are members. Microsoft’s channel overview describes standard channels as “open to all team members,” and its comparison table says guests can take part in them. That includes the channel where the team discusses that very client.
The safe shape is simple:
- Give each client their own team. Add the client as a guest there, with only the colleagues on their work.
- Keep internal talk in your firm’s own team. The client never joins it.
- Read the history first. If you reuse an existing team, everything already posted in its standard channels is there for the guest to read.
Then the mechanics. A team owner adds the guest from the team’s More options > Add member, once your admin has turned guest access on. That’s in Microsoft’s add guests to a team page. The guest gets a welcome email. Access isn’t instant. Microsoft says “it can take up to 12 hours for them to have access.”
When the work ends, the guest can leave the team. Their account stays in your directory until an admin removes it. Microsoft’s guest access page says “Your Microsoft Entra admin must remove the guest account.” Put that on the list for the end of each engagement.
A shared channel has a version of the same care. Microsoft says new members of a shared channel “can see all conversations (even old conversations).” Start a fresh channel for a client rather than adding them to one with history.
Chatting with a client by email address
You may have read that Teams would let you start a chat with anyone, using only their email address. Microsoft announced it in message center item MC1182004. The client would get an email inviting them in as a guest. On May 8, 2026, Microsoft updated that item to say “We are not releasing this feature at this time.” As of October 4, 2026, a client without Teams reaches you the way they always have, by email.
Where the client’s email waits while the team talks
While a question is out with a colleague, the client’s original email is still in your Microsoft 365 mailbox, unanswered. That’s the part that slips. The channel feels busy, so the thread feels handled.
Point works from that mailbox. The client’s email keeps its place in your feed, ranked by what the client asked and when it’s due. When the team has agreed the answer, Point can prepare the reply in the way you write. With the default settings, nothing goes until you’ve looked it over and sent it yourself. It leaves from your own address and lands in the client’s thread. The talk stays in Teams, where it started.
How chat and email can sit in one ranked list is in chat and email in one ranked feed. Scheduling, follow-ups and the morning briefing sit alongside it on the benefits page, so you can judge the whole of it.
Common questions
Should clients be on Teams or email?
For most small firms, email. Every client has an inbox, and the thread is easy to find later by date and sender. Teams fits a client on a long project who already uses it, and then best in a team of their own.
Can a client see our internal Teams channels?
Only if they’re a member of the team. A guest added to a team can take part in its standard channels, so a client added to your firm’s main team could read them. Give each client their own team instead.
If I reply in Teams to a client email shared to a channel, does the client get it?
No. Microsoft says “Replying to the post in Teams doesn’t send an email reply to the original sender.” Answer the client from Outlook, in reply to their original email.
Can I send files to a client who chats me from their own Teams?
Not in that chat. Microsoft’s comparison table says you can’t share files with external access users. Send the file by email, or add the client as a guest in a team of their own.
How long does it take for a guest to get into a team?
Microsoft says it can take up to 12 hours after the guest is added. Send the invitation a day before you need them in.
Can I chat in Teams with someone who doesn’t use Teams?
Not as of October 4, 2026. Microsoft planned a way to start a chat from an email address, then said on May 8, 2026, that it’s “not releasing this feature at this time.” Email is the route for those clients, or guest access in a team.