Skip to main content

Assistants that answer from your own documents

We build assistants for customers or for your team that answer from your documents, policies, and data, not the open web, and hand off to a person when they are not sure.

Build an assistant

What this service is about

What it is

An assistant that answers questions from your customers or your team using your own documents, policies, and data, not the open web. It shows where each answer comes from and passes the conversation to a person when it is not sure.

Who it's for

  1. Your team answers the same questions every day by chat, email, or WhatsApp.

  2. Customers wait for answers that are already in your documents.

  3. New employees spend weeks finding information scattered across files.

What you get

  • An assistant built on your documents, FAQs, and data

  • Deployment on your website, WhatsApp, email, Slack, or Teams

  • Handoff to a person, with the conversation attached

  • A monthly view of unanswered questions and errors, to keep improving it

What it looks like in practice

Illustrative examples of typical projects.

  • 01

    Support that answers at 2 a.m.

    An online store adds an assistant to its website and WhatsApp that answers questions about orders, shipping, and returns from its own policies, and passes complex cases to the team.

  • 02

    An internal help desk

    Employees ask an assistant in Slack or Teams about vacation policy, expense rules, or how to use a system, and get an answer with a link to the source document.

  • 03

    A sales team that knows the catalog

    A distributor's salespeople ask an assistant for product specs, stock, and similar items during a call, instead of searching through PDFs.

Our Process

  1. Gather

    The documents, FAQs, and data the assistant is allowed to use.

  2. Build

    The assistant, its rules, and the channel it lives in.

  3. Test

    Real questions from your business, checked before launch.

  4. Improve

    Review what it missed, then update the content and the rules.

Timeline and pricing

Typical timeline
Usually four to eight weeks, depending on how much content the assistant uses, how many channels it serves, and which systems it connects to.
How it is priced
A fixed price to build and launch, based on the scope. Running costs depend on the number of conversations, and we estimate them with you before launch.

Common questions

Answering the same questions every day?