wren wren
Open app

wren onboarding

Set up your AI helper in six steps.

wren reads your public pages, learns your menu, policies, and FAQs, then gives you a helper you can configure and publish in one line of embed.

~20sto read your site
6 stepsfrom URL to publish
1 scriptto deploy widget

Three pillars

Crawl, teach, publish.

Every wren setup follows the same arc — point at a URL, add the stuff the site doesn't say, then launch.

Crawl

Read your public pages

Paste a URL. wren walks the sitemap, pulls hours, menus, policies, FAQs, then shows you exactly what it found so you can keep or drop any page.

bluebird-cafe.com → 12 pages · 2,184 words indexed
Teach

Fill in what the site missed

Upload PDFs, paste internal notes, or write plain-text FAQs. wren layers your know-how on top of the crawl so the helper answers from the same source of truth your staff does.

returns-policy.pdf · 1 page added · 320 words of context
Publish

One line, live on any site

Copy a single embed script, drop it before </body>, and the widget is live. Squarespace, Shopify, WordPress, plain HTML — same snippet.

<script src="wren.js"> deployed · bluebird-cafe.com

How it works

The exact six-step flow.

No guesswork. Each screen in the app maps to one of these — and you can back out of any of them without losing progress.

01

Your website

Paste a URL and run the crawl. wren simulates visiting each page and shows progress live.

02

What we found

Review every discovered page. Toggle off anything that shouldn't train the helper.

03

Add know-how

Attach docs, paste context, or write FAQs. Fill in anything the public site doesn't cover.

04

Your helper

Name it. Pick a greeting, tone, colour, and supported languages. Voice stays consistent.

05

Try it out

Chat with the helper in a realistic preview. Test the golden path and the awkward edge cases.

06

Publish

Copy the embed. Paste it once. The helper is live, and you can tweak anything without redeploying.

Built in

Everything a small shop actually needs.

No plugin tree, no prompt engineering. Just the pieces that make the helper feel like part of your brand.

Helper personality, not just a bot

Name your helper, pick greeting and tone, add the languages you answer in. The same config drives every reply, so the helper sounds like your shop no matter who's asking.

NameRobin
ToneWarm · direct
Colours

Only your public site leaves

No scraping of admin pages, no background watching, no clipboard access. wren trains on what you explicitly approve.

Smart hand-off when unsure

If the helper isn't confident, it says so and offers to grab an email. No made-up answers, no guessing at hours.

One embed, anywhere

Squarespace, Shopify, WordPress, or plain HTML. Drop one script before </body> and the widget is live. Update your helper from the app — no redeploy needed.

<!-- before </body> -->
<script src="https://wren.app/w/bluebird.js" defer></script>

Live preview before publish

A realistic chat widget sits next to your config. Test the golden path and the edge cases before anything goes live.

Dark and light, polished

Every screen works in both themes with the same care. The widget itself adapts to your site so it never looks glued on.

FAQ

A few things worth knowing.

No. The whole flow is URL crawl plus one script embed. No databases to wire up, no webhooks to expose.
Yes. Toggle off any crawled page, add specific training files or FAQ answers, and the helper will only draw from what you've approved.
Yes. Configure name, greeting, tone style, and supported languages in step four. The widget picks up your colour too, so it feels native to the site.
It says so and offers to collect an email for a human follow-up. No hallucinated hours, no invented return policies.
Anywhere you can add a script tag. Squarespace's Code Injection, Shopify theme editor, the wren WordPress plugin, or a plain HTML template.

Launch your helper this afternoon.

Paste a URL, add any extras, publish. The whole arc takes less than an hour the first time.