Service

AI website assistant with human handoff

Routine questions get an answer at once, day and night; the hard ones go to your staff in the same conversation. You can try it right now: the assistant in the corner of this page is our Site Agent.

Who it's for

  • Businesses that answer the same questions every day
  • Sites where a visitor should reach a person without hunting for contacts
  • Teams that want AI answers, but from their own materials and under their rules

Tasks we take on

  • Answer questions about services, terms and products from your materials
  • Call a staff member into the chat when the visitor asks for a person or the AI should not decide
  • Notify your team in Telegram and let them reply from an operator console
  • Take the visitor's contact and the context of the request

What you get An assistant on your site that answers from your knowledge base and passes the conversation to a person with the whole history.

Scope of work

What the work can include

  • Connecting the widget to your site
  • A knowledge base from your pages and documents
  • Rules for when the assistant answers and when it calls a person
  • Telegram notifications and the operator console
  • Tuning after the first real conversations

What the estimate depends on

  • The volume and state of your materials
  • Languages
  • Integrations with your systems
  • Where it runs and who supports it

What helps us start

  • Your site and the documents the answers should rely on
  • Questions customers ask most often
  • Who answers when a person is needed, and when
  • Topics the assistant must not answer

Cases

Screen recording of the Site Agent demo

Own product Working demo at lnpower.org/agent/

Site Agent — the AI assistant on this site

The assistant on this page is Site Agent, our product: it answers from the site's content and hands over to a person.

Our part: Our own product: server side, widget, operator console and deployment are ours.

See it working

Site Agent product page

The product itself and its demos: what it can do on a business site.

How we start

  1. 01

    Describe the task

    Use the form, the chat, or write directly by email or Telegram. No ready specification is needed: a few sentences about what should work and for whom are enough to start.

  2. 02

    We clarify the details

    We read the request and ask only what affects the next step: a new or existing solution, platforms, constraints, materials.

  3. 03

    We agree on the next step

    Depending on the task, this is a consultation, an estimate, a prototype or development. Format, cost and timing are agreed individually before any work starts.

What affects cost and timing

  • The size of the knowledge base and how often it changes
  • Languages and channels
  • Integrations with your systems
  • Hosting and support after launch

There is no price list: the cost is confirmed after we look at the task, and format and timing are agreed before work starts.

Questions

Will the AI make things up?

No AI is free of mistakes, so it answers from your knowledge base, and the rules say when it must hand the conversation to a person instead of guessing.

Who answers when a person is needed?

Your staff: they get a Telegram notification and reply in the operator console. The visitor sees that a person is being called and when they have joined.

What if nobody is available?

The assistant says so and asks the visitor to leave a contact, so your team can reply later.

Can we see it before ordering?

Yes: the chat on this page is Site Agent with our own knowledge base. Ask it about anything on this site.

Not ready to order development?

Start with a consultation: we sort out the question first, with no obligation to order the work.

Discuss a consultation About consultations

Contact

Tell us about your task

A few sentences and one way to reach you are enough.

What is it about? (required)

What should work and for whom; 10 to 4000 characters.

0 / 4000

One channel: email, Telegram @handle or phone.

Add details (optional)

Your contact is used only to reply to this request.