Website & digital presence
Website edits by chat
The opening hours are wrong, the new team member is missing, the price list is from last year. Nobody's happy about that. But the back end is intimidating, and the fear of breaking something comes with every click.
You'll get …
- 1
A website that stays up to date
Opening hours, team, case studies or job ads change with a single sentence in the chat – no back end, no fear of breaking anything.
- 2
A preview and approval for every change
You see in advance what will change, and it only goes live once you approve it – with a record in the change log.
- 3
Structure and design stay protected
The chat can only change the fields set aside for it. Everything else is off limits.
01Intro
Editing by chat turns this around: you write what needs changing – "we're now open until 2pm on Saturdays" – and get a suggested change with a preview. The website only changes once you approve it. Structure, design and code stay as they are.
This isn't an AI agent let loose on your website – that's where the danger would lie. Only defined fields change, and only once you've approved it. The chat also needs a clean foundation (structured content in the CMS). We check whether your website already has that – any rework needed is then part of the project, not the small print.
02How it works
- 01
Decide what should be editable
Which content do you change regularly? Opening hours, team, case studies, prices, job ads, news – the list is usually shorter than you'd think, and that's what becomes editable.
- 02
Move the content into a clean data model
The editable content becomes structured fields instead of running text in a page builder. That's the foundation – and it also shows whether the existing CMS is up to the job or needs some groundwork first.
- 03
Connect the chat and set the limits
The chat learns which fields it may change and which it never may. Every suggestion comes with a preview of how the page would look. Nothing goes live without your OK.
- 04
Try out the approval process
Who can make changes, and who approves them? In a one-person business, that's one person and one click – in a team, there are roles.
- 05
Review and extend
After a few weeks, it becomes clear which changes come up in practice. Then we adjust: add new fields, refine the writing suggestions, tighten up the log.
03Stages
The core problem – the fear of breaking something – can be solved before there's any chat at all. Each tier builds on the one before.
Starter: safe editing without a chat
Cleanly structured CMS fields plus a short guide: you only ever change content, never the structure. Often that's enough to solve the problem.
Next step: the chat editor
Edits by chat for a few clearly defined fields – with a suggestion, a preview and your approval. Copy, FAQs, opening hours.
Full build: several content types, whole team
Case studies, job ads, events, team – with roles and permissions, a change log and a draft mode for two-person sign-off.
04Try it yourself
The website of a fictional physio practice. Give one of the three instructions – on the right you see the preview, and only your approval makes the change “live”. Try the third one too.
physio münchner freiheit
Why nothing can break here: every command runs through a field check – only the approved content fields are reachable at all. And nothing is written until a human approves the preview. Everything else ends before that.
Two signals: the first is an allowed content change and runs all the way to the website. The second wants to touch the structure – and ends at the check.
05Technical implementation
- Basic principle: an API layer can only change defined CMS fields – everything else is technically out of reach.
- The language model only generates suggested changes; they're written once you've approved them (tool calls behind a confirmation step).
- The CMS depends on your setup: Webflow CMS/API, a headless CMS, a database or Markdown content – the chat sits in front of it, not inside it.
- Every change is logged – who, when, what – with the option to restore the previous version.
- Access by login only; on request, a draft mode instead of publishing directly.
- Hosting: your existing website plus a small back end for the chat and approvals.
for context · This shows how something like this usually gets built – not how it has to be built for you. What actually fits is worked out in the project: around your existing setup, your team, and what stays easy to maintain.