home / use cases / email and inbox / faq-autoresponder

The questions you answer every single day

An Aivell answers the questions your customers ask again and again — opening hours, prices, policies, how-do-I — by email, within minutes, using only your own documents as the source. Anything it cannot source is escalated to a person instead of improvised. It runs onboard, so customer mail never leaves your office.

Watch the demo

starts when: A customer question lands in your info@ mailbox

The problem

Some questions arrive every single day, and the answer has not changed in years. Is parking included. Do you allow dogs. What time is check-in. Can I get the invoice with a different VAT number. Each one takes a person two minutes to answer and zero minutes to think about — the definition of work that should not exist.

Speed is the part that stings. The customer asking about availability is usually asking two competitors in the same minute, and answering within a minute lifts conversion by 45% or more. Your documented answer, sent four hours later by a busy human, loses to a mediocre answer sent immediately.

How your Aivell does it

  1. The question is read the moment it arrives. At the front desk’s busiest hour or at midnight — the trigger fires per email, no queue.
  2. The answer is retrieved, not composed from thin air. The knowledge base holds your actual documents — guest guide, price list, policies — and the reply cites them. A guardrail makes your documents the only allowed source.
  3. The reply goes out in the sender’s language. Two tight paragraphs, your tone, within minutes. After hours it adds one honest line: a human follows up in the morning.
  4. The exceptions never get auto-answered. Group requests, discount fishing, anything without a source in your documents — forwarded to the person you named, with a one-line summary, exactly as the chore says.
  5. The repeat offenders improve your docs. A question that arrives three times in a week lands on a docs-update list, so the knowledge base grows where customers actually push on it.

The whole behavior is one chore in plain language. When the rules change — a new cancellation policy, a colleague on leave — you edit a sentence, not a phone tree. And because everything runs on the box, the entire exchange, customer name included, stays inside your building.

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 · answer the usual questions ● active

read every new message in info@; skip anything that isn't a question

find the answer in the knowledge base — house rules, price list, parking, check-in times

no matching source? don't improvise — forward to Nadia with a one-line summary

answer in the sender's language, two short paragraphs at most

group requests and anything mentioning a discount go to Nadia, always

same question three times in a week? add it to the docs-update list for Nadia

between 22:00 and 7:00, add that a human will follow up in the morning

keep a log of every question — answered or escalated, and from which document

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.

Email reads questions, sends the answers
Knowledge Base the only permitted source of answers

Sensible guardrails.

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

Knowledge Base Answers may cite only the approved documents folder. No matching source means escalate — improvising is blocked.
Email May reply only to the sender's own thread; new outbound mail is limited to your team's addresses.

Questions, answered.

What happens when the answer isn't in our documents? +

Nothing gets invented. The guardrail on the Knowledge Base allows answers only from your approved folder, so an unsourced question is forwarded to a person with a one-line summary. Your customers get either your documented answer or a human — never a guess.

Will customers realize they're writing with a machine? +

That's your call, written into the chore. Many businesses sign honestly — "answered automatically from our guest guide, a human is one reply away" — because a correct answer in four minutes beats a signed one in four hours.

Where does customer email actually get processed? +

On the box, in your office. Reading, retrieval and drafting all run onboard; the mailbox stays on your own mail server. No message, name or booking detail is sent to a cloud AI service.

How do we change an answer — say, new opening hours? +

Update the document, the way you already do. The knowledge base indexes your files, so the next reply cites the new hours. There is no second place where answers live and go stale.

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