Ask for a change
Say what should be different in your own words, and follow every change from asking to live on the Changes screen.
Anything you want your application to do differently starts on Changes. Say what should be different in your own words. The AI proposes a change, and you read it before anything is built. The same screen lists every change anyone has asked for, and where each one has got to.
Ask for a change
- Open your application and choose Changes.
- In the box headed What should be different?, say what you want. For example: "When a job is finished, the engineer should be able to take a photo of the boiler and add a note."
- Press Ask. While the AI works, the button reads Asking… and can't be pressed again.
You can write up to 4,000 characters. The answer appears under the box.
Editors, admins and owners can ask for changes. Viewers and finance approvers see every change but not the box. Their screen says You can follow every change here.
The answers it can give
The AI answers in one of four ways:
- What it would do. A proposed change, in a sentence, with a link to its own page. There it is saved with its conversation, and you read it and approve it. If the change removes data or can't simply be undone, a note asks you to read it carefully before approving.
- It needs to know. One question before it proposes anything, often with answers to choose from. Choose one, or type your own and press Answer. The question and your answer are kept with the change.
- Nothing needs to change. Your application already does what you asked, and the answer says how.
- This one is ours. The AI can't be reached just now. Nothing is charged, and your words are kept. This is for us to fix, so try again later.
A request that isn't about your application, such as asking it to write a letter, is turned down without a proposal. So is a request your AI budget can't cover. Nothing in your application changes in either case.
What it costs
Every answer the AI gives counts against your account's AI budget, whether or not you accept it. That includes the check that your request is about your application, any question it asks, the proposal and each reworked proposal.
Each change on the list says what it has cost so far, for example Cost so far: 14p of your AI budget. Your budget, what is left and when it resets are on Plan and billing. If the budget runs out, requests wait until it resets. You are never charged extra. See Plans and billing.
A first change to try
If your application started from a template and you haven't asked for anything yet, A first change to try offers three changes businesses like yours often make first. Choosing one puts its words in the box. Nothing is sent or charged until you press Ask, so you can edit the words first.
Follow your changes
Under the box, your changes are listed in three groups:
- Waiting for you: changes you can approve now.
- In progress: everything asked for and not finished yet.
- Done: changes that are live or closed.
Each line shows what was asked for, a status, the date and the cost so far. Open a line to see the change's page. You can't approve anything from the list itself.
The status is always one of these:
| Status | What it means |
|---|---|
| Waiting for you | A proposal is ready and you may approve it. |
| With Divvent | Your request is being turned into a change, or our team is reviewing it. |
| Waiting on Divvent | It needs something Divvent can't do yet. It comes back to be proposed again when that is built. See What the AI can't do yet. |
| Approved · not released yet | A new version is written, but it isn't running anywhere yet. Release it from Releases. |
| Live · 0.5.0 | The version this change made is running. |
| Closed · declined | The proposal was declined, with a reason. Nothing was built. |
| Closed | It was closed without anything being built. For example, someone declined it before a proposal was ready, or nobody replied for 14 days. |
A change waiting for someone whose role can approve it, but not yours, shows under In progress for you. See Read a change and approve it.
Every version
At the bottom of the screen, open Every version to see a table of every version your application has had, newest first. It shows the version number, when it was written, and who approved it: you, a colleague's email address, or Divvent. The version that is running in production is marked live.
Tips for describing a change well
The AI asks when your request leaves something open, and each question is an answer you pay for. A clear request saves a round and gets a better proposal.
- Say which record it belongs to. "Track where a customer has got to" could mean the customer, the job, or something new. Say "add a stage to each job", not just "add a stage".
- List the choices. If you want a status or a type, say what the options are: "Booked, In progress, Waiting for parts, Finished." Only you know them.
- Say who. Name the role: "Only the office can see prices", "Groomers can add notes but not delete them."
- Say when, for anything automatic. "When a booking is made, email the customer a confirmation."
- One change at a time. A small, clear change is easier to read and approve, and easier to put right. If a draft doesn't pass Divvent's checks, try saying it another way or in smaller steps.
- Use your own words. You don't need Divvent's terms. Say it as you would to a member of staff.
- Leave out real details. The AI never needs your customers' names, figures or payment details to make a change. Divvent refuses anything that looks like a card number.
If the proposal is nearly right, don't start again. Reply on the change's page, for example "Not quite: put it on the job, not the customer", and the proposal is reworked in the same conversation.