AI support

An agent that answers from your content, not the internet.

Train it on what you already wrote. Embed one line of code. It answers the questions your team is tired of repeating, in ten languages, and gets out of the way when a person or a ticket should take over.

  • Answers from your files, site, text and Q&A — not the open internet
  • Live on your site with one script tag
  • Hands off to a person, or files a ticket, when it should not answer alone
Support agentLive

How long is the refund window?

30 days from delivery, as long as the item is unused.

Trained on

refund-policy.pdf

Trained

help.acme.com

Trained

Q&A · Returns

Trained

What the agent is for

This is the front line. Everything else in AssistLoop — the inbox, the ticket queue, the actions — hangs off a visitor who opened the widget and asked a question.

Your material, not a generic guess

It answers from the files, pages, notes and Q&A you trained it on. Ask a general model your refund window and it invents one. This one cannot, because it was never given the open internet as a source.

On the site in minutes

One script tag, or an official plugin for WordPress, Framer, Bubble or WHMCS. The dashboard has install guides for the rest. Most teams are live the same afternoon they sign up.

Around the clock, in ten languages

The widget speaks the visitor’s language without a translation plugin, including Arabic with right-to-left support. Nobody has to be online for an FAQ to get an answer.

Knows when to stop

If the question is one a person should take, a teammate picks up the same thread. If the work will outlast the chat, it becomes a ticket. The agent is not asked to be perfect.

Can do more than talk

Book a meeting, look up an order, collect a lead — if you give it an action. The default is still an honest answer from what it was trained on.

Free to put on a site

The free plan trains an agent and embeds the widget, with 150 message credits a month and no card. Handoff, tickets, and saved appearance live on paid plans.

How AI support runs

  1. 01

    Teach it what you already wrote

    Upload files, crawl the site, paste text, pin the answers that have to be word-perfect. The agent has no other knowledge.

  2. 02

    Put the widget on the site

    One script tag, or a plugin. Style it so it looks like you built it. Visitors do not leave the page to get an answer.

  3. 03

    It answers. A person or a ticket takes the rest

    The repetitive questions stop reaching the team. The ones that should not stay with the bot have a live path and a desk.

AI support in depth

The job is answering, not chatting

Most “AI support” is a chat window bolted onto a general model. It is fluent, and it is guessing. A visitor asking for *your* refund window does not want a plausible paragraph. They want the policy you actually run.

AssistLoop’s agent is a support front line trained on your own content. That is the whole product, stated plainly: it answers from what you gave it, around the clock, and it stops when it should. Live chat and tickets are what happen after that.

The agent answers from your files, site, text and Q&A. It is not browsing the open internet for a plausible reply.

What it knows, and what it does not

Four sources cover where support knowledge usually lives: uploaded PDF, DOCX or TXT files (up to 42MB each), a crawl of your website from one root URL, pasted text, and pinned question-and-answer pairs for the answers that cannot be paraphrased.

It does not invent a missing policy to sound helpful. If the answer is not in the sources, it says so, or a person takes the thread. It also does not attach source links to its replies — the customer gets a plain-language answer, not a bibliography. How you feed it, prune a crawl, and retrain a source that changed is on the training page. Which model reasons over that material, and what each reply costs in credits, is on model selection.

PDF, DOCX and TXT up to 42MB, a site crawl, pasted text, and Q&A. Retraining is a click you make, not a background job.

When the agent should not finish the conversation

The objection to every support bot is the same: what happens on the question it cannot help with. Here there are two exits, and they are not the same job.

A person takes over the same thread when the customer is still waiting — refunds that are actually complicated, someone who is already angry, anything that should not be left with a model. That is human handoff, on every paid plan. You can also turn the AI off entirely and run the widget as a live inbox.

A ticket is filed when the work will outlast the chat: a bug, an investigation, a refund that will take two days. Native tickets sit next to the inbox, with an owner and a private link for the customer. They are not a HubSpot sync.

Handoff is for a customer who is waiting. A ticket is for work that continues after they leave. Both keep the conversation attached.

Getting it on the site, and letting it act

Install is a single script tag, or an official plugin on WordPress, Framer, Bubble or WHMCS. The widget can look like yours: name, logo, colours, greeting. On the free plan you can change every appearance setting and watch the preview; only the agent name and interface language persist until you upgrade.

Answering from documents is the default. If a question needs a live system — order status, a Calendly slot, a lead form — that is an agent action. You wire the endpoint; the agent gathers what it needs in the conversation and calls it. Actions are how the front line stops being a search box. They are not required to go live.

A script tag or an official plugin is enough to go live. Actions are optional, and appearance beyond name and language needs a paid plan to persist.

What it costs

Free is $0, 150 message credits a month, no card. You can train an agent and put the widget on a site. Paid plans start at Basic $29 (3,000 credits), then Pro $130 and Business $390. Annual billing trims the monthly rate. See pricing for what each tier includes.

Each AI reply spends credits. The cost per message is shown next to the model before you pick it. Credits reset each month and do not roll over. Handoff and native tickets are paid-plan features. Extra credits, agents and seats are add-ons.

Free trains and embeds the agent. Handoff, tickets, and saved widget appearance start on paid plans. Credits do not roll over.

Frequently asked questions

Where does the agent get its answers?

From the content you trained it on: uploaded files, a crawl of your website, pasted text, and pinned Q&A pairs. It does not browse the open internet, and it does not invent a policy to sound helpful.

How long does it take to go live?

Most teams are on the site the same day. Add sources, copy one script tag or install a plugin, and the widget is live. Official plugins exist for WordPress, Framer, Bubble and WHMCS.

What happens when the AI cannot help?

A person can take over the same conversation, or the work can become a native ticket if it will continue after the visitor leaves. You can also turn the AI off and use the widget as a live-chat inbox.

Does it work in languages other than English?

Yes. The widget supports ten languages, including Arabic with right-to-left layout. You pick the language in the widget settings; there is no separate translation plugin.

Can it do more than answer FAQs?

Yes, if you give it actions. It can book a Calendly or Cal meeting, collect a lead in the chat, or call an API you own for things like order status. Without actions it still answers from what you trained it on.

Is AI support on the free plan?

Yes. You can train an agent and embed the widget for free, with 150 message credits a month. Human handoff, native tickets, and saving the full widget appearance require a paid plan.

Keep exploring

Let the repetitive questions stop reaching the team

Train an agent on what you already wrote, put it on the site, and keep people and tickets for the work that is actually work.