Your assistant can answer questions, prepare updates, and help with routine website tasks — but risky changes do not happen without your approval.
Start read-only. Preview changes. Approve before publishing.
Your WordPress site is part of your business. It should not be changed blindly, automatically, or without a clear approval process.
This assistant is designed around control. It can help you understand your site, prepare small updates, replace images, publish content, and send reports — but important actions are reviewed before they go live.
The goal is simple: make WordPress easier to manage from WhatsApp without creating new risks.
The assistant does not silently make important changes to your WordPress site.
What this means
Example
If you say, "Unpublish the old offer page," the assistant first checks matching pages, shows the exact page it found, and asks for approval before changing the status.
You stay in control of what changes on your site.
Not every user needs full control. Permissions can be set based on what each person should be allowed to do.
Users can ask questions and receive answers, but cannot request changes.
Users can request updates, but someone else must approve before anything goes live.
Owners, managers, or approved team members can review and approve prepared changes.
Higher-risk actions can stay disabled, especially in the early version.
Your team can use the assistant without giving everyone full wp-admin access.
You can start safely without giving the assistant editing access.
In read-only mode, the assistant can:
In read-only mode, the assistant cannot:
You can test the assistant with almost no operational risk.
Before making a change, the assistant shows what it found and what it plans to do.
A preview may include:
Example
"I found the Services page. Current heading: 'Our Services'. New heading: 'Business Website Services'. Do you approve this change?"
You can catch wrong pages, wrong wording, or unclear requests before anything changes.
Publishing affects what visitors can see, so it should always be deliberate.
What happens before publishing
Example
"I found the blog post 'Website Maintenance Checklist'. Current status: Draft. URL will be /website-maintenance-checklist/. Do you want to publish it now?"
No accidental publishing. No wrong-page updates. No hidden changes.
Important actions can be recorded so you know what changed and when.
The activity log can include:
Example log entry
"Homepage heading updated. Approved by Sarah. Completed at 10:42 AM. Previous heading saved in change history."
You get visibility after the change, not just before it.
The early version is intentionally limited to safer WordPress operations.
Included in the early version
Not included in the early version
The assistant focuses on routine website operations, not high-risk technical changes.
The assistant can start small and become more useful only when you are comfortable.
Begin with daily health reports and site questions.
Let users request updates while keeping approval with the owner or manager.
Allow text updates, image replacements, publishing, and unpublishing after preview.
Theme, plugin, code, and critical setting changes can remain outside the assistant's scope.
A normal website change, handled with control.
The assistant helps complete the task, but you stay in charge at every step.
The assistant is useful because it removes friction without removing control.
Reduced by showing the exact page before making changes.
Reduced by previewing current and new content.
Reduced by requiring approval before publish or unpublish actions.
Reduced by using roles and permissions instead of giving everyone wp-admin access.
Reduced by limiting the early version to safer, objective WordPress tasks.
We'll review your site, explain the safest permission setup, and show what the assistant can do in read-only mode before enabling updates.
Read-only available. Approval required. No code edits in the early version.
No. Important actions like text updates, image replacements, publishing, and unpublishing require preview and approval.
Yes. You can start in read-only mode and use it only for questions, checks, and daily website health reports.
Yes. Team members can be given limited permissions, such as ask-only or request-only access.
No. The early version does not edit theme files, plugin files, or custom code.
The assistant shows a preview, confirms the target page or content, and waits for approval.
Yes. Approved actions can be recorded in an activity log with details like the action, page, approving user, and time.
It should ask for confirmation instead of guessing. For example, if more than one page matches your request, it shows the options first.
Hi there 👋
How can I help you?
