Awe Chat
AI live chat for your website that answers from your own knowledge, and puts every conversation in Microsoft Teams.
A visitor asks a question and gets an answer in seconds, from what you have told the assistant and nothing else. Your team watches the thread in Teams and can take over, ask for a drafted reply, or leave the AI to it. When the assistant does not know, it says so, offers a person, and logs the gap so you can fill it.
- AI
- Claude, from Anthropic
- Team
- Microsoft Teams, two-way
- Alerts
- Teams or Slack
- Install
- One script tag
- From
- £150 a month, plus £600 setup
- Data
- Cloudflare, EU region
Nell is the assistant on this site: Awe Chat, set up for Awe Creative.
On your website
In your Microsoft Teams channel
Website chats · Awe Chat🟢 New Awe Creative chat
Visitor from a business network Prospect
- Told us
- Need: online shop · Sells to trade
- Lead score
- 7 / 10: asked for a person, told us 2 things, viewed a pricing page, returning visitor
- Arrived
- Google search, landed on /awe-commerce.html
- Visit
- 3rd visit · 6 pages · desktop
- Status
- Lee has taken over
This is youLive, from this visit
Here is what Awe Chat can see about you, right now.
This is the card your team gets in Teams when a visitor starts a chat, drawn from your own visit to this site. Only you can see it. Names and contact details are left out: it says whether you have given them, never what they are.
Visitor
ProspectVisitorsEveryone, not just the chatty ones
Most visitors never open a chat. You still see who they were.
Awe Chat records every visit from the first page, so the console shows which organisations came, where from, what they read and how they found you, whether or not they said a word. The ones worth ringing today are pulled to the top.
The Visitors view in the consoleIllustration. The visitors are made up. Click one.
Worth a look now
| Visitor | Organisation | Source |
|---|
Worked out from the network a visitor is on and its reverse DNS. Visitors are sorted into business, home broadband, mobile, and cloud or bot traffic, so the list is not padded with noise.
Google, Bing, LinkedIn, a campaign tag, a paid click, or an AI assistant such as ChatGPT, Perplexity or Claude. Search queries are stripped unless a campaign tag carries the term.
Open a visitor for a timeline of each session: the pages in order, the links and buttons they clicked, and any chat messages in the place they happened.
When you recognise a visitor, add their name and company and it sticks. "This is me" marks every browser on your own connection as staff and keeps them out of the numbers.
A second tab groups business visitors by organisation: how many people, how many pages, which towns, and whether any of them chatted.
Search by company, place, page or source, and switch between the last 24 hours, 7, 30 or 90 days, with visitors and chats charted per day.
Microsoft TeamsTwo-way, not just alerts
Your team already lives in Teams. So that is where the chats are.
Every chat gets its own thread in the channel you choose. At the top sits a visitor card that updates as the chat moves on: who they are if we know, what they have told us, where they came from, what they have looked at and a lead score with the reasons. Under it, each exchange arrives as it happens. Nobody has to keep a console open in another tab, and it works from the Teams app on a phone.
Take over
The AI stops. Whatever you type in the thread goes to the visitor, who sees your first name and your Microsoft 365 photo. If the AI was halfway through a reply, that reply is thrown away.
Assist me
For each visitor message the AI writes a draft in your voice, as an editable card. Send it, change it, or write your own. Nothing reaches the visitor until you press Send.
Hand back
You have dealt with the part that needed a person. The AI picks the conversation up again, with everything that was said still in front of it.
When a visitor asks for a person, leaves contact details or scores as a hot lead, up to 20 named people are mentioned in the thread, so it reaches their phone.
// like thisA reply that starts with two slashes is a note for the team. It never goes to the visitor.
While the AI has the chat, ordinary replies in the thread stay between staff. Mention the bot to speak to the visitor without taking over.
When a visitor we can identify is on a pricing, demo or contact page and has not opened the chat, the channel gets a message. Once a day per visitor at most.
Each site links to one team and channel. Several sites can share a channel, with a prefix on the thread title to tell them apart.
Sites without the Teams app get one-way alerts into a Teams or Slack webhook, with the last six messages and a link that opens the chat in the console.
What it doesAll of this is running today
Answers you can stand behind
Grounded in one knowledge base per site. It is the only thing the assistant is allowed to treat as true.
- It does not make things up. The rules forbid inventing products, prices, integrations, certifications, customers, opening hours or timelines. Contact details come from the knowledge base or not at all.
- It says when it does not know. Then it offers someone from the team and quietly records what was missing.
- It always admits it is an AI. The launcher and header are labelled, and it must say so when asked.
- Short, plain replies. One to three sentences, one question at a time, with two to four one-tap suggestions under each answer.
- The visitor's language. Written to in French, it replies in French. The widget's own labels are in English.
- Your instructions, inside fixed limits. Set the tone and what to recommend. A site's instructions cannot override the honesty, privacy and safety rules.
- A fallback if the AI is down. A second model is tried. If both fail the visitor is asked to leave an email rather than left hanging.
Knowledge gaps
Every question the site could not answer, in a list. It is a content brief written by your own visitors.
- What was missing, and what was asked. The last 90 days, each with a link to the chat it came from.
- Fix it in the editor. The knowledge base is plain text with headings. Save, and the next reply uses it.
- Try it before visitors do. A test panel chats with the saved assistant and stores nothing.
Leads, qualified gently
You decide what is worth knowing. The assistant finds out without turning the chat into a form.
- Up to eight things to find out. Need, budget band, timeline, platform, company, whatever matters to you. It asks about one at a time, after it has answered the question.
- One-tap answers. Typical answers appear as buttons, so a visitor can reply without typing.
- Up to six next steps. A quote form, a booking page, a case study. The assistant steers towards one, and talking to a person is always among them.
- A lead score out of 10, with its working. Left an email, asked for a person, what they told us, pricing pages viewed, return visits, paid clicks, urgency. Seven or more is a hot lead and raises an alert.
- Contact details caught in passing. An email address or UK phone number typed into the chat is picked out, saved against the visitor and flagged to the team.
Who is on the site
Visitors, not just chats. Including the ones who never open the widget.
- Companies, where they can be read. From the network a visitor is on and its reverse DNS. Home broadband, mobile and VPN traffic is recognised and not mistaken for a company.
- Where they came from. Campaign tags, the referring site, the landing page, and whether the click was a paid one.
- A timeline per visitor. Visit by visit: pages, clicks on links and buttons, and chat messages in order.
- Worth a look now. The most promising visitors of the last 24 hours, and who is on the site this minute.
- Signed-in customers by name. If your site has accounts, one line of code tells the chat who is logged in.
- Your own team left out. Mark a browser as staff and every browser on that network is kept out of the numbers.
A launcher that reads the page
The button in the corner is the whole advert for the chat. So it changes with the page it is on.
- Words that follow the page. Different text, pop-up message and opening buttons on a pricing page than on a case study, with a separate welcome for returning visitors.
- Five styles. Pill, orb, faces, card or tab, in three sizes, on either side, in your colours. Button text colour is picked for contrast.
- A pop-up with manners. It waits for a buying page, a second page or a return visit. It shows once per session at most, stays away for seven days after being dismissed, and never opens the chat by itself.
- Quiet on phones. The launcher shrinks to a small round photo, and the open chat goes full screen.
- A funnel for the launcher itself. Pop-up shown, opened, dismissed, buttons clicked, chats started.
- Live preview. See it on desktop and phone, for each page type, before publishing.
A widget that behaves
Small, isolated from your site's styles, and it keeps the conversation going from page to page.
- The chat follows the visitor. Move to another page and the conversation is still there. It stays open for 24 hours after the last message.
- Late replies still land. Close the panel and a reply from your team arrives as an unread badge while the visitor is on the site.
- Cannot clash with your CSS. It renders in its own shadow root. About 17 KB gzipped, loaded async.
- Works on single-page apps. Page changes made through browser history are followed.
- Links to your pages. A path in an answer, such as /pricing, becomes a link on your site.
- Keyboard and screen reader support. Labelled dialog, live regions, Escape to close, and reduced motion respected.
- A small JavaScript API. Open the chat with a question from any button on your site, identify a signed-in user, pass on a consent choice, listen for events.
The console
For everything that is not a conversation: setup, knowledge, visitors, reporting.
- Chats. Thirty days of conversations with unread counts, full transcripts, and take over and hand back without Teams.
- Visitors. Visitors, chat rate, emails left, hot leads and requests for a person, by period, with a daily chart and a companies tab.
- Setup. Brand, persona name, role, photo and greeting, goals, what to find out, page-aware words, limits, Teams and alerts.
- Knowledge and gaps. The editor, the test panel and the list of what is missing.
- Sites. Add a site, copy its tag, set which web addresses may use it, or pause it.
Limits and privacy
A public AI endpoint is a bill waiting to happen unless it is fenced. This one is.
- Spending limits, per site. Messages per visitor per hour, per network per hour, new chats per network, and AI replies per site per day. Over a limit, the AI is not called.
- Only your web addresses. Each site has a list of allowed addresses. Calls from anywhere else are refused.
- Respects a no to statistics. If a visitor declines statistics cookies, page and click tracking stops. The chat still works.
- Discreet. The assistant is told never to repeat a visitor's location, network or browsing back to them.
- Prompt injection refused. Attempts to change its rules or extract its instructions are ignored.
- Stored in the EU. Chats and visitor records sit in a Cloudflare database in the EU region. Ad click identifiers are noted by type only, never their value.
Works with
Microsoft TeamsTwo-way threads, take over, assist
Microsoft 365Staff names and photos in the chat
ClaudeWrites the answers and the draftsGetting it live
One line on your site. Or none, if your domain runs through Cloudflare with us.
<script src="https://chat.awecreative.co.uk/embed.js"
data-site="pk_your_site_key" async></script>Where we do not deploy the site's code, the tag can be added at the network edge. It can also hide the chat widget you are replacing, so there are never two buttons in the corner. If anything in that step fails, the page is served untouched.
We write the knowledge base
From your site and what you tell us, with anything we could not confirm listed for you to check.
We set up the assistant
Name, voice, greeting, colours, launcher, goals and the things worth finding out.
You add Teams
Install the Awe Chat app in your team, pick the channel and who gets mentioned, and send a test.
The gaps list does the rest
It shows what visitors asked that the assistant could not answer. Fill those in and the answers improve.
PricingPer site
We write the knowledge base, set up the assistant and launcher, add the tag and connect your Teams channel.
Hosting, the AI, the Teams connection and the console. 200 conversations included.
A conversation is one visitor's chat, however many messages it runs to. Each site has a daily limit on AI replies, so the bill cannot run away.
No charge per member of staff: everyone in your Teams channel can read, take over and reply.
Honest about fit
A good fit
- Your team already uses Microsoft Teams
- Visitors ask questions before they buy or enquire
- You want leads with context, not a name and an email
- You would rather the AI said "I don't know" than guessed
- Nobody has time to sit watching a chat inbox
Not yet
- Emailed transcripts or follow-up emails to visitors
- WhatsApp, SMS or social channels
- File and image sharing in the chat
- CRM connections such as HubSpot or Salesforce
- Two-way replies from Slack (alerts only)
- Office hours and rotas
Questions
What does the AI answer from?
One knowledge base per site, written in plain text. The whole of it is given to the assistant on every reply, and it is told that the knowledge base is the only source of truth. It must not invent products, prices, integrations, certifications, customers, opening hours or timelines.
What happens when it does not know?
It says it is not sure and offers someone from the team. It also records what was missing, with the question that exposed it, in a knowledge gaps list. Fill the gap in the knowledge base and the next reply uses it.
Do our staff need to learn a new tool?
No. Every chat is a thread in a Microsoft Teams channel you choose. Staff read, take over and reply from Teams, on desktop or phone.
Does the visitor know they are talking to an AI?
Yes. The launcher and the chat header are labelled as AI, and the assistant must say so when asked. When a person takes over, the visitor sees that person's first name and photo.
How is it installed?
One script tag. If the site's domain runs through Cloudflare with us, the tag can be added at the network edge instead, with no change to the site's code.
Can a scraper run up our AI bill?
There are limits per visitor, per network and per site per day, set for each site. Over a limit the visitor gets a polite fixed reply and the AI is not called. Only the web addresses you list can use your widget.
What does it cost?
£600 to set up, then £150 a month for each site, which includes 200 conversations. Conversations above that are 50p each. There is no charge per member of staff.
Where is the data stored?
In a Cloudflare database in the EU region. Replies are generated by Claude, from Anthropic.
Try it on us
The assistant in the corner of this page is Awe Chat. Ask it something awkward. Then tell us about your site and you will hear back within one working day, with questions and a ballpark.