The hardest part of a website you run by conversation is not the technology. It is the blank prompt.
People stall at that first message, and almost never because the product is difficult. They stall because a chat box has no menu, no buttons and no edges — nothing telling them what is allowed. So here is a list of things that work, written the way you would actually say them.
Start with the shape of the site
You do not need to describe a design. Describe the business and let it propose one.
- “A site for my bakery — warm, simple, a booking form, and the market photos from Saturday.”
- “Add a page about the services we offer, and put it in the menu.”
- “Write an About page. We started in 2011 and there are four of us now.”
- “Add a frequently asked questions page — use the questions people actually email us.”
If you do not like what comes back, say so plainly. “Too corporate, make it warmer” is a perfectly good instruction, and a much better one than trying to name a font.
Ask for changes the way you would ask a person
The thing that surprises people most is how little precision is required.
- “The home page is too wordy. Cut it by half without losing anything important.”
- “Make the buttons bigger — a lot of our customers are older.”
- “The text on the hero image is hard to read. Fix it.”
- “Show me what the home page looks like on a phone.”
You can also send a picture. “Here is a screenshot of a layout I like — can you do something similar?” works, and so does a photograph of a competitor’s menu.
Photos are a conversation, not an upload form
- “I have photos on my phone. Send me a link to upload them.”
- “Put the photos I just sent on the gallery page.”
- “Swap the main photo for the new one and keep everything else the same.”
They arrive optimised and correctly sized. You do not need to resize anything first, and you should not — the platform makes better versions than a phone’s share sheet will.
The three habits worth forming
Ask for a preview before you publish
You get one anyway — nothing reaches the public site until you say so — but asking for it out loud puts the link in front of you rather than in the log.
“Show me a preview before you publish anything.”
Say what you did not like, not what to do instead
“I do not like today’s changes, start again from what is live” is a better instruction than a list of corrections, and it takes one sentence. Undo is not a fallback here; it is part of how the thing is meant to be used.
“Put the site back how it was on Friday.”
Ask it what it did
At the end of a busy week this is the most useful sentence on the list.
“What have you changed this week?”
The three that people forget they can ask
About being found. “Why are we not coming up on Google for our own name?” gets a real answer about titles, descriptions and your sitemap, not a shrug.
About speed. “Is the site fast enough? Be honest.” — and it will tell you which page is slowest and what is making it slow.
About leaving. “Give me a copy of the whole site as files.” You can ask that on day one, and you should, so you know it works.
One thing it cannot do
It cannot touch anything except your website. Not your email, not your files, not another customer’s site. That is not a policy we promise to enforce — those things are not reachable from the connection at all. If you ask, it will tell you the same thing.
There is a fuller version of this list inside your console, on the Connectors screen, filtered to what your plan can actually do. If you are not a customer yet, the FAQ covers the questions that come before these ones.