Front line support
Answers routine questions from your own docs, in your tone, and escalates anything angry, unusual, or outside policy straight to you.
Guide — — by Mahmoud Zalt
A function by function map of what AI can run in your business today, what needs a human check, and what should stay entirely yours.
Most advice about AI at work is either a sales pitch or a warning. Neither helps when you are sitting with a real list of jobs and trying to work out which ones you could stop doing on Monday. What you need is a map, not an opinion.
So here is the map. Nine functions that exist in almost every business, each one sorted honestly. Some are ready to hand over whole. Some can be handed over as long as you sign the last step. A few should never leave you, and knowing which is which saves you from both timidity and a bad surprise.
The unit of handover in Sistava is a function, not a task. You hire an AI Employee for a job like support, bookkeeping admin, or content, brief it once, connect the tools it needs, and give it a schedule. It then owns that function on a loop, escalating anything that falls outside what you described.
Four run end to end right now: front line support, lead intake and qualification, scheduling and reminders, and records and admin. They qualify because each one is high volume, has a describable right answer, and produces output you can check afterwards in seconds.
Answers routine questions from your own docs, in your tone, and escalates anything angry, unusual, or outside policy straight to you.
Replies to every enquiry within minutes, asks your qualifying questions, and books a call only when the lead fits the rules you set.
Offers real open slots, confirms the day before, reschedules cancellations, and fills gaps from a waiting list.
Updates the CRM, logs notes, names files, and keeps the small data hygiene current instead of letting it rot until quarter end.
Notice that none of these decide anything. They execute rules you already hold in your head, just consistently and at any hour. That is exactly why they are safe to release first, and why the time they give back is real rather than theoretical.
Three sit in the middle: marketing and content, invoicing and collections, and reporting. AI does ninety percent of the work in each, and you do the last step. The pattern is always the same: it produces, you approve, it sends.
Content is a good example. An AI Employee can build the month's plan from what actually sold, draft every post and email, and queue them. Your job shrinks to reading a list once a month and striking out what does not sound like you. Invoicing works the same way: it chases on schedule, but a write-off or a payment plan comes to you.
Two never move: people and commitments. People means hiring, managing, developing, and letting go. Commitments means pricing, contracts, refunds outside policy, delivery promises, and moving money. Both carry consequences that need a named human behind them.
An AI Employee still helps around the edges of both. It can screen applications against your criteria, prepare the interview questions, draft the contract summary, and lay out the pricing comparison. What it must not do is make the call or press the final button. Prepared by AI, decided by you, holds up over years.
Here is every function in one table. Read down the left column, find the row that matches something you did this week, and check which bucket it lands in. Most owners find four or five rows they can hand over immediately.
| Function | What AI runs today | What stays with you |
|---|---|---|
| Customer support | Routine replies, order status, FAQs, triage, first response any hour | Complaints, exceptions, anything that risks the relationship |
| Sales and leads | Instant first reply, qualifying questions, booking, follow up sequences | The price, the proposal, the negotiation, the close |
| Marketing and content | Plan, drafts, scheduling, publishing, repurposing, performance summary | Brand voice calls, claims, campaign spend decisions |
| Scheduling | Booking, confirming, rescheduling, waiting list, reminders | Your availability rules and who gets priority |
| Finance admin | Invoice sending, overdue chasing, expense sorting, a weekly money summary | Write-offs, payment plans, and every outgoing payment |
| Records and CRM | Logging, updating, deduping, tagging, keeping data current | What you choose to track and why |
| Reporting | Weekly and monthly numbers pulled, compared, and explained in plain words | What you do about the numbers |
| Operations admin | Supplier chasing, order tracking, document collection, checklists | Supplier choice and contract terms |
| People | Application screening against your criteria, interview prep, onboarding admin | Hiring, managing, developing, and letting go |
Emeka runs an online kitchenware shop with two part time packers. His week was fifty percent customer messages, mostly the same six questions about delivery times, returns, and induction compatibility. Marketing happened when he had energy left, which was rarely.
He handed over three rows of the map. Support went whole: an AI Employee answers from his shipping and returns pages, checks order status, and escalates any damaged delivery to him. Content went with a check: it plans the month from what sold last month, drafts everything, and he approves once. Records went whole: every customer interaction lands in his CRM without him touching it.
He kept two rows deliberately. He still decides discounts and never lets an automated message offer one. He still handles anyone who is genuinely upset, because that conversation either saves a customer or loses one. Support replies now land in about four minutes instead of a day, and his marketing goes out whether or not the week went well.
Take one real week, not a typical one you invent from memory. Write down what you actually did, then put each item next to a row in the table. The pattern will be obvious within ten minutes, and the first function to hand over usually picks itself by sheer repetition.
One warning about the map. The middle bucket is where people get impatient and skip the check to save a minute. Do not. The check is what keeps a small mistake small, and it costs far less time than the trust you would spend rebuilding after a bad send.
Whichever one costs you the most minutes per week among support, lead intake, scheduling, and records. Those four are the safest because a mistake is visible and cheap. Pick by volume rather than by irritation, because volume is where the hours actually hide.
It can run the mechanics without you: planning, drafting, scheduling, publishing, and reporting. You should still read the month's plan once, because marketing makes claims in your name. That single approval is the difference between output you are proud of and output you have to apologize for.
It runs the admin around your books: sorting expenses, sending invoices, chasing overdue payments, and summarizing cash weekly. It should not file returns or move money, and it does not replace an accountant. Treat it as the person who keeps the books tidy so your accountant has less to fix.
One can cover a couple of related functions, but sharper briefs produce better work. Most owners end up with one per function, the same way you would not ask a bookkeeper to also run your social feed. Start with one and add the second only once the first is quiet.
The map still applies, because the sorting rule is about the nature of the task rather than the sector. Anything repeating, describable, and checkable can be handed over. Anything that binds you or defines a relationship stays with you, whether you run a clinic, a studio, or a workshop.
Usually two to four weeks. The first week is heavy on approvals, the second gets quiet, and by the fourth you are scanning a summary rather than reading every item. If it still feels heavy after a month, the brief is too vague rather than the work being unsuitable.