Send the request from your phone. Niwa checks the scope, uses the WordPress tools allowed for that role, and reports what happened. Work that needs approval stays visible before it becomes a live change.
Telegram and WhatsApp become controlled operating channels, not shortcuts around WordPress permissions.
The point
Your store should not stop because you are away from a laptop
A product needs updating. A post needs publishing later. A customer issue needs context. None of those requests should require a ritual of opening wp-admin, hunting for the right screen and rebuilding the whole task in your head.
Niwa turns Telegram and WhatsApp into controlled operating channels for WordPress and WooCommerce. Permissions, tools, previews, logs and verification are the operating layer behind it.
The loop
Request. Check. Act. Prove.
Send the job in normal language
Tell Niwa what needs changing, inspecting, scheduling or preparing. Include a product ID, page, image or deadline when it matters.
Niwa finds the relevant tool and checks the boundary
The runtime searches the available WordPress and WooCommerce tools for the current task. The connected channel identity and role decide which actions are available.
Previewable work stays reviewable
Supported admin actions can be prepared as a preview before execution. A risky request should not become a blind production write because it arrived through a chat app.
Approved work runs against the site
Niwa performs the allowed action through the WordPress runtime, not by asking you to repeat the job manually in wp-admin.
The result comes back with evidence
The useful reply is not “done.” It is what changed, what was verified and what remains blocked.
Daily workflows
The jobs that follow you away from the desk
Catalog operations
Inspect products, work with product IDs and catalog context, update store content through approved tools, and keep variant choices explicit when a product needs clarification.
Content and page work
Prepare or publish posts, work with Elementor page data and use rollback-safe page flows where the tool supports them.
Store diagnostics
Ask for current state, scheduled work, runtime health or the evidence behind a failed action before deciding what should happen next.
Customer and lead follow-up
Route founder, stock-manager and lead conversations through separate identities instead of giving every WhatsApp contact the same access.
Scheduled work
Create time-based jobs that can wake later, inspect fresh state and run the permitted action at execution time. Recurring jobs include lock, retry and stale-run recovery controls.
Messaging channels
Two front doors. One controlled operating layer.
A founder control channel that remembers the task
Niwa can receive founder work through Telegram, keep message identity across retries and return the result to the originating admin channel. Duplicate inbound updates are reserved and deduplicated before they enter the work queue.
That matters when the task is operational. A retried webhook should not publish twice or send the same customer message twice.
A linked channel with explicit roles
WhatsApp access lists separate admin, stock-manager and lead/customer-support users. Group access can be limited to approved groups and messages that explicitly address Niwa by command, mention, callback or reply.
The gateway keeps route identity attached to the message so replies return to the correct chat. Inbound raw message IDs are used for idempotency, and gateway supervision can recover a dead or stalled process without opening every conversation to admin access.
Approvals
Chat convenience does not erase production risk
A useful operator has a brake.
Niwa supports preview and execute flows for administrative work. Elementor and site-setting changes can carry previous-state data for rollback. Scheduled publishing keeps drift checks so a post that changed while waiting is not treated like the same task.
If the action changes public content, customer data, money, access or infrastructure, the site should know who authorized it and what state existed before the write.
Logs and recovery
When something fails, the answer should be inspectable
Niwa keeps high-value runtime traces for tool calls, delivery and failures without dumping every internal step into normal production logs. Queue locks, stale attempts and supervised channel processes are designed to recover instead of silently duplicating work.
Rollback still depends on the action. A content update can restore previous page data. A scheduled post can preserve its prior state. A tool that has no safe reverse action must say so before execution.
A practical example
The phone request did not bypass WordPress control. It became the front door to it.
You send
Request-to-proof
Niwa identifies the site action, prepares a reviewable version and records the schedule. At the due time, the job wakes against current site state. If the target changed in the meantime, the drift check blocks a stale write. If it runs, the reply states what was published and where it was verified.
Setup
Move one workflow out of wp-admin first
Connect Niwa to WordPress.
Choose Telegram, WhatsApp or both.
Define the founder, admin, stock-manager and customer-facing identities.
Approve the first narrow tool set.
Test preview, execution, failure and rollback paths.
Add scheduled work after immediate actions are stable.
FAQ
Before you operate from chat
Can anyone who messages the WhatsApp number control the site?
No. Admin, stock-manager and lead access use explicit role lists. Public lead access is an explicit setting, not a side effect of receiving a message.
Can Niwa work in WhatsApp groups?
Approved groups can be allowlisted. The message must address Niwa through a supported command, mention, callback or reply path.
Can I schedule WordPress work from chat?
Niwa includes scheduled self-wake and interval job flows for permitted tasks, with due checks, lock ownership and recovery controls.
Does every action need manual approval?
The boundary depends on the tool, role and risk. Repetitive read-only checks can stay fast. Public writes and sensitive actions should use preview and explicit approval where supported.
Can changes be rolled back?
Rollback-capable tools preserve previous state or a rollback record. Actions without a safe reverse path should be treated differently before execution.
What if Telegram or WhatsApp retries the same message?
Niwa carries channel-specific message identity and idempotency controls so the same inbound event does not become duplicate work.
Free messaging-workflow audit
Your phone can be the control surface without becoming a security hole
We will map the WordPress work you repeat, the approvals it needs and the proof required after each action.
Request your free messaging-workflow auditPrefer email? Write to niwa@niwachat.com with the three wp-admin tasks you most want off your desk.
