Practical guides, in the order you need them
Each one is something you do, in the order most people do it — from the first crawl to working out whether any of it moved. If a page is not an action you take, it is in the glossary instead.
/
17 results
Getting started
Crawl something, put it on your site, see it answer. About an afternoon.
- 01Crawl your first site and build a knowledge basePoint Matter Chat at your website, choose what to index, and check coverage before you go live. The first crawl decides answer quality.
- 02Install the widget on your siteTwo lines of script before the closing body tag. Where exactly they go on each platform, and how to verify the install worked.
- 03Set your bot's tone, greeting, and rulesSet a greeting, choose a tone that matches your brand, and write the rules that decide what your assistant will and will not attempt.
- 04Add documents the crawler cannot reachInternal handbooks, datasheets, and gated material can be uploaded directly, so they are answerable without being published publicly.
Configure
The settings that decide what it says, where it runs, and what it costs.
- 01Set spend caps, rate limits, and domain locksThree controls decide what your assistant can cost: domain locks, per-visitor rate limits, and a hard daily reply cap. Set all three before launch.
- 02Deliver captured leads to your CRMLeads are emailed and posted to a webhook the moment they are captured, so they reach your CRM or inbox without anyone checking a dashboard.
- 03White-label the widget and dashboard for clientsPut your agency's branding on the widget, take the Powered-by badge off, and give each client a login scoped to their own conversations and leads.
- 04Set up handover so nobody repeats themselvesDecide when the assistant hands over, where the escalation lands, and what goes with it — so your team starts from context rather than from zero.
- 05Support multiple languages from one knowledge baseAnswer in the language the question arrives in, from content you maintain once — and check quality in languages nobody on your team reads.
- 06Secure your widget with domain locksYour public key is visible in your page source by design. Domain locks, rate limits, and caps are what make that safe.
- 07Send escalations and leads to SlackPut escalations and captured leads in the channel your team already watches, with the conversation attached, so nothing waits in another inbox.
Grow
What to read once it is live, and what to write next.
- 01Turn refusals into captured leadsConfigure when the assistant offers a human, what it asks for, and where the capture goes — so unanswered questions become pipeline.
- 02Read your analytics without fooling yourselfAnswer rate, volume, sentiment, and content gaps — what each number means, and which combinations are misleading on their own.
- 03Find and fill the questions your content never answersEvery refusal is recorded and ranked by demand. Turn that list into a content plan written by your own visitors, in their own words.
- 04Write documentation an assistant can actually retrieveSmall changes to structure and phrasing make a large difference to whether an assistant finds your answer. What to do, and what to stop doing.
- 05Measure deflection in a way you can defendDeflection is easy to overstate. Here is how to establish a baseline, choose an honest metric, and separate real resolution from customers giving up.
- 06Stop your assistant from inventing answersGrounding, refusal behaviour, and citations do most of the work. Here is what else to configure, and how to test that it holds.
Answer honestly. Capture the rest.
Point Matter Chat at your site and see what it can — and can't — answer. It's honest about both.
Start free — chat in your site
No credit card. 2 minute setup.
Every answer cites the source it came from. When there isn't one, it says so — and hands the visitor to you.
Installs on the tools you already run.