Chat with a Coworker in Slack or Microsoft Teams
Message a Coworker from Slack or Microsoft Teams, link your account the first time, approve its requests in the thread, and open the conversation in the app when needed.
Your administrator can connect a Coworker to Slack, Microsoft Teams, or both. Each connection is an app in that chat tool, named for the Coworker, and you message it like a colleague. The Coworker answers with your own permissions in Workforce Intelligence: it can see and do only what you can. Ask your administrator which apps are set up, or look for the Coworker's app in Slack or Teams.
Link your account the first time#
The Coworker only answers people whose chat account is linked to their Workforce Intelligence sign-in. This takes a minute and you do it once for each app.
- Send the app a direct message, for example "hello".
- The app replies privately, in the direct message, with a Link account button. Only you see it. The message says the link works once and expires in 15 minutes.
- Select Link account. Workforce Intelligence opens a page titled Link your chat account. If you are not signed in, it shows Sign in to continue; select Sign in, and after you sign in you return to this page.
- Check Confirm this chat account. It lists the App, the Slack workspace or Microsoft Teams organization, and your Account. It reads "Only confirm if you just messaged this app from this account." In Slack the workspace and your account show their names, with the ids in brackets beside them; when a name is not available the id stands alone. Select Confirm link only if that is true. Select Cancel otherwise.
- The page reads "Account linked" and "You can now message <app> from <Slack or Microsoft Teams>." Select View my chat accounts to see it in your settings.
If the page reads "This link has expired or was already used. Message the Coworker again to get a new one.", send the app another message. If it reads "This chat account is already linked to someone else in your company. Ask them to unlink it in their Settings, or ask your administrator for help.", that chat account belongs to a colleague's sign-in.
Never confirm a link you did not ask for. A link you were sent by someone else would connect their chat account to your sign-in.
Talk to the Coworker#
Send messages in the app's direct message (in Teams, a personal chat) as you would to a person.
- Replies. The Coworker answers in the same chat. A working indicator shows while it is at work, and a long answer arrives as several messages.
- Conversations. In a Slack direct message, each thread is its own conversation. A new message you send at the top starts a new thread that remembers what you talked about earlier, so you do not have to explain again. When you reply inside an older thread, the Coworker continues that thread, which does not include what you said in later threads, so "make it shorter" applies to the right answer. If you send a quick follow-up while the Coworker is still working, it is added to the same request and answered in the thread of your first message. In Microsoft Teams, your personal chat with the app is one continuous conversation. Each conversation is saved in Workforce Intelligence like any other, so you can find it under Chat and continue it there.
- Files. Attach up to 10 files to a message, each up to 10 MB. Any kind of file works: a spreadsheet, a document, a data file, an archive, a script or an image you paste or attach. The Coworker looks at images directly and puts every file in its working folder, so it can open it, read it, work through its contents and tell you what it found. A file you attach is also saved in the conversation in the app, where you can download it. Files and images the Coworker shares or creates are posted in the thread after its reply, each once: in Slack as an upload, in Microsoft Teams as a link to the file in Workforce Intelligence. At most 10 are posted with one reply. Teams passes files to the Coworker only in personal chats.
- Stopping. To stop a reply while the Coworker is working, use the stop control Slack shows on the working message, or open the conversation in Chat and select Stop. The Coworker then says it stopped, and any approval it was waiting for is cancelled and its buttons are removed. Only the person who asked can stop a reply; anyone else who selects the stop control is told so privately.
- Long or odd messages. A message longer than 32,000 characters is turned down with a request to shorten it, and a message with more than 10 files asks you to send fewer. If something goes wrong, the Coworker says "Something went wrong on my side. Please send your message again."
- No access. If you cannot chat with this Coworker, it says "You don't have access to chat with me. Ask your administrator." Access is the same as in the app.
In channels and group chats#
If your administrator has allowed it, you can mention the Coworker in a channel (in Teams, also a group chat) to ask it something there. It answers only when it is mentioned, every time: in a thread it is already in, a follow-up still needs a mention, and a message without one is not read by it. Three things to keep in mind:
- Everyone there sees the reply. The Coworker answers with only your permissions, but the answer goes to the whole channel. Ask for private information in a direct message instead.
- Each thread is its own conversation. In a channel, every thread you start with the Coworker is a conversation of its own, so a follow-up in a thread continues that thread and does not mix with your other threads. A new thread remembers your earlier conversations with the Coworker in that channel, so you do not have to explain again. If someone else mentions the Coworker in your thread, it answers them with their own permissions in a conversation of their own. It never shares one person's conversation with another.
- A quick follow-up joins your request. If you send another message to the Coworker in the channel while it is still working on your last one, it adds the message to that same request instead of starting over, and answers in the thread where you first asked. A quick follow-up gets an eyes reaction on your message so you can see it was received.
- You must be linked. If you are not, the Coworker sends you the Link account message privately, never in the channel.
- It catches up on what was said. The first time you mention the Coworker in a channel or group chat, it reads the last few messages there, so it understands what you mean by "what do you think?" When you start a new thread, it reads only what was said in the channel since you last talked to it. When you mention it in a thread you have not talked in before, it reads that thread from its first message, including what the Coworker said to the people there. When you come back to one of your threads, it reads what was said in that thread since you last wrote. It does not read the other threads of the channel. It treats everything it reads as background from other people, never as instructions from you, and it never reads a channel it has not been added to. It acts only on your own message: a request that someone else already made, and that the Coworker already answered, is not done again. These messages are saved with your conversation. In a direct message it has your conversation already.
- It answers where you asked. The reply goes under the message that started the request, in the thread where you asked.
- Short, room-friendly replies. In Slack and Teams the Coworker keeps replies short and conversational, and does not paste sensitive results from your connected accounts into a channel unless you plainly ask it to share them there.
When the Coworker posts, messages or reacts for you#
Besides answering you, a Coworker can act in Slack or Teams when you ask it to, and when it runs on a schedule for you:
- Post in a channel. Ask it to post an update in a channel and it does, but only in a channel it was invited to. It never posts anywhere it was not invited. If it is not a member it tells you so, and someone can invite it.
- Message a colleague. Ask it to tell someone something and it sends that person a direct message from the Coworker's own app. If the person has not linked their account and replies, they get the usual Link account prompt before the Coworker answers them.
- Message you. A scheduled run can send you a direct message, once you have linked your account in that app.
- React. It can add a reaction, such as an eye, a thumbs up or a check mark, to the message you sent. In Slack it can also react to an earlier message in the channel or thread when you point at it, for example "react with a thumbs up to Keith's message about lunch", as long as it can see that message. In Microsoft Teams it reacts to the message you sent or to the first message of a thread, using the reactions Teams offers.
- Do the work without replying. When you only ask for an action, such as a reaction or a message to someone else, the Coworker may do it and post nothing in the conversation, so the room is not filled with "Done". If you want a confirmation, ask for one.
- Read a thread it was in. If it needs to see what it replied earlier in a channel thread, it can read that thread. It never reads direct messages this way.
- Look back through the channel. When you point at a message it was not shown, such as your earlier message in the channel, it can look back through the channel's recent messages to find the one you mean. If it cannot find it, it tells you and asks instead of acting on a different message. Direct messages are never read this way.
It does not message people you did not ask it to, never uses @channel or @here, and does not start conversations with other bots. Its final answer to you is posted automatically; it only adds a short note along the way when that helps. In Microsoft Teams it can post in channels and chats it has already been used in.
Where your conversations live#
A conversation you have with a Coworker in Slack or Teams stays in Slack or Teams. It is not listed under Threads in Workforce Intelligence, so your thread list holds only the chats you start there. It is still saved, and any link to it opens it in Chat.
When the Coworker needs your OK#
If the Coworker needs your approval to use one of your connected accounts, it asks in the same thread: "<Coworker> is asking for your approval to use <function> in <system>." with Approve, Deny and Open in app buttons. Select one and the message changes to show your answer, for example "<Coworker> asked for your approval to use <function> in <system>. You approved this request." In a channel or group chat, where others see the message, it reads "It was approved." or "It was declined." The Coworker then carries on and replies in the same thread. See Approving a request.
Only you can answer a request made for your account. If someone else selects a button, they are told "This request is no longer available." and nothing changes. Other replies you may see: "This request was already decided." "This request is no longer waiting for an answer." "You can't answer this request." and "I couldn't record your answer. Please open the app to answer this request." This works the same in Slack and Microsoft Teams, in a direct message, a channel or a group chat. In a Slack channel or thread that answer shows only to the person who selected the button, in place; nobody else there sees it. In Microsoft Teams it arrives as a private direct message.
When the Coworker needs the app#
Some things can only be done in Workforce Intelligence: connecting an account, entering a secret value, or switching on a connector. When a Coworker's reply needs one of them, a short message follows the reply in the same thread and says what is needed, for example "I need you to connect an account in Workforce Intelligence." with an Open in Workforce Intelligence button. The button opens that conversation in Chat, where you can finish the step and the Coworker carries on.
Notifications from your Coworkers#
A Coworker can message you on its own when it has something for you. This is off until you turn it on. Open Settings and, under Chat accounts, turn on Send me notifications here for that account. What arrives, as a direct message from the Coworker's app:
| What | What the message says |
|---|---|
| A trigger's result | "<Coworker> finished a triggered run:" followed by its answer, with an Open conversation button. If the run failed, a short message says so. |
| A review request | "You have a new review request from <Coworker>" with the workflow and step when you can see them, and an Open review request button. See The review queue. |
| An approval request | "<Coworker> is asking for your approval to use <function>." with Approve, Deny and Open in app buttons, for a request raised outside your chat thread. |
A trigger can also post each run's final message to a channel or to your direct messages, with no opt-in needed, because whoever sets up the trigger chooses it; see Triggers. You can also ask a Coworker in chat to set a trigger up and report back to you or the channel; it chooses the destination for you.
Notifications go only to direct messages, never to channels, and only through the app for the Coworker the notification is about. In Microsoft Teams, send the app one message first, so Teams has a chat to deliver to, and make sure the app is added for you. Turn the switch off at any time to stop them.
Approve a request from a direct message#
A request that a Coworker raises outside your chat thread, for example in the app, reaches you as a direct message when you have notifications on. It works like the buttons in the thread:
- Select Approve or Deny on the message.
- The buttons are replaced with the answer, for example "<Coworker> asked for your approval to use <function>. You approved this request." and the Coworker carries on.
You can also answer in the app, under Waiting for your OK in Settings or on the card in the conversation; see Approving a request. Select Open in app to answer in Workforce Intelligence.
Stop using chat#
Unlink an account under Settings, Chat accounts; see Chat accounts. Your administrator ending your access also unlinks your chat accounts. You can link again at any time by messaging the app.