For COOs and heads of operations
Sales promised it. Finance never heard. Your customer noticed.
Work drops between teams because every handoff lives in a different inbox, chat or spreadsheet. We set up Slack with your CRM so each handoff has an owner, each approval has a trail, and vendors work from the same facts as your team.
The week
Where the work drops.
The honest no: if the work is a software factory with a named delivery date, we are the wrong partner.
The work
What changes in the week.
Slack is where the work moves. Salesforce stays the record. Each step stands on its own.
How it starts
One handoff first. Then the next.
See it in your business
The handoffs operations owns.
Each card says what happens today and how it runs in Slack. Open the ones that fit and send them to us.
All use casesSee every department, filter, and send us the list that fits.
- SalesDiscount and quote approvalsToday: Approvals wait in an inbox or happen in WhatsApp with no trail. In Slack: Request in #deal-desk, routed to the approver; the answer is written back to the CRM.Workflow Builder approvals, Salesforce Flow
- Customer serviceEscalation roomsToday: An urgent case bounces between teams by email. In Slack: The case opens a channel, pulls in the right people and closes with a summary on the record.Service Cloud for Slack, workflows
- Customer serviceShift handoverToday: Notes in a shared doc that nobody reads. In Slack: An end-of-shift post of open cases and who owns them.Scheduled workflow, Lists
- FinanceSpend and purchase approvalsToday: Purchase requests wait in email chains. In Slack: A request form routes by amount to the right approver; the decision is logged.Workflow Builder approvals
- OperationsMorning briefingToday: Leaders ask five people for status. In Slack: A daily message with pipeline, open escalations and what is stuck.Slackbot, scheduled workflow, CRM data
- OperationsDecision logToday: Decisions made on calls are forgotten. In Slack: Decisions posted to #decisions with an owner and a date, searchable later.Workflow Builder, Lists
- OperationsVendor and supplier channelsToday: Orders and delays tracked by phone. In Slack: A shared channel with each key supplier.Slack Connect
- OperationsCross-team projectsToday: Status meetings to find out who is blocked. In Slack: A project channel with a tracker and a weekly summary.Lists, Slackbot summaries
- OperationsMove off WhatsApp groupsToday: Company decisions live in personal WhatsApp groups. In Slack: The same groups as company channels, searchable, and kept when staff leave.Channel design and migration
Read next
What your IT team will ask.
FAQ
What operations leaders ask.
- Our customers are on WhatsApp. Do they have to move?
- No. Customer WhatsApp can stay. The internal decisions about the customer move to Slack, where the company keeps them.
- Do we need Salesforce?
- No. Slack works on its own, and Slack has a built-in CRM on some plans. Handoffs carry more when Salesforce is connected, because the record moves with the work.
- How do vendors join?
- Through Slack Connect, a channel shared between your workspace and theirs. We set the rules: which vendors, which channels, and who approves a new one.
- We already use Microsoft Teams. Is this a second tool to police?
- Only if nobody decides. Teams keeps meetings and files. Slack takes the work that crosses teams, systems and partners. We write a one-page rule on what goes where and train each team on it.
- Where is our data held?
- Slack offers data residency in several regions. We confirm with Salesforce which region applies to your plan before you sign, and write it in the proposal.
- How long before the first handoff runs?
- It depends on how many teams start. We write the scope and the first workflows down before any work starts, so you see it before you agree.
The brief · one email
Name the handoff that drops.
The honest no: if the work is a software factory with a named delivery date, we are the wrong partner.