Three ways to put your AI in front of people

You have an AI that knows your work. Now it has to be somewhere people will actually meet it.

That is where most of these projects quietly die. The thing gets built, it lives on an internal page, and the people it was built for never find it. So SupaVector gives you three ways out, and you can turn any of them on or off after the fact. Same AI behind all three.

This is the whole walkthrough, start to finish. It takes about five minutes.

First, make the thing

Two fields.

A name. Whatever your visitors should see. "Acme Support", "Ask the Practice", your own name.

One sentence about what it helps with. Something like "Answer customer questions about our pricing, plans and returns policy." That sentence becomes its instructions, so a clear one beats a paragraph.

Then give it your knowledge, whichever way you already have it:

• Files. Drop in PDFs, Word documents, slides, spreadsheets, OpenDocument, EPUB, RTF, images or plain text. Old binary Office formats need re-saving as .docx, .xlsx or .pptx first.
• Pasted text. For the things that live in your head rather than a file. Policies, FAQs, the answer you have typed out forty times.
• Your website. Just the address. It reads the pages and indexes them.

Indexing starts immediately and you get your link before it finishes. It begins answering as the knowledge lands.

Way one: a link

You have this already. It appeared the moment you created the AI.

Send it, pin it, put it in your bio, print it on a card. It works on a phone, and the person opening it does not need an account unless you decide they do.

This is the right answer more often than people expect. If you are a consultant, a councillor or a creator, a link in the place your audience already looks is the whole distribution problem solved.

Way two: embedded on your own site

One script tag, pasted anywhere in the page:

<script src="https://supavector.com/embed.js" data-agent="YOUR-SHARE-ID"></script>

Your share ID is in the dashboard, and the snippet is there ready to copy with the ID already filled in, so you do not have to assemble it yourself.

A chat bubble appears in the bottom corner of every page you add it to. Someone reading your pricing page can ask a question without leaving the pricing page, which is the entire point. Nothing else on your site changes and nothing is loaded until it is needed.

It works on anything that lets you paste HTML: Webflow, Squarespace, WordPress, Shopify, a plain HTML file you edit by hand.

If you would rather control when it opens, the same script gives you SupaVectorEmbed.open("YOUR-SHARE-ID"), so you can hang it off your own "Ask a question" button instead of the default bubble.

Way three: your own domain

Put it on a domain you own, and there is no mention of us in the address bar.

That can be a whole domain, askacme.com, or a subdomain of one you already use, ask.acme.com. Both work the same way, and a subdomain is the usual choice because it inherits the trust of the domain it sits under.

Your dashboard shows two DNS records to add: a CNAME that points the name at us, and a TXT that proves you control it. Add both wherever your domain lives, then press verify. If you are using a root domain rather than a subdomain, check that your DNS provider supports CNAME flattening (Cloudflare and Route 53 do); if it does not, use a subdomain instead.

This is the version that matters if the AI is speaking for a brand. People trust an answer at your address in a way they do not trust an answer at somebody else's.

And one you do not have to send at all

The three above are ways of putting your AI somewhere. This one is people finding it without you.

There is a switch in the settings: List it in the public directory. It is off by default, and the link works exactly the same either way. Turn it on and your AI joins Explore — the directory built into the SupaVector app on iPhone, iPad and Android, which anyone can browse and search without an account or a link from you.

Switching it on asks for three things, because they are what somebody browsing has to go on:

• A category, from a fixed list. It is what the filter chips in Explore are built from.
• One line describing it, shown under the name in the listing.
• Tags, for the words people actually type. returns, shipping, billing.

Two things worth knowing before you turn it on. It takes two separate opt-ins: an AI only appears in the directory if it is reachable by link and listed, so nothing private can end up there by accident. And the directory never shows prices, on any plan — the app stores do not allow selling inside the app, so listings carry the name, the description, the category and its rating, and nothing about money.

If you have made something genuinely useful, this is distribution you do not have to work for. Turn it off later and it disappears from Explore, while every link you have already sent keeps working.

Then decide who gets in

Independent of how people reach it:

• Private while you are still testing, or permanently if it is your own notes.
• Anyone with the link.
• Anyone with an email address at your company, which is the usual answer for something internal.
• An exact list of addresses, for a client portal or a members area.

You can change your mind later and it takes effect immediately. On Brand you can go further and restrict individual documents to specific roles, so the pricing sheet your sales team sees is not the pricing sheet a visitor sees.

What to check before you send it anywhere

Five minutes of testing saves a bad first impression:

1. Ask it the three questions you get most. If an answer is wrong, the fix is almost always a missing document rather than a settings problem.
2. Ask it something you never told it. It should decline rather than improvise. That is the behaviour you want in front of customers.
3. Open your own link in a private window. That is what a visitor sees, including whether the access rules do what you think.
4. Try it on a phone, since that is where most people will meet it. The app is in beta if you want to test it there yourself.

That is the whole thing

Name it, feed it, put it where your people are. A link costs you nothing, the embed is one line, the domain is two DNS records, and the directory is one switch.

If you want the argument for why any of this matters, it is in Introducing SupaVector.

Build yours. Free to start.