How to ask for what you want
Examples you can copy, plus three habits that make an assistant much more useful on a real site.
Three habits worth forming
Ask for the plan first. "Tell me what you'd change before changing anything." You get to correct the direction while it's still free.
Ask it to read back what it did. "List every line you changed, before and after." Much faster than opening each page to check.
Ask to see it. "Show me how the home page looks now." It takes a screenshot and puts it in the chat. Every edit also comes back with a preview link you can open — worth clicking before you tell it to publish.
Say where things live. An assistant that knows "pricing lives at /pricing and the plan names are in the three cards" gets it right first time.
Changing copy
On the pricing page, rename the three plans to Starter, Growth and Scale, and change the prices to $19, $49 and Contact us.
Find every page that still says beta and reword it as now available. Show me the list before you change anything.
The hero on the home page is too wordy. Give me three shorter versions and let me pick.
Building pages
Build a landing page for a webinar on 30 September: hero, agenda, speakers, and a sign-up form asking for name, email and company.
Add a customer stories page. Use the case studies starter so it comes with a collection I can add entries to later.
Copy the pricing page, call it Pricing for teams, and rework the copy for companies over 50 people.
Rearranging a page
Move the testimonials above the pricing on the home page.
The features section only has three columns of text. Add a screenshot row under it.
The "Book a demo" button on the home page goes nowhere. Point it at /contact.
Look and feel
Switch this site to the warm colour scheme and make the corners square.
Make the brand colour match #1f6feb.
Content collections
What collections does this site have, and what fields are on each?
Every post is missing a summary. Write one for each from the first paragraph, show me the list, then save them as drafts.
Publish the four posts I just approved. Leave the rest as drafts.
Starting a whole site
Create a site for a small hotel called Pine & Salt using the boutique hotel template, then show me what pages it came with.
Create a site from the blog template and rewrite the home page for a design studio in Shanghai.
Checking and publishing
Run the pre-publish checks and fix anything that's actually broken. Leave the SEO suggestions for me.
What's changed on this site since the last publish?
Publish when the checks pass.
When it needs a nudge
It asks which site every time. Tell it once at the start: "Work on the pine-and-salt site unless I say otherwise."
It invents a template or starter name. Ask it to list them first: "What site templates are there?"
It says it can't do something. Usually one of three things: the permission wasn't granted when you approved it, your role in the workspace doesn't allow it, or it's one of the things assistants can't touch.
It made up a section or block name. Ask it to look first: "What ready-made sections are there for a pricing page?" It has a list; it just has to read it.
It changed the words but the page still looks wrong. Words and settings are two different jobs. "The copy is right now — make it two columns instead of three."
What it can and can't do
The full list of what a connected assistant can change, what it deliberately can't touch, and why publishing and deleting are off by default.
Multi-language sites
Multi-language sites in Tessolo: one site and one set of pages served in several languages — what can be translated and what visitors get.