Your business closes at six. Your customers don’t stop at six. After hours they write on your website chat, email you, text the number on your van, and call. Each of those lands in a different place, and most of it waits until someone gets in the next morning. By then some of those people have booked with whoever answered first. The fix is one agent that answers every channel with the same memory, books what can be booked, wakes someone up only for what’s urgent, and leaves your team one inbox showing everything that happened overnight.
How the work runs today: one night at a three-location business
Take a three-location home-services company and follow one ordinary Tuesday night.
| Time | Channel | Lands in | What they wanted | What happened |
|---|---|---|---|---|
| 6:42pm | Web chat | An email alias nobody checks after 5 | “Do you do Saturday appointments?” | The widget says “We’ll get back to you.” The visitor closes the tab. |
| 7:12pm | The service inbox, only on the office manager’s phone | AC stopped blowing cold, wants a visit this week | Unread. | |
| 7:40pm | Phone | The voicemail app | Price for a first visit | No message left. |
| 8:15pm | The shared inbox, under two newsletters | Move Thursday’s appointment | Unread. | |
| 9:30pm | SMS | The van phone, switched off | “Running 10 min late tmrw, is that ok?” | Unread. |
| 11:48pm | Web chat | The same email alias | The 6:42pm visitor, now comparing you with two competitors | Same auto-reply. |
| 6:55am | Phone | The voicemail app | The 7:40pm caller, trying again on the way to work | Rings out. The office opens at 8. |
At 8:03am the front desk logs in. There are seven conversations across five places, and nobody knows that the two chats are the same person, or that the voicemail and the 6:55am call are the same person.
Nothing in that night is unusual. Every step is someone doing their job with the tools they have. The customer chose the channel, and each channel lives in a different tool.
Why do after-hours messages go unanswered?
1. Every channel lands in its own inbox. Nobody sees all of it, so nobody can answer all of it, and the morning starts with someone hunting through each place in turn. You notice this when a customer says “I messaged you last night” and nobody can find the message.
2. Customers repeat themselves. The 6:42pm visitor came back at 11:48pm and asked the same question, because nothing remembered the first conversation. The 7:40pm caller tried again at 6:55am. When your team finally replies, different people answer different channels, sometimes with different answers. You notice this when two of your staff reply to the same customer in two places.
3. The first reply gets the first chance. Someone who needs help tonight may well ask more than one business. If the AC is out and the homeowner messages three companies, whichever answers first gets the first chance to book. A reply at 8:30am, however friendly, competes with someone who answered at 7:13pm. You notice this when a customer replies to your morning message with “Thanks, already sorted.”
What we’d build: one agent, every channel, one memory
The same agent answers web chat, SMS, email and phone, remembers every conversation across them, and acts inside the systems you already use. Here is the same night again.
| Time | Channel | What the agent did |
|---|---|---|
| 6:42pm | Web chat | Answered: yes, two of the three locations open Saturday. Offered the next three Saturday slots. The visitor booked 10:30am at the nearest location. |
| 7:12pm | Recognised the customer, asked two questions to check whether it was urgent (no water leak, the system still runs), and booked Thursday morning, the first open slot. Confirmed by email. | |
| 7:40pm | Phone | Answered on the first ring, gave the first-visit price from your approved answers, and offered to text a booking link. The caller booked by text before hanging up. |
| 8:15pm | Moved Thursday’s appointment to Friday in your booking system and replied with the new time. | |
| 9:30pm | SMS | Checked tomorrow’s schedule, said 10 minutes late is fine, and added a note for the front desk. |
| 11:48pm | (none) | The 6:42pm visitor was already booked, so they didn’t come back. |
| 6:55am | (none) | The caller was already booked, so they didn’t call again. |
At 8:03am the front desk opens one inbox across every channel: three bookings, one reschedule, one late arrival noted, and nothing urgent overnight. Each item opens the full conversation.
This is the job of AtomsAI’s Front desk agent. In short:
- After-hours message on any channel → Front desk agent → answered, booked, rescheduled or noted in your system, and confirmed on the channel the customer used.
- Something urgent or outside its rules → Front desk agent → your on-call person paged with a summary, or a handover waiting for your team in the morning.
It answers every channel with one memory, so a customer who starts on chat and switches to a call is picking up the same conversation. When a new enquiry needs qualifying, for ex. a full system replacement rather than a repair, it works alongside the Sales agent. When an existing customer needs something done to their account, such as a refund or a plan change, it works alongside the Support agent. You can try the chat agent yourself.
What you control. Which channels the agent answers, during which hours, and in whose name. What it can book, change or cancel, and what needs a person to approve. What counts as urgent: for ex., a no-heat call in January or a gas smell pages your on-call person straight away with a summary, while a price question waits for morning. Your team can pause the agent for one customer or join any conversation live.
What it never does on its own. Diagnose, quote a price you haven’t approved, promise something your schedule can’t deliver, or argue with a customer. When someone asks for a person, or when the agent isn’t sure, it hands over with a short summary, what it already tried, and the full transcript, so nobody has to ask the customer to start again.
Where it connects. Your calendar (for ex. Google Calendar or Outlook) or booking system, your CRM (for ex. HubSpot or Salesforce), your website, your texting number, your phone line and your email. If you run JustCall, we connect your JustCall account during the build.
What leaving it costs
Here’s a worked example. Swap in your own numbers.
Take the same three-location home-services company, getting 20 contacts after 6pm on an average weeknight, across every channel.
- Say 6 of those 20 are new people asking for a job or a visit.
- Say the average first job is worth $400.
- Say that, because they hear nothing until morning, 2 of the 6 book with someone else first.
That’s 2 × $400 = $800 a night. Across 22 weeknights a month, that’s $17,600 a month, before weekends and before what those customers would have spent with you next year.
Then there’s the morning. If the other 14 contacts each take 4 minutes to find, read and reply to, that’s 56 minutes of catch-up before the phones even start, every day.
You can measure your own version in a week. Count everything that arrives after closing, on every channel, and note how many were new customers and how many of those you actually booked.
How to start
Ask us for a teardown of your after-hours workflow. It takes 30 minutes. Bring a list of every channel customers use to reach you, where each one lands today, and, if you can, a rough count of last week’s after-hours messages. You’ll leave knowing which conversations an agent can finish on its own, which ones need a person, and what it would take to connect your booking system and CRM.
Standard agents go live in days. Custom work across several of your systems takes 4 to 8 weeks.
Questions buyers ask
Do we really need to answer on every channel? You need to answer on the channels your customers already use. One agent can cover web chat, SMS, email and phone with the same answers and the same memory, so adding a channel doesn’t mean adding a person to watch it.
Will customers know they’re talking to an AI? They should, and we set it up that way. The agent introduces itself as your assistant, and anyone who wants a person can ask for one and gets a clear answer about when they’ll hear back.
What happens when something is urgent at night? You set the rules. For ex., a no-heat call in winter or a burst pipe can page your on-call person straight away with a summary, while a price question waits for a reply in the morning.
Does it book into our own calendar and systems? Yes. The agent books into the calendar or booking system you already use, updates your CRM, and logs every conversation, so your team starts the morning from one inbox that shows what happened on every channel.
How long does it take to set up? Standard agents go live in days. Custom work that connects several of your systems takes 4 to 8 weeks.