How to build a trial demo workspace from your own website
Instead of exploring a trial full of someone else’s sample data, you can have Atender build the workspace out of your own business. Give the demo builder your website address (or a short description if you don’t have a site), tell it how thoroughly to read what it finds, and it writes contacts, conversations, help articles, tags, snippets, and an Agent Stack from that content — landing in your trial inbox while you carry on working elsewhere in the app.
This is only offered to trials where it’s turned on for that tenant — if you don’t see it, your trial isn’t eligible.
Where to start it
There are two ways into the guide:
- The corner launcher. A small round launcher sits in the bottom-right corner of the app, the same shape and spot as a web chat widget. Click it to open the guide.
- The empty-inbox offer card. If your inbox is empty and unfiltered, an offer card for the demo builder appears above the usual sample-data card — because a workspace that looks like your own business is worth more than a set of generic examples. This is also the easiest way to find the builder again if you closed the first-login guide.
Opening the guide never dims or blocks the rest of the app. There’s no overlay behind it in any state — you can keep reading conversations, replying, or clicking around while the guide is open, and the same is true once a build is running.
Give it your site — or describe your business
Inside the guide, enter one or more site addresses. You can add more than one if your business spans a few domains (a marketing site and a separate help center, for example), up to the limit shown in the guide.
If you don’t have a website, switch to the description field instead and write a few sentences about your business. The field enforces a minimum and maximum length so the description is enough to work with but not a full brief — the guide will tell you if you’re under or over.
Choose how deep to read
Once Atender maps the pages behind your address(es), it shows you what it found and asks how much of it to actually read:
- Quick — reads a smaller set of the mapped pages. Faster, good for a first look.
- Deep — reads more of what was mapped, for a fuller picture of your content.
The guide shows a time estimate for each option before you commit — for the smallest scopes that’s a matter of seconds, otherwise a small number of minutes. Whichever you pick, the pages read are exactly the pages you were shown; nothing extra gets pulled in behind the scenes.
Most pages are read directly. If a page turns out to be client-rendered — a help center that needs JavaScript to show its content, say — Atender can optionally re-read just that page with a supplementary crawler to get real text out of it. This only kicks in for pages your first read came back empty on, and it’s invisible from the guide itself.
What gets built
Once you confirm a scope, the build runs in the background and writes, from the same profile it read off your site:
- Contacts — real people and organizations drawn from your content.
- Conversations — seeded conversations that read like your own support history.
- Help articles — a starting Knowledge Base built from what your site already explains.
- Tags — categorization pulled from the same content.
- Snippets — reusable reply text in your own voice.
- Agent Stack — your AI agent configuration, built from the same profile rather than left as defaults.
Every seeded conversation lands on the human side of the inbox — it is not attributed to your Agent Stack, because the stack couldn’t actually have produced it. This matters if you’re evaluating what your AI would do: seeded history sits alongside the AI’s work rather than pretending to be it.
Resuming, cancelling, and dismissing
A build can run for minutes, so the guide is built around you not having to sit and watch it:
- Minimizing the guide (the corner chevron) collapses it back to the launcher without stopping anything. The build keeps running, and the launcher stays put as a reminder that something is happening. Minimizing is not the same as finishing — it only puts the guide away.
- Cancelling a running build stops it. Use this if you picked the wrong scope or want to start over with different addresses.
- Dismissing the guide before or after a build (rather than minimizing it) puts it away without keeping the launcher around as a nag. This is available any time the guide isn’t actively mid-build, so a cancelled or failed attempt doesn’t leave the corner bubble stuck there for the rest of the trial.
If you convert out of trial, the offer to build a demo workspace closes regardless of how far you got — it’s a trial-only feature, not something that follows you into a paid tenant.