Skip to main content
GullySystem

Chatbot and Virtual Assistant Development Process

Chatbot and virtual assistant development covers the work behind the conversation. Content is gathered, refusals are defined, answers are tested against real customer questions, and the bot is released to a small group first.

The stages, in order

Collect the content

Rate lists, policies, timings and standard answers are gathered as one current version each, approved by whoever owns them.

Define the refusals

Some topics are handed to a person: discounts, credit, legal and clinical matters, and complaints beyond acknowledgement.

Build the question set

Real questions come from your chat and call logs, with the correct answer agreed for each one.

Test and release narrow

The bot is run against that set, then opened to a limited audience. Conversation logs are read daily.

Why chatbots give wrong answers

A chatbot pointed at a website can answer a customer confidently and wrongly. Usually it has not been given the business’s current rates, policies and timings, and nobody has listed what it should refuse. Neither is a model problem.

After it goes live

The first fortnight is review work. Conversations are read, wrong answers are traced to missing or stale content, and refusals are tightened where the bot strayed. Volumes and handover rates are tracked. A bot nobody reviews goes out of date, as the rate list it was built on does.

FAQ

Frequently asked questions

Can a chatbot handle more than one language?

Yes, in the common languages your customers use, including mixed typing, tested separately for each. Adding a language means testing it properly, since quality differs by language.

Will a bot replace our support staff?

No. It takes the repeated questions, and your team handles the conversations that need judgement.

Can our team edit the answers later?

Yes. Content sits in files or a small admin screen your staff can change, and the index updates from there. A wording change does not need a developer.

How do we know when a bot is ready?

It scores well on the agreed question set and refuses correctly on the out-of-scope ones. The second measure decides whether it is safe in front of customers.

Talk to us

Tell us what you need.

Share your requirements and one of our engineers will come back to you within one business day.

What happens after you share your requirements

  1. A senior engineer reads your answers. Nobody phones first.
  2. Within one business day you get a written note: what we understood, what we would start with, and the questions we still have.
  3. If it fits, a proposal follows with the order of work, what we need from you and what you receive at each step.
  4. No call is booked and nothing is paid until you have read the note. Your details stay with us.

Start with your requirements

Seven short steps that tell us what you need. A senior engineer reads them before anyone gets in touch.

Share your requirements