home / use cases / chat, leads and customer service / after-hours-coverage

After-hours coverage without the night shift

From closing time to opening time, an Aivell answers the chat and the inbox — routine questions from your knowledge base, booking inquiries with details collected, emergencies routed to the on-call number. At 7:45 the night log is waiting, sorted by urgency. Every conversation happens on the box, inside your walls.

Watch the demo

starts when: An inquiry arrives at 11 PM — chat or email, either way

The problem

Your customers’ evening is your closed sign. The couple planning a weekend away at 10 PM, the tenant with a question on Sunday, the traveler in another timezone — they all write when it suits them and hear nothing until it suits you. By then many have moved on: answering within a minute raises conversion by 45% or more, and overnight silence is the opposite of a minute.

The alternatives are all bad trades. An answering service reads a script and knows nothing. Staffing a night shift for a dozen nightly inquiries makes no financial sense. So the standard solution remains an auto-reply — which answers nobody’s question and everyone knows it.

How your Aivell does it

At closing time, the chore takes the desk:

  1. Chat and email both stay live. A message at 11 PM gets a real answer in the writer’s language, whether it came through the widget on your site or straight to the inbox.
  2. Routine questions get real answers. Rates, directions, check-in times, policies — pulled from your own knowledge base, so the night answers match the day ones word for word.
  3. Inquiries get worked, not parked. A booking request at midnight becomes a complete record by 12:05 — dates, party size, name, phone — instead of a one-line email needing three follow-ups.
  4. Emergencies wake the right person. Messages matching your emergency list get the on-call number instantly, and Ines gets an urgent-flagged email. Everything else respects her sleep.
  5. The morning starts with a sorted log. At 7:45 the night’s traffic is in Ines’s inbox — what was answered, what needs a decision, hottest first. The day begins at step two.

The lines are hard where they must be: no rates confirmed, no new recipients beyond on-call, no reading of contract folders — guardrails, not good intentions. Everything softer, from the tone of a holding reply to what counts as urgent, is a plain-language chore you tune like a shift briefing.

The chore, as you'd write it.

No flowcharts, no code — a chore is just a message to your Aivell, in your own words. It shapes it into a solid, guarded procedure and follows it to the letter. This one:

Giulia Aivell · cover the night shift ● active

from 7pm to 8am, and all weekend, handle chat and email yourself

answer routine questions from the knowledge base, in the writer's language

booking inquiries — collect dates, party size, name and phone

a real emergency — lockout, leak, alarm — give the on-call number and email Ines flagged urgent

never confirm group rates or discounts; promise an answer by 9

everything else gets a warm holding reply with an honest timeframe

at 7:45 send Ines the night log, most urgent first

You
Got it — I'll start right away, and check with you whenever something needs a human.
Giulia Aivell

The tools it uses.

Connected with single-click passkeys — no copied tokens, no OAuth hell.

Chat widget answers night visitors on your site
Email handles the inbox, sends the night log
Knowledge Base rates, directions, policies — your own answers

Sensible guardrails.

Every tool can be limited to exactly what this chore needs. For this one, you might set:

Email Replies stay inside incoming threads; the only new outbound address allowed is the on-call mailbox.
Knowledge Base Reads the public-information folder only. Contracts, rate agreements and internal notes are off-limits to this chore.

Questions, answered.

What does "pre-handled" actually mean when I arrive in the morning? +

It means the back-and-forth already happened. The night log lists each request with the details a human would have asked for — dates, party size, contact, what was already answered — sorted by urgency. You start with decisions, not with "thanks for reaching out, could you tell us more".

How does it recognize an actual emergency at 2 AM? +

You define emergencies in the chore — a lockout, a leak, an alarm — and the Aivell matches the message against your list. Those get the on-call number immediately and an urgent-flagged email to Ines. Everything ambiguous is treated as urgent rather than guessed away.

Are night conversations processed by some offshore AI service? +

No. The chat widget and the mailbox both feed the box in your office, and the model answering at 2 AM runs onboard. Guests' names, travel dates and complaints stay behind your firewall at night exactly as they do during the day.

Will it commit to prices or bookings while nobody is watching? +

Only within the lines you drew. The chore forbids confirming group rates and discounts, so those get a promise of a morning answer instead — and the guardrails cap who it can email. The night shift is helpful precisely because it cannot freelance.

Related.

What is an Aivell?

An Aivell is an on-premise AI colleague: a small box that plugs into your network, runs its own AI onboard and takes the repetitive work off your desk. Prompts, documents, data — nothing ever leaves your office. Unplug the internet: it keeps working.

You describe each task as a chore, in plain language. Your Aivell turns it into a solid, guarded procedure and runs it in the background — with guardrails on every tool, a complete audit trail, and approvals in your hand when you want them. One-time setup, fixed monthly fee. No tokens, no overages.

Watch the demo

onboard inference · air-gapped · fixed monthly fee