Most advice on AI and productivity stops at “use an AI assistant”. It skips the hard part: which task do you give it first?
Pick a task that is too complex and you lose a month. Pick one that is repeatable and low-risk, and you get hours back in the first week. Here is how I decide.
Step 1: List a week of interruptions
For five working days, write down every time you were pulled away from what you were doing: a call, an email that needed the same answer as last time, a quote to chase, a message about opening hours.
Do not analyse yet. Just collect.
A few habits make the list more honest. Keep a note open on your phone rather than relying on memory at the end of the day. Write the interruption in a few words, not a paragraph. Add the time, because patterns by hour often show up later. And do not skip the small ones: a thirty-second question asked fifteen times in a week is a better candidate than a single long call.
Step 2: Score each one on three questions
| Question | Good sign for hand-off |
|---|---|
| Does it happen often, in nearly the same form? | Yes: the pattern is easy to describe |
| If it goes wrong, is the damage small and recoverable? | Yes: you can correct it afterwards |
| Can you write down the right answer in a page? | Yes: hours, area, services, rules |
Three yes answers make a candidate. A single no on the second question (damage) is a reason to keep a human in charge.
A scoring example, with generic tasks
The list below is an illustration of the method. The tasks are generic and the answers are mine, not data from a real business. Yours will differ, and that is the point of scoring your own week.
| Interruption | Often, same form? | Small, recoverable damage? | Answer fits on a page? | Decision |
|---|---|---|---|---|
| “Are you open on Saturday?” | Yes | Yes | Yes | Hand off |
| A new customer wants an appointment | Yes | Yes, you can read the recap | Yes, if rules are clear | Hand off, read the recaps |
| A customer asks for a price on a custom job | Sometimes | No | No | Keep |
| A customer is angry about a past job | Rarely | No | No | Keep |
| A supplier confirms a delivery | Sometimes | Yes | Yes | Possible, but not the first one |
Two or three tasks usually come out on top. Take the one that interrupts you most, not the one that looks most impressive.
What usually scores well
- Answering the phone when you cannot: frequent, same few questions, and the recap tells you exactly what happened.
- Booking appointments: the rules fit on a page (free slots, business hours).
- Answering “when are you open, where are you”: the answer never changes.
What usually does not
- Negotiating a price or a complaint.
- Anything where a wrong answer costs a customer.
- Judgment calls that depend on knowing the person.
Step 3: Write down what “done well” means
Before you hand anything off, describe the good result in one or two sentences. Without it, you cannot tell whether the hand-off worked.
| Task | “Done well” looks like | How you check it |
|---|---|---|
| Answering calls | Every call has a name, a number and a clear reason | Read the recap email |
| Booking appointments | The slot is free, correct and in the calendar | Compare the calendar with the recap |
| Giving opening hours | The caller got the right hours, nothing invented | Read the transcript |
If you cannot describe what “done well” means, the task is probably not ready to be handed off.
Why I start with the phone
I build Atlas, so I am biased, but the reasoning is simple. A missed call is the interruption you cannot postpone, and it is also the one with a short, checkable script. Atlas picks up, qualifies the call, checks your Google Calendar, books the appointment, and emails you a summary with the transcript.
The recap is what makes it safe to hand off: you can read every call. If Atlas handled one badly, the email subject starts with [PROBLEME].
What it will not do: send SMS, transfer calls, diagnose or promise an arrival time. It speaks English and French only. For the full call walk-through, read How AI Handles Inbound Calls.
What to read during the first week
Handing off a task is not the same as forgetting it. For the first week, read the results closely.
- Read every recap. Do not skim: look for a missing number, a vague reason, or a request the assistant did not understand.
- Open a few transcripts. The transcript shows how the conversation really went, which a summary can hide.
- Compare the calendar with the recaps. Each booked slot should match what the caller was told.
- Note what keeps coming back. A question that the assistant cannot answer might belong in the profile.
- Test a call it should refuse. Ask for something outside its remit, such as a diagnosis, and check that it does not invent an answer.
After that, a quick look at the recaps each day is usually enough. All calls also stay in your customer dashboard as long as your subscription is active.
If you hand off email, know the rules
Outreach is another common task to delegate, and it has legal rules. The FTC’s CAN-SPAM Act compliance guide says the law covers “any electronic mail message the primary purpose of which is the commercial advertisement or promotion of a commercial product or service”, adds that “the law makes no exception for business-to-business email”, and requires that opt-out requests be honored “within 10 business days”. Whoever sends the message, you are responsible for it.
A 30-day test
- Choose one task from your list.
- Write down what “done well” means: booked, answered, forwarded.
- Run it for a week, then read every result.
- Keep it, adjust it, or drop it. Only then pick the next one.
Mistakes that waste the first month
- Starting with the hardest task. A complex hand-off teaches you little and can cost you a customer.
- Handing off several tasks at once. If something goes wrong, you will not know which one caused it.
- Not defining success. Without a clear result, every outcome looks acceptable.
- Not reading the output. The point of a checkable task is that you check it.
- Expecting a CRM to be set up from day one. It is possible as an option, quoted separately, but it is not part of the starting offer.
What it costs
Atlas costs $49/month for the first 20 customers (then $99/month) plus $0.25 per call minute, rounded up to the next minute. The trial lasts 7 days with 100 free minutes, once. Minutes beyond them are billed, even during the trial. Details on the pricing page.
| Billed minutes in the month | Launch price ($49 + minutes) | Regular price ($99 + minutes) |
|---|---|---|
| 50 | $61.50 | $111.50 |
| 100 | $74.00 | $124.00 |
| 200 | $99.00 | $149.00 |
| 300 | $124.00 | $174.00 |
Each call is rounded up, so a 70-second call counts as 2 minutes. To estimate your month, count the calls you would want answered each week, multiply by their average length rounded up, then by about four.
Related: 24/7 phone coverage without hiring and Integrating an AI Virtual Assistant into Your Business.
Try Atlas
Discover Atlas · See pricing · Start the 7-day free trial
If you would rather talk first, email me at [email protected] or call our US line at +1 302 947 8583.