Skip to content

AI chatbot development in London, Ontario

In short. Aiwah Labs in London, Ontario builds AI chatbots for web chat, SMS and WhatsApp from USD 299, live in about 3 days for a defined flow. The bot answers in English or French from sources you approve, books visits and logs leads in your CRM, and hands the thread to a person when it is unsure.

AI chatbot development overviewAll services in London, Ontario

People working across a manufacturing floor
Starting price
USD 299
One-time setup, in US dollars. Usage at provider cost.
Typical timeline
3 days
For a defined flow. Extra channels or integrations add time, which we scope on the discovery call.
Languages
English, French
English by default. French where your customers write in it, tested on your own chat history.
Office
London, Ontario
Also serves St. Thomas, Kitchener, Waterloo and Southwestern Ontario.
You own
Code and data
Plus the prompts and the accounts set up for you.

What is AI chatbot implementation?

AI chatbot implementation puts a chat agent on WhatsApp, your website or another channel your customers already use. It answers from sources you approve and takes only the actions you allow, such as logging a lead, moving a booking or opening a ticket.

A widget that only talks leaves your team retyping. We tie the chat to the booking, order or support record and design the handover, so a person gets the whole thread when the bot is unsure. For the wider operation, see customer lifecycle.

  1. Customer

    Writes on web chat or WhatsApp, the channel they already use.

  2. Chat agent

    Answers in the thread and collects the fields the record needs.

  3. Approved sources and CRM

    Quotes only approved pages and policies. Writes the result to your record.

  4. Handover

    A person gets the whole thread when the agent is unsure.

How one message moves through a chat agent, and where a person takes over.

Where it helps in London, Ontario.

Scenarios the setup is built around. Each one ends in a record or a person, not a dead end.

After-hours web chat for a clinic or professional firm

A visitor asks about fees, services or opening a file at night. The bot answers from your approved pages, offers a booking, and logs the enquiry for the next morning.

Quotes and visits for a contractor

A homeowner describes a job by text. The bot collects the address, photos and timing, and passes a complete request to the estimator.

Bilingual first-line support

Common questions get answered in English or French from the policies you approved. Anything else reaches a person with the thread attached.

What we build.

The bot sits on the channels your customers already use and writes into the systems your team already works in.

Channels

WhatsApp and web chat are the usual pair. Instagram, Messenger, Telegram or SMS can be added where you hold the account. Hand-offs reach your team in Slack, Teams or email.

Your sources, your history

The prompts, the approved sources and the thread history stay with you. The models underneath are chosen per flow and can be swapped later.

Your system of record

A reply that books, qualifies or opens a ticket lands in your CRM, helpdesk, store or booking system. If you have no record yet, we build a private one you own.

Approved answers only

Prices, discounts, delivery slots and legal or medical claims come from a source you approved, or from a person. The bot hands over instead of guessing.

Your businessText thread, French and English
  1. Customer:

    Bonjour, est-ce que vous avez une disponibilité cette semaine?

    In English: Hello, do you have an opening this week?

  2. Chat agent:

    Bonjour! Oui, jeudi à 14 h ou vendredi à 9 h. Lequel vous convient?

    In English: Hello! Yes, Thursday at 2 pm or Friday at 9 am. Which suits you?

  3. Customer:

    Vendredi, s’il vous plaît.

    In English: Friday, please.

  4. Chat agent:

    C’est noté. Vendredi à 9 h. Vous recevrez une confirmation par texto.

    In English: Noted. Friday at 9 am. You will get a confirmation by text.

  5. Written to your calendar:

    Booking saved with the thread attached.

Illustrative example. Not a real conversation.

From one real case to a live path.

Live in about 3 days. For a defined flow. Extra channels or integrations add time, which we scope on the discovery call.

  1. Day 1First working session

    Bring one real thread

    A lead, an order change or a support case that someone retyped by hand. That thread becomes the first flow.

  2. Day 1Design, before build

    Mark the approved sources

    We list the pages, prices and policies the agent may quote. Anything off the list becomes a handover.

  3. Day 2Build

    Connect the channel

    WhatsApp, the web widget or both, plus the system that receives the structured request.

  4. Days 2–3Test, before launch

    Test the unsure cases

    A missing price, an angry message and a question outside the source all get tested. Each one should reach a person with the thread attached.

  5. Day 3Launch

    Go live on the channel customers already use

    A defined flow is usually live in about three days. Customers keep writing where they already write.

Setup, priced once.

Prices are in US dollars and exclude taxes. They are one-time setup, not a subscription.

Starter

FromUSD 299One-time setup
  • One channel, web chat or WhatsApp
  • One conversation flow tied to a booking, order or support record
  • Answers limited to an approved source you provide
  • Handover to a person, with the thread attached, when the agent is unsure
Book a call

Growth

FromUSD 799One-time setup
  • Web chat and WhatsApp
  • Up to three flows
  • One integration, such as a CRM, calendar or shared inbox
  • Handover with the conversation attached
  • A review queue for replies the agent was not allowed to send
Book a call

Scale

FromUSD 1,599One-time setup
  • Web, WhatsApp and one further channel you already use
  • Several flows on one customer record
  • Up to three integrations
  • Handover, a record of what the agent said, and a review queue
  • The same limit to approved sources as the smaller tiers
Book a call

Usage is passed through at provider cost: LLM tokens and WhatsApp or other messaging fees. We add no markup.

Bring one call, thread or workflow. We scope from there.

Book a call

What you own at the end.

You own

  • The chat flows and their logic
  • The prompts and the list of approved sources
  • The thread history we set up, subject to the channel and model providers’ own terms
  • The messaging and model accounts, which can sit in your name
  • The build itself, with no vendor lock-in

Controls that stay in place

  • The agent answers from approved sources. It never invents a price or a promise.
  • When it is unsure, a person gets the thread with the history attached.
  • Consent and retention follow the rules where your customer is. Each city page sets out the local rule we design against.
  • Model and messaging usage is billed by the provider at cost. The setup tiers are one-time.

Integrations

Every channel in. Every system out.

Customers write where they already write. The bot answers there, then books, quotes or opens the record in the system your team works in.

Messaging channels

  • WhatsApp
  • Instagram
  • Messenger
  • Telegram

Your website or store

  • WordPress
  • Shopify
  • WooCommerce
  • Magento
ChatbotApproved answers, then the right record

CRM and helpdesk

  • HubSpot
  • Salesforce
  • Zoho
  • Zendesk
  • Intercom

Orders and payments

  • Shopify
  • Stripe
  • Razorpay
  • PayPal

Bookings

  • Google Calendar
  • Calendly

Hand-off to your team

  • Slack
  • Microsoft Teams
  • Gmail
Examples, not the full list. Logos do not imply a partnership with their makers.

Not on the list? We still connect it.

If your system lets data in or out, we connect to it. If it does not, we find a workaround, and we tell you how dependable that route is before we build. We also connect WhatsApp accounts on Gupshup, Interakt or WATI, SMS, Freshdesk, LeadSquared and your ordering or booking system.

  1. API or webhook

    The clean route. Most modern tools have one, and many older ones do too.

  2. Database or export

    No API? We read the database, or a scheduled CSV or SFTP export.

  3. Email and shared folders

    We pick up the reports, invoices and attachments your system already sends.

  4. Screen automation

    For a portal with no other way in, a bot works the screen the way your team does, with every step logged.

How we approach integrations →

What changes in London, Ontario.

Also serves St. Thomas, Kitchener, Waterloo and Southwestern Ontario.

In London, Ontario, a dental office, a law firm or a contractor often gets its first message by text or web chat after hours. A chatbot answers from your approved price list and policies, books the visit, and writes it into your calendar. It speaks English and French, and it works on web chat, SMS or WhatsApp, whichever your customers already write to. Web chat is the simple case. SMS and WhatsApp add a legal layer.

The Canadian Anti-Spam Legislation, CASL, covers commercial electronic messages. Its definition of an electronic address takes in email, instant messaging and telephone accounts, so SMS and WhatsApp follow-ups are in scope. The sender needs the recipient’s express or implied consent, and every message has to identify the sender, give contact details and include an unsubscribe mechanism. The maximum penalty is 10 million Canadian dollars per violation for a business and 1 million for an individual. So the flow records how consent was given, honours a stop word on the spot, and keeps a stopped customer out of the next campaign. We design a reply to a customer’s own question and a promotional follow-up as separate flows, and your counsel confirms the consent basis for each.

PIPEDA applies to the details a chat collects, such as a name, a phone number or an address. Ontario has no general private-sector privacy law of its own, so PIPEDA usually governs, and we write the purpose of collection into the thread.

Sources behind the local points

  1. CASL prohibits sending a commercial electronic message unless the recipient has given express or implied consent and the message identifies the sender, gives contact information and includes an unsubscribe mechanism. “Electronic address” covers email, instant messaging, telephone and similar accounts, so SMS and WhatsApp follow-ups are in scope.

    Electronic Commerce Protection Act (CASL), S.C. 2010, c. 23, sections 1 and 6
  2. The maximum administrative monetary penalty under CASL is 1,000,000 Canadian dollars per violation for an individual and 10,000,000 Canadian dollars for any other person.

    Electronic Commerce Protection Act (CASL), section 20(4)
  3. PIPEDA applies to private-sector organizations handling personal information in commercial activity. Ontario has no substantially similar general private-sector law, so PIPEDA generally governs Ontario businesses.

    Office of the Privacy Commissioner of Canada, PIPEDA in brief (modified 1 May 2024)

Straight answers.

Does CASL apply to a chatbot that texts or messages customers?Local

It can. CASL covers commercial electronic messages, and its definition of an electronic address takes in instant messaging and telephone accounts, so SMS and WhatsApp follow-ups are in scope. The sender needs consent, identification and an unsubscribe mechanism. We record how consent was given and honour a stop word immediately. Your counsel confirms the basis for each flow.

Can the chatbot reply in French?Local

Yes. We build English and French paths and test them on your own chat history before launch. When a message falls outside what the bot handles well, a person takes the thread.

What does an AI chatbot cost in London, Ontario?Local

Setup is one-time: Starter from USD 299, Growth from USD 799 and Scale from USD 1,599. Messaging and model usage are billed at provider cost with no markup from us. There is no monthly fee from us for the setup.

How long does it take to launch?

A defined web chat or messaging flow is usually live in about three days. Extra channels or integrations add time, which we scope on the discovery call.

Where is the chat data stored?

In your own cloud account, in a region you choose, with a retention rule you set. PIPEDA applies to the details the chat collects, so the bot states its purpose in the thread.

Bring one workflow.

Tell us the call, the thread or the record. Every setup on this page starts with a call.

Book a call