Real output, not a summary
A file in the channel, a booking on the calendar, a reply already sent. The work arrives done, not described.
One Sanaf, on every channel
One employee that runs a team. Sanaf hands each job to an agent that knows it, brings you one answer and keeps a record of everything. You pay for the work, not the seat.
Example, shown in Slack: in #accounts, You messages @Sanaf which accounts should I be worried about this week?. Sanaf, an AI employee, replies: Three have gone quiet. Two do this every August and always come back. Millar Group is the one worth your time: no reply since the 12th, and the check-in that was due last week never happened. Completed: Reviewed 34 accounts this morning. Flagged 3 that have gone quiet. Drafted the check-in Millar Group is owed. Waiting on a person: Sending the check-in to Millar Group.
An illustration of how the conversation reads, not a transcript from a client account. Slack, Microsoft Teams and Discord are products of their own owners. This is our workspace, drawn to look like theirs.
A file in the channel, a booking on the calendar, a reply already sent. The work arrives done, not described.
It works inside the software you already run, so one request can touch the books, the calendar, and the inbox at once.
Enquiries answered at nine at night, reminders sent before you open. In the channel before you ask.
Correct it once and it remembers: your tone, your templates, who gets copied in, what waits for you.
An illustration of how the conversation reads, not a transcript from a client account.
Someone in Slack asks Sanaf for the week. It says "On it.", works through the connected apps, and posts the report back in the thread. Then the office empties and it keeps going, asking before anything leaves the business.
Sanaf is the one you talk to. Behind it, every job you hand over is done by an agent with its own job description, its own logins and its own rules for each kind of action, and everything the team does lands in one record. That is what makes it a hire rather than a tool.
The agent on the support inbox knows what a support manager does. The one on the invoices knows what a bookkeeper does. Thirty five jobs are written; you can write the thirty sixth.
Each agent reaches only the apps you granted it, at the narrowest permission that lets its work happen. Revoke one without touching the rest of the team.
Booking without asking, but never sending money without you. You decide per kind of action for each agent, and either can be told never.
What did the team do on Tuesday is a question with an exact answer: who read what, who sent what, and what was asked of you first, across every agent.
Credits pay for what gets done, not for how many agents you have. Adding a third costs nothing until it does something.
A customer one agent met in the support inbox is a customer another recognises when it chases the invoice. One team, one memory, instead of five tools that have never met.
Sanaf works the same way in Slack and Microsoft Teams: one app, one name to mention, and the team behind it. You can see the whole team, and who reports to whom, on the Orgs screen in the console.
Every department on the roster is a set of agents Sanaf can hand work to. When a job crosses from one to another, Sanaf carries it, and you read one thread instead of chasing three.
You have tried the apps. They hand you a plan and wait. An employee does the thing and posts the result.
Tells you which health metrics to track and how to build the dashboard.
Drafts a follow-up email for you to personalise and send seven times.
Explains how to word a polite reminder for a late account.
Suggests when to ask a customer for a review and what to say.
This compares how the two are used, not a specific clientโs measured results. What your AI employee takes over depends on your business, and we will tell you honestly what to expect before you commit to anything.
No new app, no dashboard to check. Your AI employee shows up in the chat your team already has open, and you talk to it the way you would talk to anyone on the payroll. Ask it something at six in the morning and it answers at six in the morning.
@Sanaf anything I should worry about in the accounts this week?
Three have gone quiet. Two are seasonal and always do this in August. Millar Group is the one I would look at: nobody has replied to us since the 12th, and the check-in that was due last week has not happened.
Get me a call with them and send over what I need.
Asked them for a time on Thursday or Friday. Their notes are attached: what we agreed at renewal, what is still open on our side, and the two things they asked for last quarter that nobody came back on.
An illustration of how the conversation reads, not a transcript from a client account.
The full customer success manager job or every job it can take
@Sanaf turn my site notes and the photos into a quote for the Fletcher job.
Quote drafted from your rate card: labour, materials, and the access equipment they will need for the rear elevation. I have left the price line blank because the roof pitch is not in your notes and I am not going to guess at it.
Pitch is steep, add the access surcharge.
Added and recalculated, and the opportunity is updated in your pipeline so it does not sit as a site visit with nothing after it. The quote is ready to send once you approve the total.
An illustration of how the conversation reads, not a transcript from a client account.
@Sanaf anything back on last week's quotes?
Seven quotes went out, and I have followed up on all seven. Two booked. Three asked for time and gave me a date to come back. One went to a competitor and told me why, which I have written down. One has not answered three times, so I have stopped rather than keep chasing.
Why did we lose the one?
Timing, not price. They needed it done before a house move and we could not start until the following month.
An illustration of how the conversation reads, not a transcript from a client account.
The full lead follow-up specialist job or every job it can take
@Sanaf how did this week go for reviews?
Eleven jobs finished, eleven asked the same evening they were done. Six left a review. One customer replied to the ask saying the tech was late, so I did not push for a review and flagged it to you instead.
Draft a reply to the four-star one.
Drafted, waiting on you. It thanks them by name, names the thing they praised, and does not argue with the criticism.
An illustration of how the conversation reads, not a transcript from a client account.
Type what you want the way you would type it to a colleague. No commands to memorize, no special words, no training course for your team.
Anyone in the channel can ask it for something, and you decide who is allowed to ask for what.
It reads and answers day or night. Nobody has to be awake for the work to keep moving.
When something is unusual, awkward, or above its pay grade, it stops and tags whoever should handle it.
Begin where the busywork hurts most, then hand it the next job. Same employee, same memory, same credits, so a longer job list is a longer week of work and not a bigger bill.
Sanaf as your customer success manager
Watches every account, and tells you which one to call.
Thirty five jobs it already knows. Give it one today and hand it the next whenever you like. See every job
Give Sanaf its first job, it learns how your business actually runs, and you manage the work. There is nothing for you to build and nothing for your team to install.
Tell it where the busywork piles up: the accounts, the follow-ups, the books. Sanaf already knows thirty five jobs, and if you can write a short job description for another one, it can take that too.
It learns your services, hours, booking rules, and tone, and gets wired into the calendar, inbox, and software you already run. Nothing for your team to install.
Every day you get a list of what was answered, booked, and chased, and what is waiting on you. Anything consequential stops and asks first.
It asks before anything it cannot undo, and it pushes back when you are about to make a mistake. It proposes, you decide. Every consequential action waits on a person.
An illustration of how the conversation reads, not a transcript from a client account.
You do not move anything, cancel anything, or teach your team a new system. Your AI employee signs in to the apps you already run, the same way a new hire would on their first day, and works inside them from there.
1,500+
apps it can sign in to
23,000+
ready-made tools inside them
84
categories of software
You approve the accounts it should reach, we do the setup, and it starts working in them. Nothing to install on anyoneโs computer.
Your customer list, calendar, and books stay exactly where they are. Your team carries on in the same screens they used yesterday.
Access is yours to grant and yours to take back, one app at a time, and everything it does in them is written down where you can see it.
A few of the ones owners name most often are below, and the whole list is one search away. If you run something that is not on it, tell us and we will check it before you commit to anything.
Follow along instead. Field notes on what an AI employee can take off a team, what it costs to run, and where it still needs a person.