The same employee, inside Microsoft Teams.
Most of the products like ours are Slack-first. Sanaf works in Microsoft Teams the same way it works in Slack: added to your tenant as an app, mentioned in a channel like a colleague, approving from the thread, posting what it did where the team already looks. It reaches Outlook, the calendar, SharePoint and Excel through the same scoped sign-ins as every other app.
An illustration of how the conversation reads, not a transcript from a client account.
In Microsoft Teams, Sanaf is an app your admin adds to the tenant and a colleague your team mentions in a channel. It works inside Microsoft 365 and the rest of your apps through sign-ins scoped to each job, holds consequential actions behind an approval card in the thread, and posts its work log and weekly summary to the channel the job is assigned to. Nothing about the job description, the rules or the shadow period is different from Slack.
From install to the first job
- Step 1
Add it to your tenant
An admin adds the Sanaf app to Microsoft Teams. The permissions it asks for are listed before you approve them, and removing the app removes its access.
- Step 2
Add it to a team channel
Give it the channel where the work is discussed. It reads the channels it is in and the threads it is mentioned in, and nothing else.
- Step 3
Mention it like a colleague
Ask a question, hand it a task, or reply to something it posted. It works in the thread so the context stays with the conversation.
- Step 4
Approve from the thread
A held action arrives as a card that says what it wants to do and why. A linked manager approves or holds it, and nothing happens until they do.
- Step 5
Read the log in the channel
What it did, what it used, and what is waiting on you, posted where the team already looks.
What is different about this channel
Microsoft 365, through scoped sign-ins
Outlook, the calendar, SharePoint and Excel are in the catalog, connected one at a time with a sign-in scoped to the job. What it may do in each is set per kind of action.
One employee for the whole tenant
Anyone in the channel can hand it work. There is no seat per person and no separate tool for the team to learn.
The same rules as everywhere
The job description, the approval rules, the shadow period and the work log are the same in Teams as in Slack. Where you talk to it does not change what it may do.
Consequential actions stop at a card, and wait for you
This is what a held action looks like in the channel. Sanaf says what it wants to do and why, and nothing happens until a linked manager answers.
An illustration of how the conversation reads, not a transcript from a client account.
Ask it the way you would ask a colleague
@Sanaf, what came into the shared inbox overnight and which ones need a person?
@Sanaf, put the site visit from this thread in the calendar for Tuesday and send the confirmation.
@Sanaf, update the tracking sheet from this thread and tell me what is still outstanding.
@Sanaf, what did you do this week?