A job description for every agent
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.
You have tried the AI tools. The work is still there. An AI employee is different: it lives in your inbox, your calendar, and the Slack or Teams your team already uses, and it does the work. Enquiries answered. Leads followed up. Jobs booked. Invoices chased. Around the clock, trained on how your business actually runs, supervised by you.
An illustration of how the conversation reads, not a transcript from a client account.
Work in. Work done. You stay the boss.
“Hi, do you have anything tomorrow for an AC tune-up? And what do I need to have ready?”
Booked: tomorrow’s first opening
Confirmation sent to the caller. Call summary logged for your team.
These describe how your AI employee is designed to work, the coverage it adds and the control you keep, not a client performance guarantee. It watches and drafts before it sends anything, and the work log shows what it actually answered, booked, and handed off. No invented numbers.
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.
Whatever the job, Sanaf reports the same way: what it did, what it produced, and what is waiting on you.
An illustration of how the conversation reads, not a transcript from a client account.
Sanaf arrives knowing these jobs. Give it the one where the busywork piles up, put it in your Slack or Teams, and it starts. Hand it the next job whenever the next pile appears: it is the same employee, with the same memory and the same credits, so a longer job list is a longer week of work and not a bigger bill.
The front door of your business: the inbox, the chat, the calendar, and your reputation.
Owns one lane
Account health, check-ins, renewals
Where it stops: When a customer is unhappy, when the conversation turns to price or the terms of a contract, or when keeping an account needs a promise only the owner can make, you say so plainly and bring in a person with the whole history attached.
Runs a function
Customer support & issue resolution
Where it stops: Refunds, exceptions to policy, and any customer who is genuinely unhappy go straight to a person, with a short summary of what happened and what has already been tried.
Owns one lane
Appointments, calendars & reminders
Where it stops: Anything that would double-book a crew, break a rule you set, or squeeze an unrealistic drive time gets flagged to a person before it lands on the calendar.
Owns one lane
Reviews & online reputation
Where it stops: You draft every public response and wait for your client’s approval before anything is posted under their name. A review that alleges something serious goes to them immediately, unanswered.
Owns one lane
New-customer setup, training & first weeks
Where it stops: A customer who is frustrated, a request to change what was sold, or a question the materials do not answer goes to a person with everything you have already done attached. You never guess at a setup step.
Everything between a stranger and a signed job: prospecting, qualifying, quoting, and following up.
Owns one lane
Prospecting & outbound sales
Where it stops: You never send outreach whose shape has not been approved, and every interested reply is handed to a person with the full thread and the research behind it.
Owns one lane
Qualify, score & route leads
Where it stops: You score and route, you do not turn anyone away. A lead you cannot read confidently still reaches a person, flagged as unclear rather than silently binned.
Runs a function
Quotes, proposals & sales pipeline
Where it stops: Every quote and proposal is drafted for a person to price, check, and send. You prepare the work, a person signs off on the number.
Owns one lane
Follow-ups & lead reactivation
Where it stops: Anything that needs a concession, a discount, or a change to the scope stops with you and goes to a person with the customer’s exact words.
Owns one lane
CRM hygiene, pipeline reports & lead routing
Where it stops: You tidy and report; you do not change a deal’s value, stage or owner without the rep or the owner agreeing, and merging two records that might be two real customers is always a person’s call.
The work that keeps your name in front of customers instead of stuck in a to-do list.
Runs a function
Campaigns, promotions & marketing
Where it stops: You plan and draft. Budgets, offers, and anything going out under your client’s name are theirs to approve before a single message sends.
Owns one lane
Social content & engagement
Where it stops: Posts are drafted for your approval, and anything a commenter raises that sounds like a real complaint goes to a person instead of getting a public reply.
Owns one lane
Content creation & distribution
Where it stops: Every piece is drafted for review. You never publish a claim about pricing, guarantees, or results without a person confirming it is true.
Owns one lane
Tracking, automations & the marketing stack
Where it stops: You change nothing on a live page, a live automation or an ad account without a person approving the change and seeing what it will do. Anything that touches billing, a domain, or customer data beyond the marketing tools goes to a person first.
Owns one lane
Search rankings, site health & content briefs
Where it stops: You draft and recommend. No page goes live and no change touches the site until a person approves it, and you never promise a ranking or invent a number to justify a change.
The engine room: workflows, projects, vendors, stock, and the paperwork that keeps you compliant.
Runs a function
Business workflows & operations
Where it stops: You coordinate the routine and escalate the rest. Anything that changes how the business runs is proposed to a person, never enacted on your own.
Owns one lane
Projects, deadlines & task coordination
Where it stops: You raise the risk, a person makes the call. Rescoping, moving a client date, or pulling someone off a job is always a person’s decision.
Owns one lane
Vendors, purchasing & orders
Where it stops: You prepare orders and comparisons. A person approves every purchase, and any vendor dispute goes straight to them.
Owns one lane
Inventory, stock & reorder management
Where it stops: You recommend, a person orders. Anything that looks like shrinkage or a count that does not reconcile is flagged to a person rather than quietly corrected.
Owns one lane
Policies, documentation & compliance workflows
Where it stops: You organize and remind, you do not give legal or regulatory advice. Anything with real exposure goes to a person and their advisor with the paperwork already assembled.
Owns one lane
Contracts, matter files & legal admin
Where it stops: You are an assistant, not a lawyer, and you say so. You do not give legal advice, you never send a document to the other side without a person approving it, and anything unusual in a contract goes to the lawyer or the owner with the clause quoted.
Owns one lane
Orders, fulfillment status & customer updates
Where it stops: A refund, a discount, a return outside the policy you were given or an order that looks like fraud goes to a person with the order history attached. You update and inform; you do not make exceptions on your own.
Money in, money out, and the daily admin nobody wants but everybody needs.
Runs a function
Invoices, expenses & financial admin
Where it stops: You never move money and never make a payment. Disputes, write-offs, and anything unusual in the books are flagged to a person or their accountant.
Owns one lane
Administrative & back-office work
Where it stops: Anything that reads as a customer issue, a bill, or a decision gets routed to the right person instead of filed away.
Owns one lane
KPIs, analytics & insights
Where it stops: You report what the numbers say and where you are unsure. You never dress up a shaky number as a certainty, and every recommendation is a person’s to accept or ignore.
Owns one lane
Data entry, record cleanup & imports
Where it stops: You enter and tidy, you do not decide. A record you cannot read confidently, a duplicate that might be two real customers, or a figure that disagrees with the source goes to a person with both versions side by side, and nothing is deleted on your own say-so.
Owns one lane
Supplier bills, approvals & payment runs
Where it stops: You never pay anything and never approve a bill. Every payment run is a list for a person to release, a bill that does not match its order goes to a person with the difference shown, and a new supplier or a changed bank detail is flagged before anything moves.
Owns one lane
Categorizing, reconciling & month-end close
Where it stops: You keep the books, you do not give tax or accounting advice. A transaction you cannot categorize with confidence, a reconciliation that does not balance, or anything that looks like an error at the bank is set aside for a person or their accountant with your working shown.
Hiring, HR admin, internal support, company knowledge, and the executive desk.
Runs a function
Recruiting & hiring coordination
Where it stops: You organize and communicate, you do not decide who gets hired. Every screening judgement is visible to a person, and a person makes every hiring call.
Owns one lane
Employee administration & HR workflows
Where it stops: You do not handle grievances, discipline, pay decisions, or anything sensitive. Those go directly to a person, and you say so to the employee.
Owns one lane
Internal employee IT support
Where it stops: Anything touching security, billing, or a system you cannot safely reach becomes a ticket for a person, with everything already tried written up.
Owns one lane
Company knowledge, SOPs & documentation
Where it stops: You never invent an answer. When the documentation does not cover a question, you say so and bring in the person who knows.
Owns one lane
Owner/executive support
Where it stops: You draft on a person’s behalf and send nothing under their name without approval. Anything personal, sensitive, or high stakes waits for them.
Owns one lane
Research, briefs & due diligence
Where it stops: You separate what you found from what you think, and you say when the sources disagree or run out. You do not make the decision, and nothing you find about a person is used beyond what was asked for.
The job that runs all the other jobs it holds, and reports to you.
Runs the week
One desk across every job it holds
Where it stops: You propose and coordinate, you do not overrule anyone. Priorities, spending, and anything that changes direction go to a person as a recommendation with the reasoning attached.
These are the jobs owners hand over most, not the only jobs Sanaf can take. If the work is repetitive, follows rules you could write down, and lives in systems you already use, it is probably a job it can own. Tell us what it is and we will give you a straight answer either way.
We scope the first job with you before anything goes live, and we tell you honestly when a job is not worth handing over yet. You stay the manager: Sanaf logs what it does, and anything consequential waits for a person.
Not a dashboard, not a prompt box. The same chat your team already has open, with work handed back when it needs a person.
@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.
Every job on the list has an example like this.
Every one of these is a moment where a customer, a booking, or a payment quietly slips away, and no tool has taken it off your plate. Sanaf exists to finish them.
No AI tool has ever worked your support inbox. Questions sit for days while your team is with a customer, and the slow ones turn into bad reviews.
Your AI employee works the queue continuously, nights and weekends included: answers the routine questions accurately, keeps every conversation moving, and pulls a person in the moment a customer needs one.
The tools can draft a reply to a new lead. Someone still has to notice the lead, finish the draft, send it, and log it, and by then the lead has booked elsewhere.
It replies the moment an enquiry lands, asks the qualifying questions your best salesperson would, logs every answer, and hands the hottest leads to your team first.
Booking one appointment still takes a week of back-and-forth.
It books straight into your real calendar openings, sends confirmations and reminders, and handles reschedules, no back-and-forth, no double-booking.
Your team still answers the same twenty questions every single day.
Trained on your services, hours, booking rules, and tone of voice, it handles the repetitive questions accurately, so your people stop repeating themselves.
The tools can write the awkward payment-reminder email. It still sits unsent, because chasing money is nobody’s favorite job.
It drafts invoices on schedule, actually sends the reminders, and follows up on overdue payments politely and persistently, flagging anything unusual for you.
The CRM is stale and follow-ups slip through the cracks. A summary of the mess is not the same as someone cleaning it up.
Every conversation, booking, and lead is logged as it happens. Your records stay current, and a daily work log shows you exactly what got done.
The difference is who finishes the job. A tool waits for someone to drive it. A hire owns the outcome. Follow the same five moments and watch where each one ends up.
This compares where the work ends up with tools you drive yourself versus an AI employee on shift, not a specific client’s measured results. Your numbers depend on your volume, and we will tell you honestly what to expect before you commit to anything.
You hire it the way you would a person: give it its first job, put it in your Slack or Teams, manage it with full visibility, and hand it more as it earns your trust. There is nothing for you to build.
Sanaf already knows thirty five jobs. Choose the one where the busywork piles up, the front desk, lead follow-up, the books, and it starts there. Free, and no card.
Add it to the channel your team already uses, then connect the accounts it needs for the job: your calendar, your inbox, your books. One click each, scoped to the job it is for.
It handles the routine work end to end and logs everything it does. Anything consequential, an unusual request, an upset customer, a judgment call, pauses and waits for a person.
Give it feedback the way you would a new team member. It learns from corrections, takes on more of the job as it proves itself, and when the next pile of busywork appears you hand it that job too.
Want to know what it costs before you start? See the pricing.
Most AI employee products are one shared assistant your whole team talks to. Sanaf is a hire: a job description for every job, logins scoped to each, rules you set per action, a trial period, and a memory you can question. These are the mechanics, not promises.
Sanaf holds a written job description for every job you hand it: what it owns day to day, what it hands to a person, which apps it works in. Thirty five are written before you start, and the thirty sixth is yours to write. It is a colleague with a role, not an assistant waiting for a prompt.
Elsewhere: One assistant shared by the whole workspace, wearing every hat at once with no job to be measured against.
Every app connection is granted for a job and scoped to the narrowest permission that lets that work happen. Revoke a single connection without touching anything else, and see at a glance which job each one serves.
Elsewhere: Integrations connected once and shared across everything the assistant might ever do.
For every kind of action, you choose: do it, ask me first, or never. Add conditions like an amount, after hours, or a new contact. Unattended work runs one notch stricter than work you asked for in the moment, and every decision carries a one-line reason. A safety check proves the rules hold before it goes near a customer.
Elsewhere: A single "ask before anything irreversible" setting, or an always-approve button per tool.
Sanaf drafts first and asks before anything it cannot undo. You review what it did, then allow one kind of action at a time, with a report of what it did and what you turned down. Every change is your explicit call and is written down.
Elsewhere: Live on day one, learning by making mistakes in front of your customers.
Overnight it reviews the day and proposes changes to its own instructions, each one citing the moments that prompted it. You accept or reject. Accepting creates a new version; rejecting is remembered so it stops asking. It cannot change itself without you.
Elsewhere: Notes the assistant writes to itself that nobody reviews.
Ask "why do you think that?" and it answers with when it learned the fact, where, and what it replaced. Correct a fact inline and the old one keeps its history. Nothing it acts on is untraceable.
Elsewhere: A memory you can reset but cannot inspect.
Every turn is a replayable log: what it read, what it called, what it asked, what it sent. Your manager view shows it live while it works and keeps the timeline afterward, so "what did Sanaf do on Tuesday?" has an exact answer.
Elsewhere: A chat transcript and a credits total.
There is no seat fee and no per-job fee. You pay for the work Sanaf actually does, and the work log shows you what each piece of it used, so handing it another job costs nothing until that job produces something.
Elsewhere: A seat fee on top of credits whose price is never explained.
Sign up, give Sanaf its first job, and add it to your Slack. There is no demo gate, no waitlist and no onboarding queue between you and a colleague doing real work, and the $120 of credits you start with is enough to find out on your own jobs.
Elsewhere: A demo call, a trial that starts when sales says it does, and a setup checklist you complete yourself anyway.