Features
Everything Ask does, on one page.
The short version: a bot answers from your material, tells you where it failed, and you fix it from what it tells you. Here's the rest of it.
The differentiator
States, cases and the inbox
Four states detected during the conversation, gathered into one case per conversation, with the transcript and whatever the visitor left behind.
The improvement loop
Instructions, versions and replay
Instructions are versioned. Before you publish, the draft is replayed against the questions your bot previously failed, and you see which ones it now answers.
What it knows
Content and data levels
A paragraph of instructions, structured entries with typed attributes, or a read-only API of yours. Crawl, import, sync, or write them by hand.
Where it runs
Channels
The website widget today, with Slack and Discord next, plus a plain API and MCP access for your own tooling.
Setup
Crawl-based onboarding
Give Ask your address and it reads your site, drafts instructions and entries, and shows you both before anything is live. You end with a working bot, not an empty text box.
Setup
WordPress plugin
Install, connect, done. No theme file editing, no snippet, and the cases show up inside wp-admin.
Routing
Where cases go
Keep them in the inbox, email them to an address per state, or post them to a webhook. Outbound email starts working once your widget's domain is verified.
Measurement
Analytics by version
Conversations, answered-well rates, content gaps and cost per conversation - every metric sliceable by the instruction version that produced it.
Appearance
Theming and the widget
Colours, scheme and placement from the app; a documented token and slot contract for anything deeper. The widget's code is public, so you can read exactly what it does.
Control
Retention, export and deletion
Set how long transcripts are kept, export everything your workspace holds, and delete one visitor's data through the whole chain it reached.
Cost
A hard stop, not a bill
When the included usage is gone, the bot stops answering and tells the visitor so. Their question is still recorded as a case.
Access
Sign-in and staff
Email and password or your own single sign-on, and as many staff accounts as you like. There is no per-seat charge - more people reading the inbox is the point.