Bot builder, essential AI agents and autoreplies: why they are legacy

Plan requirement

Subscription Any plan
Access Admin

Bot builder, essential AI agents and article autoreplies still exist and are not where new work belongs.

What each of them was

  • Bot builder: a flow chart. You drew every path the conversation could take.
  • Essential AI agents: the same flows with intent recognition added.
  • Article autoreplies: a suggested article sent automatically in reply to a ticket.

Why they are being left behind

All three worked by pattern rather than by understanding. A flow handled the paths you drew; an autoreply matched a question to an article and sent it whether or not it fitted.

The current generation answers from your content in its own words and follows procedures you write in sentences. That is a different thing to maintain, and it covers cases nobody anticipated.

What this means practically

They keep running and they will not gain new capability. Anything you build in them is work you will do again.

If you are starting now, start on the current generation. If you are already running a flow that works, there is no emergency, and there is no reason to extend it either.

Moving is a rebuild

Flows do not convert into procedures, because the thing you maintain changes from a diagram to written instructions. Plan it as a project, and use it as an opportunity to drop the paths nobody ever took.

Why this matters when you read

Documentation and forum posts cover all three generations without always saying which. Instructions about dragging nodes onto a canvas are describing the oldest one.

See also

Was this article helpful?

0

Still stuck?

Our support team will take a look with you.

Comments

0 comments

Article is closed for comments.