See the assistant work in context
Choose a scenario. See the page context, the conversation, and the result in one focused view.
Find a compatible product
The assistant recommends only in-catalog, compatible parts — never a guess from the model alone.
Why this worksWhen it helps, result, and technical details +
A shopper is on a technical product page where compatibility matters more than a general FAQ answer.
Two real, in-stock, compatible items — with price and availability pulled from the catalog.
- Page context ruled out incompatible AM5/DDR5 options before any search ran.
- search_products and get_product read the live catalog — no invented items.
- Both are read-only tools: they run automatically, no confirmation needed.
Tools: search_products, get_product
Check my order status
The visitor gets a real status update, and a different customer’s order stays invisible — not even its existence leaks.
Why this worksWhen it helps, result, and technical details +
A signed-in customer wants an order update without digging through email or contacting support.
A live status straight from the store, with cross-account access refused outright.
- get_order_status runs only against the signed-in customer’s own identity.
- A foreign order returns the same refusal as a non-existent one — existence never leaks.
- No tracking number is shown unless the store’s own tool actually returns one.
Tools: get_order_status
Understand the current article
A grounded answer with clickable citations, not a hallucinated summary.
Sources:
• Standard vs Advanced modes
• Security model
Why this worksWhen it helps, result, and technical details +
An article is long or uses internal terminology, and the reader wants a direct answer sourced from the site itself.
A short, sourced explanation plus a pointer to the next relevant piece of content.
- Current-page context helps interpret what "Advanced" refers to on this specific site.
- The answer is grounded in synced content, not the model’s general knowledge.
- Citations link straight back to the host’s own pages.
Tools: search_content
Get help on the current screen
The assistant already knows which integration and error are on screen — no screenshot needed.
Fix the domain under Install → Allowed origins, then re-run the check.
Why this worksWhen it helps, result, and technical details +
A user is stuck on an integration-settings screen, and a generic knowledge base doesn’t know which provider or status is currently open.
A direct diagnosis and a one-click path to the fix, grounded in the actual screen state.
- The host builds a structured screen context itself — the assistant never scrapes the DOM.
- No hidden input values or closed-form fields are ever included.
- The fix link is a host-defined navigation action, not a guess.
Tools: get_screen_context (custom)
Reschedule a booking
A real proposed change, shown before anything is saved to the booking system.
Booking moved to Friday, 4:30pm. Confirmation will be sent by the booking system itself.
Why this worksWhen it helps, result, and technical details +
A client wants to move an existing appointment without a phone call, on a site whose booking backend is entirely custom.
A confirmed new time, applied only after the client explicitly approves it.
- Context Assistant orchestrates the conversation and the confirmation step.
- Availability, booking rules and notification delivery all belong to the client’s own system.
- Nothing is written until the client picks a specific slot and approves it.
Tools: get_availability (custom), update_booking (custom)
Update product stock
A visible before/after, applied to the real store only after Apply.
Change applied.
Recorded in the action log · request req_…
Why this worksWhen it helps, result, and technical details +
The owner is already looking at a product or working the shop floor and needs a quick stock change without opening wp-admin.
Stock and status updated, with the change recorded in the action log.
- search_products and get_product ran automatically to find the item.
- update_product_stock is a write tool — it waited for an explicit Apply.
- The action is recorded in the audit log with a request ID.
Tools: search_products, get_product, update_product_stock
Create a draft from notes
A structured draft, never auto-published.
Draft created. Want to open it in the editor?
Why this worksWhen it helps, result, and technical details +
An editor already has rough notes and wants a starting structure without publishing anything by accident.
A new draft post, ready to open and refine in the editor.
- create_draft_post can never set status to published — the field doesn’t exist in its write scope.
- The editor keeps full control to revise before publishing.
Tools: create_draft_post
Moderate and answer comments
Reads run instantly; every moderation action is still its own confirmed step.
Marked as spam. This can be restored from WordPress spam.
Why this worksWhen it helps, result, and technical details +
An editor has a backlog of comments awaiting moderation and wants to triage quickly.
Spam cleared, real questions answered — each as a distinct, confirmed action.
- list_comments is a read — it runs without confirmation.
- spam_comment and reply_to_comment are separate write tools, each with its own preview — never bundled into one opaque button.
- A reply is published under the moderator’s own name, nested under the parent comment.
Tools: list_comments, spam_comment, reply_to_comment
Move old media to trash
The delete policy in action: preview, a second confirmation, and a real Restore path.
Move this file to trash?
Moved to trash. Restore from WordPress trash any time.
Why this worksWhen it helps, result, and technical details +
An editor is cleaning up old assets and wants to remove one safely, without a silent, unrecoverable delete.
The file moves to WordPress’s own trash — recoverable, not erased.
- trash_media never permanently deletes — WordPress’s own trash is the recovery window.
- A second, explicit confirmation stands between preview and the actual move.
- The preview surfaces the one page that references this file before you decide.
Tools: get_media, trash_media
Review a sales summary
A fast, read-only answer with no separate dashboard detour.
Why this worksWhen it helps, result, and technical details +
The owner wants a quick read on recent performance while already working in the store.
A real number pulled straight from WooCommerce, exactly as the store itself returns it.
- get_sales_summary requires view_woocommerce_reports — it is not public.
- It is a read tool: no confirmation needed, but gated to the right capability.
- No period-over-period comparison is invented — only what the tool actually returns.
Tools: get_sales_summary
Update a support ticket
A visible before/after on a fully custom backend — the same contract as every other integration.
Ticket updated.
Why this worksWhen it helps, result, and technical details +
A support lead is triaging tickets and wants to reassign and re-prioritize without leaving the conversation.
The ticket updated in the client’s own system, confirmed before it happens.
- The tool and its permission model are defined entirely by the client’s backend.
- Context Assistant never receives an operator credential in the browser.
- One integration reuses the same four endpoints — /tools, /context, /tools/preview, /tools/execute — as every other Remote Tools host.
Tools: update_ticket (custom)
One mechanism, every site
The site and the task change. The rules don't. The assistant only gets allowed context, only reads within the user's real permissions, and never applies a change quietly.
The same safety rules, every time
| Situation | Behavior |
|---|---|
| Searching a product, article or status | Read-only tool runs automatically |
| Creating a draft or reply | Preview, then explicit Apply |
| Changing stock, status or assignee | Before/after shown, explicit Apply |
| Moving something to trash | Preview, second confirmation, restorable |
| Someone else's order or object | Host permission check — not revealed |
| Browser embed | Short-lived token only, never an API key |
What you'll need for your scenario
| If you have… | Start with… | Status |
|---|---|---|
| WordPress / WooCommerce | WordPress plugin | Early access |
| A React app | React SDK | Available |
| Any site with JS | Script embed | Available |
| Your own backend and actions | Remote Tools contract | Available |
| A booking/CRM/ticketing action | Build a custom Remote Tools host | Not a plug-and-play connector |
| Declarative HTML5 | — | Planned |
Frequently asked questions
How are these different from a regular chatbot?
Each example shows the current page, a real conversation, and — where relevant — a before/after change that only applies after confirmation. It’s not a generic Q&A simulation.
How does it know which page is open?
Your host sends a small allowlist of structured facts — like a product ID or ticket status — configured ahead of time.
Does it read the whole page or form fields?
No. Only the allowed facts shown in each scenario’s "What is shared?" panel — never a DOM dump or form values.
Which actions happen without confirmation?
Only reads — searches, status checks, summaries. Anything that changes data always shows a preview first.
Can it change or delete data on its own?
No. Creates/updates need an explicit Apply; deletes need a second confirmation and are recoverable.
How does it know a specific user's permissions?
The host re-checks the real, current user’s role before running any action — the assistant can’t grant more access than the user already has.
Which scenarios work with WordPress/WooCommerce today?
Everything marked "Live-verified" here has been run against a real WordPress/WooCommerce site; "Implemented" scenarios exist in code but await a fresh live check before a firm public claim.
What does "Custom Remote Tools" mean?
It’s achievable through the open Remote Tools contract, but it isn’t a ready plug-and-play connector — your team implements the host.
Can I add my own booking/CRM tool?
Yes — any typed action you expose over the Remote Tools contract can be used the same way as the examples here.
What happens if an integration is unavailable?
The assistant says so plainly and stops — it never fabricates a result when a tool or data source can’t be reached.