When did chatbots start?

Chatbots started in 1966 with ELIZA, a program built by Joseph Weizenbaum at MIT that simulated conversation by matching keywords and replying from a fixed script. Every old AI chatbot worked that way: ELIZA, then PARRY in 1972, ALICE in 1995 and SmarterChild in 2001. The modern kind, trained on a company's own content and able to answer a question nobody wrote a script for, only arrived after 2022.

This page traces the whole line, from ELIZA to the AI agents businesses put on their websites today, and ends with what that history tells you to do if you want one answering questions on your own site.

Key takeaways

Try it yourself. Train an AI agent on your website, docs, or files. Live in 60 seconds. No code needed.

Start free

The history of chatbots: a timeline from 1966 to 2026

Six moments account for most of the change.

ELIZA and the first AI chatbot

In 1966, Joseph Weizenbaum at MIT released ELIZA. It looked for keywords in what you typed and answered with a pre-set phrase built around them. The technique was simple. The effect was not.

ELIZA's best-known script, DOCTOR, played a therapist, reflecting your own words back at you as questions. People confided in it, and some refused to believe there was no one there. That gap between what the program did and what users believed it understood is still called the ELIZA effect, and it is worth remembering every time a chatbot sounds more capable than it is.

ELIZA proved a computer could hold the shape of a conversation. Everything since, including the AI agent answering questions on a website today, has been an attempt to fill that shape with real understanding.

The role of natural language processing

The step from ELIZA to later chatbots was mostly more rules, written better. Natural language processing is what let programs start working out intent instead of matching strings: reading the structure of a sentence, resolving what "it" refers to, tolerating a typo. Machine learning then let a system improve from data rather than from a developer's next edit. Both had to arrive before a chatbot could answer a question its builders had never anticipated.

What were old AI chatbots, and why did they break?

An old AI chatbot was a rule engine. A developer wrote keywords, decision trees and canned replies, and the program matched your message against those rules and picked one. That is why old chatbots felt like a phone menu in text form. Ask what the script anticipated and you got an answer. Phrase it slightly differently and you got "Sorry, I don't understand."

Three limits defined the entire generation:

Old chatbots vs modern AI agents: what actually changed

Old chatbots, 1966 to 2021Modern AI agents, 2022 onwards
How they understandKeyword and pattern matchingLarge language models that read phrasing and context
Where answers come fromReplies hand-written by a developerYour own website, documents and help articles
Off-script questionsDead endAnswered, or handed to a person
Time to launchWeeks of scriptingUnder 60 seconds
Who builds itDevelopersAnyone who can paste a link

The practical difference is where the knowledge lives. You no longer write the answers. You point the agent at material you already have and it grounds what it says in that. Dante AI works exactly this way: point it at a website, it learns that site's content, and one script tag puts an agent on the page that answers visitors from the site's own material and captures leads. Our guide on how to train a chatbot on your own data covers what to feed it.

What the history means for your website today

Every limit on that list has already been solved by someone else. You do not write scripts, you do not maintain a decision tree, and you do not need a developer. What is left is deciding what your agent should read.

When we speak with new users, the hesitation is almost never technical. It is working out which pages and documents genuinely represent the business. The history gives you the shortcut. ELIZA failed because it knew nothing, so start by giving your agent the material that makes it right the first time.

Three steps, all of them in the dashboard:

  1. Point it at your website. Create a free Dante AI account, paste your URL, and let it read the pages you already publish.
  2. Add the documents your team keeps re-sending. Price lists, policies, FAQs, onboarding guides. The answers usually exist already, buried in email.
  3. Paste one script tag into your site. The agent goes live, answers from your own material and collects the visitor details worth following up.

Then read the conversation logs for a week. What people actually ask is the most honest content brief you will ever get, and it is the one thing no chatbot before 2022 could hand you.

What to expect once your agent is live

Give it one honest test before you decide anything. Write down the five questions your inbox answers most often this month, put them to the agent, and compare each reply with what you would have typed yourself. Weizenbaum's users were fooled because they could not see the script. You can: every answer traces back to a page or a document you supplied, so when one comes back thin, you already know what to add.

You can build and test the whole thing on the free plan, which includes 100 message credits a month plus up to 700 more for completing onboarding, and paid plans start at $40 per month when you need more volume.

Sixty years on, it takes one link. Point Dante AI at your website, ask it the questions you have been answering by hand, and paste the snippet. Free plan, no card.

Start free

Further reading

Keep going with these guides from the Dante AI library: