managed
We hold the credentials
WPIntegrate runs the client-credentials flow for your tenant. Your administrator grants consent once and is not asked again.
Released component
AI Assistant
AI Assistant is a chat assistant for your website that answers from the content you give it, takes a visitor’s details when they want a reply, and hands the conversation to your team by email, in Microsoft Teams or through a webhook — and your conversations are never stored on our servers.
AI Assistant has no WordPress plugin equivalent — it exists as a web component only. The component platform is in pre-launch, so interest is collected through the contact page rather than through a signup.
larkspur dental
Ask us anything
Hi! Ask me anything about the practice, and I can put you in touch with the team.
Do you see emergency patients on Saturdays?
Yes — 9am to 12pm, by phone first. Would you like the team to call you back?
AI Assistant itself, running here on a fictional host — the released bundle from our CDN, loaded the same way your own page would load it. The data behind it is sample data of our own invention; on your site the same component reads your Microsoft 365 tenant.
Putting it on the page
What you paste into the page.
Two lines, and neither of them is a build step. Everything the component shows is resolved from the key at request time, so the markup on the page is the last markup anyone writes.
What it does
How it works
The AI Assistant component puts a chat assistant on any page, as a floating launcher or a panel placed in the page. You describe its role and tone, write the rules it follows, and give it your business knowledge as text and question-and-answer pairs. When a visitor wants a quote or a person, it collects their details with your consent wording and delivers a summary and the conversation to the destinations you choose. Replies come from Anthropic’s Claude, called from our server.
Why it exists
Visitors ask the same questions at hours nobody is answering, and a contact form makes them wait a day for something the website already says somewhere. A generic chatbot answers confidently from the internet rather than from your business. This answers from what you have written, says when it does not know, and when the answer is a person it passes the visitor to your team with the context attached instead of starting the conversation over.
- Element
<wpi-ai-assistant>- Reads from
- Anthropic Claude, Email, Microsoft Teams (Workflows), Webhooks
- Arrangements
- 4 in the builder
- Graph access
managedorproxy— the tenant chooses
Arrangements in the builder
- Floating launcher — a bubble, a labelled button or a question box — bottom left or right
- Greeting shown above the launcher before it opens, or opened on page load
- A chat panel embedded in the page
- Window size, brand colour, corner style, font and light or dark mode
Where it runs
Anywhere you can paste two lines of HTML
A custom element needs no build step and no framework, so where your site is built is not a question you have to answer before this one.
- WordPress
- Webflow
- Squarespace
- Shopify
- Wix
- Astro
- Next.js
- Drupal
- SharePoint pages
- Plain HTML
Named as examples of places HTML can be pasted. No partnership is implied, none of these are customers, and the marks beside them are our own drawings rather than any vendor's logo. WordPress is the one that gets more than an embed — the same Microsoft 365 jobs also ship as plugins with a Gutenberg block.
In detail
Everything AI Assistant does.
7 capabilities, every one of them resolved from the embed key rather than written into the page.
-
Answers from what you tell it
Give it an overview of the business, blocks of text — services, prices, hours, policies — and question-and-answer pairs. Answers are treated as guidance rather than scripts, so it can rephrase or combine them, and it is told to say when something is not covered rather than guess.
-
Rules kept apart from facts
Behaviour is written as rules, one situation each — ask for an order number before discussing a refund, never quote a delivery date. Facts belong in knowledge. Keeping the two apart is what stops the rules list turning into a second knowledge base nobody can search.
-
Collects contact details, with consent
When a visitor wants a quote or a call back, it asks for an email address and, if you choose, a name and phone number, showing your own consent wording. A visitor can decline, and it is told not to insist.
-
Hands the visitor to your team
When someone asks for a person, it sends you a summary and the conversation and tells the visitor when to expect a reply. Delivery goes to email recipients you list, to a Microsoft Teams channel through a Teams Workflows link, and to your own systems as a webhook event. Today your team replies by email; a person joining the same chat window is not available yet.
-
Your conversations are not stored by us
The conversation is held in the visitor’s browser and sent with each message. Leads and hand-offs are delivered to your destinations and kept nowhere on our side — there is no inbox of transcripts to secure, and also no copy to recover if a destination is misconfigured, so the builder warns you when nothing is set to receive them.
-
Never a dead chat
If the AI cannot answer — the free allowance is spent and no key is set, or the provider is unavailable — the assistant switches to a plain contact form whose message is delivered the same way, so a visitor is never left with a broken widget.
-
Limits you control
Every visitor message is a call to the model, so the builder sets a maximum message length, messages per conversation and messages per minute, all enforced on our server, and an allowlist of the sites the assistant may answer on.
Say what you need it to do.
AI Assistant exists as a web component only, and the component platform is in pre-launch. Interest arrives as email rather than as a signup, and somebody reads it.
Reaching your tenant
Two ways for us to reach Graph. One of them never lets us.
Every tenant runs in one mode or the other, and the choice belongs to your IT rather than to us. It is the reason this works inside organisations that will not delegate Graph access to a vendor.
proxy
You hold the credentials
You supply a base URL and an API key for your own gateway. We store that key encrypted at rest and never hold a Graph token at all.
Questions
The things people ask before they buy.
If yours is not here, ask it — the answers come back from a person rather than a form.
What does AI Assistant cost?
$9 a month or $90 a year, sold on its own rather than as part of the All Apps Pack. A free allowance of conversations is included; after that it runs on your own Anthropic API key.
Do you store our conversations or leads?
No. The transcript stays in the visitor’s browser, and a lead or hand-off is delivered to the email addresses, Teams channel or webhook you set and then discarded. What we keep is a short-lived session counter and a usage count, neither of which contains what anyone said.
Can someone from our team take over the chat live?
Not yet. Today a hand-off is delivered to you with a summary and the conversation, and your team replies by email. A person joining the same chat window is planned for a later phase.
What can it learn from?
The text you put into the builder: an overview, text blocks and question-and-answer pairs. It does not read your website or a SharePoint library yet.
Which AI model does it use, and whose account pays for it?
Anthropic’s Claude, always called from our server so no key ever reaches a browser. A free allowance of conversations runs on our account; after that you add your own Anthropic API key in the builder and conversations run on your account, under your terms with Anthropic.