Salesforce records, inside Microsoft Teams
Decisions get made in Teams. The record sits in Salesforce. Salesforce Teams integration puts one inside the other so the conversation and the record stop being separate places.
This is more than alerts. Records can be mentioned, opened, edited and approved without leaving the channel, including by people who do not hold a Salesforce licence.
What syncs between Teams and Salesforce
The first-party Salesforce app for Teams covers four distinct things.
- Record mentions. Reference an account, opportunity, case or contact in a channel or chat and colleagues can open the full record from the message.
- Embedded record view. The whole record, viewable inside Teams, without switching applications.
- In-line editing. Update Salesforce data directly from the Teams conversation or a pinned tab.
- Channel notifications. Alerts on the records that matter, visible to the whole channel.
- Approvals. Approvers get the request in Teams and can approve or reject with comments, in the conversation, and it moves down the chain.
Teams channels can also be pinned to a Salesforce record, so the deal or case has its own thread that travels with it.
Which way the data flows between Teams and Salesforce
Mostly read, with deliberate write. That balance is the design decision.
⇆ Two way→ Out of Salesforce← Into Salesforce
Nothing forces you to allow editing from Teams. Some clients open it up for speed, others keep Teams read-only and make Salesforce the only place records change. Both are defensible; decide it rather than inherit it.
What a Teams integration gives you
Fewer context switches, and information reaching people who would never open Salesforce.
- People without licences stay informed. Finance, delivery and leadership see what matters without a seat each.
- Approvals stop being the bottleneck. A discount approval actioned in the conversation takes minutes, not the next time someone opens the CRM.
- The deal thread has one home. A channel pinned to the opportunity keeps the discussion with the record rather than scattered across DMs.
- Less switching. Small on any one occasion, meaningful across a team and a quarter.
- Context reaches the record. When the conversation and the record sit together, the useful detail is far more likely to be captured.
How we connect Teams to Salesforce
The question to settle before you build the Teams integration
What is worth interrupting someone for?
Notifications are the easiest part to configure and the fastest to ruin. A channel that alerts on every field change is muted within a fortnight, and once muted it is never unmuted, so the genuinely important alerts are lost with the noise.
The useful version is narrow: the deals above a threshold, the cases breaching SLA, the approvals actually waiting on someone. That is a process question rather than a configuration one, worth an hour before anyone switches anything on.
The second question is whether Teams should be able to change Salesforce data at all. Allowing edits is quicker; restricting them keeps a single, auditable place where records change.
The discount approval that took four days
A rep needs 12% signed off. The approver is in back-to-back meetings, does not open Salesforce between Tuesday and Friday, and the customer has a competing quote with a deadline on Thursday.
With approvals surfaced in Teams, that request arrives where the approver already is, and it is actioned with a comment in the gap between two calls. The four days becomes four minutes, and the deal does not go to a competitor over an administrative delay.
The second use is quieter but adds up. A channel pinned to a major account means the discussion about that customer lives with the customer, rather than being scattered across direct messages that nobody outside the thread can find. When the account manager changes, the context is still there.
And people without a Salesforce licence stay informed. Finance, delivery and the leadership team see what matters through channel notifications without a seat each, which is often the difference between an integration paying for itself and not.
The one discipline to hold: decide what genuinely warrants an interruption before switching anything on. A channel that alerts on every field change is muted within a fortnight, and it is never unmuted.
Connect Microsoft Teams to Salesforce
The technical setup is straightforward. Deciding what deserves a notification, and whether Teams can write back, is the part that determines whether people keep it switched on.
Whatever you run alongside it, if it has an API it can be connected, so get in touch and we will tell you what is realistic.
Salesforce Teams integration: frequently asked questions
Yes. As well as mentioning and viewing records in a channel or chat, the integration supports in-line editing, so a record can be updated from the Teams conversation or from a pinned Salesforce tab. Whether you enable that is a decision worth making deliberately, because some organisations prefer Salesforce to be the only place records change.
They can see what is shared into the channel, such as notifications and the detail included in a record mention. Opening the full record still requires appropriate Salesforce access. For finance, delivery or leadership who need visibility rather than a seat, notifications and mentions usually cover it.
Yes. Approvers receive the request in Teams and can approve or reject with comments without leaving the conversation, and Salesforce moves the approval down the chain as normal. This is often the single biggest time saving of the whole integration.
By deciding what genuinely warrants an interruption before anything is configured. We would rather set up five alerts people act on than fifty that get the channel muted. It is a process conversation, not a configuration one.
No. Some clients keep an internal owner and buy specialist depth around them, others hand the platform to us completely. We will recommend one or the other based on the shape of your team rather than what suits us.