An employee in your Slack, not a bot in a tab.
Sanaf joins your workspace as an app you add with one click, sits in the channels you choose, and gets mentioned like anyone else on the team. It answers in the thread, does the work inside your apps, asks for approval with a card you tap, and posts what it did where everyone can see it.
An illustration of how the conversation reads, not a transcript from a client account.
In Slack, Sanaf is one app and one employee. You install it through the normal Slack review, add it to a channel, and mention it like a colleague. It reads the thread it is in, works inside the apps you connected, replies where it was asked, and holds anything consequential behind an approval card in the same thread. Its work log, its questions and its weekly summary all land in the channel.
From install to the first job
- Step 1
Add it to Slack
One click from the console, through Slack’s own install flow. The scopes it asks for are listed on the screen, and removing the app removes its access in the same moment.
- Step 2
Invite it to a channel
Give it the channel where the work is discussed: #support, #sales, #ops. It only reads the channels it is in.
- Step 3
Mention it like a colleague
Ask it 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
When it wants to do something consequential, it posts a card saying what and why. A linked manager taps approve or hold, 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. The weekly summary arrives on the day you set.
What is different about this channel
The whole team, one employee
Anyone in the channel can hand it work. There is no seat per person, and no one has to open another tool to see what it is doing.
Scopes you can read
It asks for the Slack permissions the job needs and no more, shown before you approve them. It reads the channels it is in, not your DMs.
Your apps, its own sign-ins
The inbox, the calendar and the books are connected with sign-ins scoped to the job, never with a person’s login. Slack is where you talk to it; the work happens in the apps.
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 support overnight and which ones need a person?
@Sanaf, book the customer in this thread for Thursday morning and send the confirmation.
@Sanaf, chase the three overdue invoices and tell me who needs a call.
@Sanaf, what did you do this week?