Work with Willo
How to ask Willo for work, what it does on its own and what it stops to check with you, and how to get good results from your first requests.
On this page
Willo's chat is where you run the business. You describe what you want in plain words; Willo works out the steps, does them, and tells you what it did. There are no modes to switch and no commands to learn.
Where the chat is
Open your business and choose Site in the left rail. The chat is on the left, beside a live preview of your site. On a phone, the chat and the preview are separate views.
What Willo does on its own
Work that's safe to run runs straight away, without asking: editing your site, adding pages, building and deploying, writing content drafts, deploying a backend function. Changes to the site's files and backend functions show in Business → Activity with an Undo.
A few actions can't be undone, or reach other people: sending an email campaign, writing to your database, deleting something, creating a Stripe product, pointing a domain. Those stop and show an approval card in the chat, and Willo waits for your yes. See What stops for your approval.
For an unclear request, Willo asks a quick question first; for a big one, it shows a checklist of the steps, then builds. For a small, clear one, it just does it.
Asking well
Good requests say what you want and why, and leave the how to Willo:
- Name the outcome. "Visitors should be able to book a call from the home page" rather than "add a button".
- Give the facts only you have. Real prices, your opening hours, the questions customers actually ask, the photos of your work. Willo won't invent testimonials, logos or figures.
- One job at a time for anything large. A redesign, then the new pages, then the email.
- Say what's wrong when something isn't right: "the headline is too long on a phone" helps more than "fix the hero".
Ask questions too. "What did you just change?", "what's on the roadmap this week?", "why did my deploy fail?", "what plan am I on?" Willo looks things up rather than guessing, and asking is free.
Before you launch
Fixing problems one at a time doesn't show how the whole app behaves once many people use it at once. Before you open an app to real customers, ask Willo "is this ready for real users?". It reviews the code and the backend for what breaks at scale (sign-ins that expire, work done twice, data one user can change for another, plan limits) and lists what it found, most serious first. It changes nothing until you pick what to fix. If your app already has people signing in, Willo offers this review on its own.
What costs credits
Chatting, asking and reading cost nothing. Work that produces something, such as research, an edit, a new page, a campaign or a coding session, uses credits. The charge is per request, not per step. See How credits work.
Who can make changes
Editors, admins and the owner get the full chat. A viewer's chat is read-only: they can ask questions and look things up, and Willo won't change anything on their turn. See Roles.
Next
- How a turn runs: sending while Willo works, stopping, and leaving the page.
- Chat threads: starting a new chat and finding old ones.
- What Willo remembers.