← All articles

AI app guides

Use visual edits for clear copy without changing the business rule

Separate a label or layout improvement from changes to what a customer action actually does.

Zocri · 2 min read · Sources checked

Decide what the change means

Lovable's preview toolbar documentation describes editing visible elements from the project preview. That is useful for refining a page, but first decide whether your request concerns presentation or behavior. Changing 'Send' to 'Request appointment' clarifies an action. Changing it to 'Confirm appointment' may promise a different outcome entirely.

Write a one-sentence description of what happens after the click today. Does the customer receive an automatic reservation, or does someone review the request? Keep that fact visible while editing. The label, success message and confirmation email should all describe the same state of the journey.

Choose the smallest coherent edit

If customers misunderstand a form, edit the heading, primary button and confirmation together. A clearer button surrounded by contradictory copy leaves the problem unresolved. Review adjacent details such as response time, whether payment is due and what the customer can do after submitting.

For layout changes, name the specific issue: the price is separated from the service, a warning appears below the action or a long name clips. Ask for a change that solves that issue. Avoid asking for a wholesale redesign when the underlying problem is one confusing relationship.

Check real content in the new layout

Use a short service title, a long one and an unavailable option. Try the page with an error message visible. A tidy preview with perfect sample text may conceal wrapping and alignment problems that appear as soon as the owner adds ordinary business content.

Then follow the action through to its result. If only the appearance was meant to change, the same record should be created with the same state and permissions. If the intended business outcome has changed, treat it as a separate functional request with explicit acceptance checks.

Give the owner a copy standard

Keep a small glossary of action words. In a consultation app, request can mean waiting for review, confirm can mean a reserved time and cancel can mean releasing that reservation. Use these words consistently across the public page, customer account and owner view.

Before publishing, ask someone unfamiliar with the app what they think the button will do. Compare their expectation with the actual result. This simple review can reveal a promise hidden in a word, without pretending that a copy edit alone proves the whole customer journey is ready.

Put it into practice.

Open Zocri →