Support and knowledge chatbot

A support chatbot that answers from your own documents

One knowledge base with an explicit access boundary: public visitors can search only material approved for public release, and staff can access internal sources according to their permissions. Every answer cites its source, and a person takes over when they should. For a staff-only assistant behind your login, see the private knowledge assistant.

Request a Free Session

Demo with made-up data · Live app · web widget and summary prototypes

Who it is for

Built around one practical workflow first

Retailers, service businesses, and teams that answer the same questions on the website every day.
Businesses with policies, price lists, and procedures that staff cannot find quickly.

Workflow pain

Where the work usually slows down

Customers ask about delivery, returns, and pricing at 9 pm and wait until morning.
Staff answer from memory, so answers drift from the written policy.
Generic chatbots make things up because they have never read your documents.

Implementation design

What Eleticle builds and controls

What is built

A website chat widget and an internal assistant on one knowledge base, where public visitors search only material approved for public release and staff see internal sources according to their permissions.
Answers grounded in your documents, with the source shown on every reply.
Hand-over rules for complaints, cancellations, and anything the documents do not cover.

What data is used

Policies, price lists, SOPs, product guides, and FAQ material you approve, each marked public or internal.
Hand-over rules and the people who receive escalations.

What AI may do

Answer questions the approved material covers, with a citation.
Say when it does not know, and hand over with the transcript.
Log every conversation for review.

Human review

AI prepares work. People approve important outputs.

The assistant is scoped around clear boundaries: what it can read, what it can prepare, what must be reviewed, and what should stay manual.

Complaints, disputes, and anything outside the documents go to a person.

Document owners decide what the assistant may read, which sources are approved for public release, and when it updates.

Before and after

Example workflow change

Before

Website questions wait for the morning, staff dig through folders for the refund policy, and answers vary by who replied.

After

Customers and staff get the same sourced answer in seconds, and a person handles only the conversations that need judgement.

More workflows

Clinic operations

Private AI for clinic admin and SOP lookup

Document extraction and processing

Document extraction and processing that only asks you about the exceptions

Lead follow-up and CRM

Lead follow-up and CRM automation that never lets an enquiry go cold

Knowledge assistant

Private knowledge assistant for internal teams

Brisbane AI automation

AI automation for Brisbane businesses

AI receptionist

AI receptionist and bookings for phone, WhatsApp, and web chat

Content pipeline

A content and marketing pipeline that drafts on brand and waits for your approval

Start with one free session

Share the workflow you want to improve. Eleticle will help identify the safest useful first step.

Request a Free Session Not ready? Read how a free session works