Slack and Salesforce · decide these before connecting them
Nothing breaks on the day.
What changes is where the reasoning lives.
Connecting the two is usually a good decision, and it quietly moves the part of the work that is hardest to reconstruct into a system with a different access model, a different retention policy and a different owner. Six gaps that opens, and the read only check for each.
Reviewed 30 August 2026.
The shape of it
The record and the reasoning end up in different systems.
Salesforce holds what is true about a customer. The conversation that decided what is true happens where the team already talks. Once those are two places, everything below follows: access is governed twice, retention is set twice, and the half that explains the other half is the half nobody can search in a year.
None of this is a defect in either product. It is what happens when a system of record and a system of conversation are joined without anybody writing down which one wins.
Gap 01
The sharing model stops at the channel wall
A record preview posted through the integration can respect Salesforce permissions, but that is a setting rather than a guarantee: unfurl behaviour is chosen by an administrator, and it is worth confirming which option your org is on. What a person types or pastes into the channel is governed by nothing at all, because it is ordinary text. In practice that is how most of the sensitive detail arrives: an amount, a name, a reason for a discount, quoted into a channel whose membership was decided by whoever created it.
How to check it
Check which unfurl option the org is set to, then list the channels where customer or deal detail is discussed and compare their membership against who can open those records in Salesforce. The difference is your actual access model.
Gap 02
The record says what changed, the thread says why
Field history tells you an amount moved and who moved it. The argument that produced the decision happened in a thread, and it is not attached to anything. Six months later the record is the only thing anybody can find, so the decision looks arbitrary and gets reversed by somebody reconstructing it from the outcome.
How to check it
Take three closed deals with an unusual discount and try to find the reason using only Salesforce. If you cannot, the reasoning for every deal is living somewhere with different retention rules.
Gap 03
Two retention policies over one conversation
Salesforce and Slack are configured separately, by different people, usually to different answers. A customer conversation that spans both is therefore governed by two policies at once, and which one applies to a subject access request or a legal hold is a question with a legal answer rather than a technical one.
How to check it
Ask who set the Slack retention period and who set the Salesforce one. If it is two people who have not spoken, that is the finding.
Gap 04
Leavers take the context, not the records
When somebody leaves, their opportunities and accounts are reassigned in an afternoon. The direct messages where half of the relationship lived are not reassigned to anybody, and often not readable by the person inheriting the account. The handover is complete on paper and missing exactly the part that was hard to write down.
How to check it
Before the next handover, ask the person leaving where the context for their three largest accounts is. If any answer is a direct message, that is a process gap and not a tooling one.
Gap 05
The better the collaboration, the emptier the CRM
This is the uncomfortable one. Connecting the two makes it pleasant to discuss records without opening them, so more of the thinking happens in the channel and less is written where the record is. The CRM becomes less complete precisely as the team becomes better at working together, and the reporting degrades without anybody doing anything wrong.
How to check it
Compare logged activities per opportunity in the six months before and after the integration was switched on. A fall is not a discipline problem, it is the predictable result.
Gap 06
An agent reading a channel is acting on text nobody governs
An agent that summarises or acts on channel conversation is consuming unstructured text with no field level security, no ownership and no record of what it read. What an agent exposes about an org applies here twice over. Everything the platform gives you on a record, it does not give you on a message. If agents are on the roadmap, this decision belongs before the integration rather than after.
How to check it
Write down what an agent is allowed to read from conversation, and where the output of that reading is stored. If the answer to the second is a channel, the loop is closed and ungoverned.
What to write down first
Three sentences, and they cost nothing before the integration.
Which categories of customer detail must never be typed into a channel. Which decisions must be written on the record before they count as taken. And how long each system keeps a conversation, agreed by the two people who set those numbers rather than separately.
Written before, these are three sentences. Written after a year of habits, each one is a change to how people already work, which is a different and much more expensive kind of project.
Asked often enough to answer here
Questions
Is connecting Slack and Salesforce a bad idea?
No, and this page is not an argument against it. It is an argument for deciding six things before rather than after, because every one of them is cheap to settle in advance and awkward to retrofit once the team has a year of habits built on the current arrangement.
Which of the six matters most?
The retention question, because it is the only one with a legal consequence rather than an operational one. The others cost you clarity and reporting quality. That one can cost you a defensible answer to a regulator or an opposing lawyer, and it is settled by two people agreeing a number.
Why would activity logging fall after an integration?
Because the integration removes the friction that used to force people into the record. When discussing an opportunity requires opening it, notes get written. When it does not, they do not. The fix is not a policy telling people to log more, it is deciding which specific things must reach the record and making that path shorter than the channel.
Can this be audited without changing anything?
Yes, and it should be. Channel membership against record access, retention settings on both sides, and activity volume before and after are all read only questions. None of them require touching a configuration, and the answers decide whether anything needs to change at all.
What does it cost to have somebody do this?
It falls inside the engagement priced at 2,750 euro for 55 hours on this site, which is the one about nobody being able to change the org safely, because that is the same problem: decisions that live somewhere nobody can find them. A narrower read only diagnostic against your own exports is 500 euro, delivered within three working days.
€2,750 for 55 hours is the engagement about an org nobody can change safely, which is the same problem in a different place. A narrower read only diagnostic is €500 within three working days, and every price here is published rather than quoted.
Serhii Skrypnyk · Senior Salesforce Administrator and developer · 7 Salesforce certifications · on the platform since 2018. Reviewed 30 August 2026.