You are looking for a feature rather than a task
Feature pages explain what a capability does and what it asks you to decide; help explains how to set it up in your business. If you have not chosen yet, start with the feature page.
Find instructions to set up your receptionist, follow a request or take over. If you are choosing a plan, start with the questions before signing up.
Questions before getting started11 results
Your first settings, your phone line and the answers to give.
Ask your receptionist, manage appointments and handle messages.
Connect your software and understand an action that needs your attention.
Usage, team access, exports and ending your subscription.
Every article matches a task an owner does alone: point the line, write the instructions, have appointments taken, connect the software, understand what is counted, grant access, cancel. They start with the outcome, not with an explanation.
They are written in words, without screenshots. That is not laziness: a picture of a screen that did not come from the real application starts lying at the first change, and we would rather describe what you see.
If your question is not here, the end of each article says where to write — and what to put in the message to get a real answer the first time.
None of these tasks calls for technical knowledge or for someone else's help.
Articles are filed by task, not by feature. «My calls are not arriving» and «I want to change the hours» are not in the same place, even though both touch the phone setup.
Every article names the screen: Phone for the number and forwarding, Knowledge for what the receptionist may say, Calendar for appointments, Connections for software, Subscription for what is counted, Team for access.
The «My receptionist» screen answers a question about your own business from your real data, with the date of each piece of information used. For «what happened last night», that beats an article.
Your business name, the screen or page concerned, and the time the problem happened. With those three, the answer usually fits in one exchange.
Each one starts with the outcome, because an owner opening a help page first wants to know whether they are in the right place. Then come the prerequisites in plain words, the steps, what happens behind them, the edge cases, and what to do when the procedure fails.
They describe screens that exist, named as they appear in your workspace. When an action is not possible for you — because a piece of software does not permit it, or because a role gives no right to it — the article says so rather than letting the procedure stop without explanation.
To get going: getting started, then numbers and forwarding, then voice and instructions. Those three are enough for a real call to be answered properly, and they take about an hour.
After that, it depends on what you want to hand over: appointments if you sell slots, written channels if your customers write more than they call, connections if a piece of software has to stay the reference. Billing, team and incidents are read when the question comes up, not before.
Feature pages explain what a capability does and what it asks you to decide; help explains how to set it up in your business. If you have not chosen yet, start with the feature page.
«Who called last night», «who is waiting for a call back»: those are data questions, not help questions. The «My receptionist» screen answers them from your real calls, with the date of each piece of information used.
A screen missing from your menu matches a capability your offer does not include, or a role that has no right to it. The Subscription screen says what your offer includes, and the Team screen what your role allows.
The guides explain the why and compare the possible setups, with their sources and their date. Help articles assume the choice is made and get you finished.
Feature pages explain what a capability does and what it asks of you; help explains how to set it up in your business. If you want to understand before deciding, start with the feature page.
A screen missing from your menu matches a capability your offer does not include, or a role that has no right to it. The Subscription screen says what your offer includes, and the Team screen says what your role allows.
An instruction takes effect when it is published, not when it is written. Check on the Knowledge screen that the latest version is the one in force.
The questions that come up before opening an article.
With «Getting started». It gives the five steps in order — describe the business, write the instructions, choose the voice, publish and forward the line, then check with a real call.
No. None of the tasks described here needs an access key, programming, or any intervention from us. There is no setup fee either.
Because a picture that did not come from the real application starts lying at the first change. The steps are described in words, and they name the screens as they are called in your workspace.
Your business name, the screen or page concerned, and the time the problem happened. With those three, the answer usually fits in one exchange.
When your calls stop arriving, start by removing forwarding from your handset: the incidents article explains why that comes first.
Yes. Each article exists in French and in English, and the screens in your workspace follow the language you chose.
From the first hookup to cancelling.