The public site should match what you just said.

Hours, a bio, a banner, a page that still describes last season. Otto drafts it from the message. You approve it. The CMS stays where it is.

The updateFrom the message you send

The person who knows the new hour is at the desk. The login is with someone who bills the month, or with a developer who has a ticket queue.

Otto prepares the public pages, including the image and the alt text, and shows the difference before anything is live.

  • One request can cover more than one page
  • You approve the line a customer would notice
  • The publish goes through the stack you already use

The updates that usually wait.

Not a redesign. The public details that go stale between a hire, a holiday, and a promotion.

  • Copy and pages

    Headlines, service descriptions, FAQs, and a landing page, from one request.

  • Images

    A photo swap, a heavy file, and alt text, without a trip through the media library.

  • Hours, bios, contact

    The details that change when someone joins, leaves, or moves a location.

  • A date you choose

    A campaign page or a seasonal offer can wait until the morning it should be public.

Nothing public goes out unapproved.

Otto drafts. You publish the lines a customer would argue with. The rest of the request is in the log.

  • A preview first

    You see what will be different before production changes.

  • Your stack

    WordPress, Shopify, or GitHub. Otto does not ask you to move the site.

  • A reversible log

    What changed, and when, is recorded so a bad edit can come back.

The hour was wrong for eleven days.

A four-location business can have Saturday hours in the group chat and last month's hours on three of the location pages. The banner for a finished promotion can still sit on the homepage.

Otto can draft the hours, the banner removal, and the matching lines on the other pages, then wait for approval.

Example: how a four-location business could use Otto

Otto would draft the new hours, take a finished promotion down, and match the same lines on the other location pages, then wait for approval.

  • 3Location pages brought onto the same hours
  • 1Finished promotion taken down
  • 1Afternoon, not a ticket
  • 0CMS logins for that edit

Questions

What people ask before they send Otto a change.

Can I approve a website change from WhatsApp?

Yes. Message Otto the way you message a teammate. He sends a preview. You reply to approve. Nothing goes live without that yes.

What if two people send Otto different updates?

Both drafts go to the person who can approve. Nothing publishes until someone picks the version that should be live.

Can Otto change more than hours and bios?

Yes. Service copy, images, a landing page, and a seasonal offer. Layout rebuilds and new templates are not the job.