Skip to main content
All website features

Change · Change it safely

Request a site change

Describe the change in dashboard chat. The system finds the relevant content, prepares a staged diff, and applies the approval rules for your site.

Clear before work starts

Custom-built for you.

  • Custom quote
  • You own your domain
  • No contract
  • Cancel anytime

The build, monthly management, and connected services are stated in the quote you approve.

See it work

Built from the real product.

admin.riveryoga.com/chat

River Yoga Studio

AI chat

Ready for approval

Add a Vinyasa Flow class Saturdays at 9am with Elena, link the booking page

You · 8:14 AM

Reading your events

Updating your events

Added the Saturday 9:00 AM Vinyasa Flow to your Events section:

  • Vinyasa Flow added to Events — Saturdays, 9:00 AM
  • Hosted by Elena R. (45 min)
  • Booking link set to your Mindbody page

Because it sets a time and a booking link, I saved it to the approval queue as a controlled change. Nothing is live until you approve.

Tell me what you need…

What you get

Everything in this one, done for you.

Request changes in authenticated dashboard chat
Use plain language: "add Saturday 9am yoga, $18"
Review a focused before-and-after for consequential changes
Verify the public result after an approved change ships

"Add a Saturday 9am yoga class, $18." "We're closed July 4th." "Swap the hero photo for the new patio shot." Write the request in dashboard chat instead of opening a page builder. The system reads the current site, identifies the affected content, and prepares a focused change.

Plain language, no page builder

The consequence rules still apply. Prices, links, structural work, and new claims wait for review. After an approved change publishes, the public page is checked so the result is evidence, not a success message based only on a saved draft.

How it works

From idea to live, step by step.

1

You send it in plain words

Open dashboard chat and describe the change the way you'd tell a teammate: "new closing time is 9pm," "86 the lobster roll," or "add a catering page." No special syntax or field names.

2

The agent finds the right spot

It reads your current site first, locates the exact section your message is about (hours, menu, a service), and rewrites only that, keeping everything else untouched. It never wipes content you didn't mention.

3

The change is sorted by risk

The site policy decides what can be prepared, what must wait for review, and what stays human-only. Prices, booking links, structural work, and new claims do not bypass review.

4

It goes live and gets verified

Once published, the system checks the public page to confirm the change landed, not just that it was saved. The chat returns the verified result or a clear failure state.

The difference

The old way, and the way with Strelva.

The old way

  • You log into a builder, hunt for the right page, and hope you don't break the layout dragging a box.
  • A menu change disappears into an agency queue while the old information stays live.
  • You're never sure the update actually saved, so you re-check the live site yourself.

With Strelva

  • You write one plain-language request and review the focused result.
  • The dashboard shows whether the request is staged, waiting for approval, published, or failed.
  • The system re-reads the public page and confirms the change is really there.

Illustrative operating scenario

A representative example of product behavior, not a customer case study.

In this illustrative scenario, a supplier shorts Mercato on branzino. The owner writes "take the whole-fish special off the menu for tonight" in dashboard chat. The system finds the specials block, prepares a diff that removes only that item, and waits for approval. After the owner approves, the live menu is checked and the dashboard returns the verified result.
Mercato, a 9-table Italian spot

Questions

The things people ask first.

What if I word it badly or it changes the wrong thing?

Most changes are staged, not published, so you see a before-and-after first and can reject it. Factual edits that do auto-publish are scoped to the exact field you mentioned, and the system reads your live page afterward to confirm what landed.

How quickly does a request go live?

Timing depends on the request, policy, and required approval. The dashboard shows its real state instead of promising a universal turnaround. Consequential changes wait for review.

Where do I send the request?

Use authenticated dashboard chat. SMS and email intake are not part of the current public offer.

Can it remove something I didn't mean to remove?

No. It only edits the section your message is about and preserves every other item unless you explicitly say to remove one. Deletions are treated as high-risk and never publish automatically.

See it on your own site first.

Get a clear build quote up front. You own your domain and the site.