Try it free
Product
Everything you can hand overSee every feature →
Set it up by talkingJust talkTell it what happened. It does the work.Set up by talkingIt arranges itself from a conversation.Your kind of workIt takes the shape of your work.Your wordsYour words, not ours.Your processPipelines and stages you design.Your questionsThe same questions, asked the same way.
Messages and answersInboxEvery message that reaches you, answered.Hand-offWhat it can't answer comes to you, with the reason.KnowledgeIt knows how you work.Web researchIt gathers from the web.
Promises and follow-upAfter the callSay it once, after the call.PromisesEvery promise, on its date.Going quietIt notices what's going quiet.AutomationsRoutines that run themselves.
Records and numbersRecordsEveryone's whole story, in one look.ImportBring what you already have.Products & quotesWhat you sell, and what you quoted.DashboardsYour numbers, from day one.AskAsk your work anything.
ControlTeamYour team, each with their part.ApprovalsJudgement waits for you.Reasons & sourcesNothing made up. Everything with its reason.
What’s new →
Use cases
What Felesh looks like for youAll use cases →
For you aloneYour own daysA business ownerA creatorSomeone who decides
TeamsA recruiterA project managerA product managerA support deskA B2B sales team
BusinessesA local grocery shopA training instituteAn online shopA small businessA wholesalerA recruitment agencyAn accounting firmA law officeA local clinicA dental clinic
Large organisationsAn enterpriseA hospitalA holding group office
PricingTrust
Resources
BlogGuidesChangelogAcademyAbout
Log in

How can I step away from the business and still know what's going on?

You cannot hand over the answering-for-it, but you can keep the work known. Here is how to set up before you leave, and what the morning back looks like.

6 min read · · The Felesh team

The short answer

Can you run a business without being there? Not entirely. Customers still expect a person to answer for the work, and that person is you, or someone you have named to cover.

What you can do is step away and still know where things stand. That depends on one habit and a few things set up before you go. The habit is writing down what happened. What you set up decides what waits for you and what you can ask about when you are back.

Felesh does not run the business while you are away. It keeps the business known, and it does the work you approve.

Fig. 1 Before you leave you write one sentence per open conversation; on your return the open items and the Needs you queue are waiting.

What do you need to know while you are away?

Not everything. If you try to follow every message from a beach or a hospital corridor, you have not really stepped away.

Most owners want three things. Has something gone wrong? Is a customer waiting on me? Is a promise coming due that someone has to keep?

Those are questions about the work. They are not questions about what each person did on which day. The people who cover for you should not feel watched, and nothing here is built to watch them. The question is whether the work is moving, and which customers are waiting.

What happens to customer messages while you are gone?

This is the part that worries people most, because customers do not stop writing.

Messages from your website chat, Instagram, WhatsApp and Telegram arrive in one inbox. Felesh answers from what you have taught it: documents you uploaded and instructions you wrote. A customer asks how long a job takes, or whether you cover their area.

When Felesh cannot answer, it does not guess. The message goes to “Needs you”, with the reason it could not answer. No notice is sent to you, so no phone buzzes on your holiday. The message waits in the queue until you or the person covering for you looks at it.

If a person joins a conversation, Felesh stays quiet. Your cover is not talked over.

How do you set it up before you go?

Here is a concrete version, for someone leaving for two weeks.

  1. Write down what happened. For each open conversation, type one sentence about where it stands. Felesh drafts a note, the promise with its date if you gave one, and the next step. Each draft shows its reason and waits for your yes (“Review draft”). Read them and say yes to the ones that are right.
  2. Add tasks for what must happen while you are away. A task is added directly, with no approval step.
  3. Teach it what customers ask. Upload your terms, your notes on how a job works. Write instructions for the things you always say. The answers can only be as good as what you put in.
  4. Bring in your contacts. If your customers live in a spreadsheet, bring them in from one Excel or CSV file. You see the column mapping and the rows before anything is saved.

The first step is the one that matters. Whatever you write down, you will be able to ask about later.

You can also build one routine once, for example: each morning, find what is overdue and what has gone quiet and tell me. It runs on the schedule you set, and the notice appears in the panel for people you have invited into your workspace, never by email or SMS and never to customers. It exists only if you set it up; by default nothing is sent.

What does the morning back look like?

Think of a morning in January, or after a summer break. The usual dread is the inbox, with a hundred threads and no idea which of them matter.

Here you begin differently. You ask Felesh in your own words. What is waiting for me? Which customers have I not heard from? What did I promise that falls due this week? It answers from your own records.

Then you look at the “Needs you” queue. Each message there carries the reason it was handed over. A customer wanted a discount you had not set. Another wrote about something your documents did not cover. These are the judgement calls, and they were always yours.

You will also see any drafts still waiting for your yes.

The aim is to see the shape of the work in a few minutes instead of an afternoon. Then you can decide what to pick up first. A quiet customer is worth noticing. It is the customer who has gone quiet, not the person who covered for you, that you look at.

What will Felesh not know?

This is where the limits matter.

Felesh knows what is done on Felesh. It knows the files you import, and what you upload or teach it. It does not read your mail or your drives, and it does not connect to other tools.

So if a call took place and nobody typed a sentence about it, Felesh does not know it happened. If the person covering for you agreed something by phone and wrote nothing down, that promise is not in your records. The picture on your return is as complete as the habit behind it.

This is why the one sentence after the work matters. It takes a short time to type, and it is the difference between knowing where you stand and guessing. If you have people covering for you, agree this with them before you leave. Ask them to say what happened, in a sentence, after each piece of work.

It is also why the answer to the original question is modest. You can be away and still know what is going on, as far as the work has been written down. Felesh does not take over the decisions, and it does not make promises in your name. They are waiting when you come back.

Before you go

Start with the conversations that are open today: type one sentence about each, and use ask to see how it answers from your own records.

Next question How do I get one answer from three people instead of three answers? Keep one record that everyone reads from and writes to, with the reason beside each entry. Here is how to set that up, and what it looks like in Felesh.