Team communication
Put the right customer request in front of the right Slack team
A customer handoff is only useful if someone sees it and understands what to do. Bob turns a conversation into a concise Slack update containing the request, relevant context, and a clear next action.
Bob posts the customer request, the relevant context, and the next action into the Slack channel your team uses.
Make notifications worth opening
Office 168/52 can connect front-office workflows to the channels your team has authorized. Instead of dropping a raw transcript into chat, Bob can prepare a focused recap and link back to the work. Your team decides which requests deserve a notification and where different types of work should go.
Workflows
Route an important request
Send supported notifications to the configured channel when a conversation needs the team’s attention.
Keep the useful context together
Include the issue, urgency, owner or destination, and record link appropriate for the receiving team.
Follow up in the right thread
Use supported message or thread actions to keep related updates together and reduce scattered handoff messages.
Example workflow
Example workflow
An after-hours customer asks about a time-sensitive service problem. Bob gathers the relevant details and prepares a notification for the designated Slack channel. The person taking over can open the linked request and see what has already been asked.
Illustrative example, not a live execution log.
Connection and setup
Authorize the Slack workspace, select approved channels, and configure the event and approval rules for messages and handoffs.
How Bob turns a conversation into a useful next step
Bob starts with the customer's request and the business information you approve. When the workflow needs a current record, Bob retrieves it from the connected service. When the next step changes a record or sends a message, Bob follows the permissions and approval steps you configure. The customer gets a useful next response, and your team gets a clear handoff when a person needs to take over.
Questions
Does Bob need access to every Slack channel?
No. Access should match the intended workflow. A channel-notification use case does not require treating all company chat as a knowledge source.
Can we approve actions inside Slack?
Only if a supported interactive approval flow is implemented. Otherwise Slack should link to the existing approval experience in Office 168/52.
Who decides what Bob can change or send?
You choose the records Bob reads and the actions he takes. A reply, a record update, or an outbound message follows the approval step you set for that workflow. See the pricing page for plans. This page does not list prices.
Continue this workflow with
These are related workflows, not prerequisites.
Get started with Slack
Tell us how your front office handles this job today. You send the message when you are ready.