Source identity
Receive only events from the approved inbox and verify their identity.
Support triage · interactive preview
Type a sample message and explore a suggested category, urgency signal, owner, reply and action plan. Results update locally using simple rules. No customer has been contacted and no task is actually queued.
Local planning preview
The example updates automatically using simple English-language rules. No inbox is connected, no AI model is called, and no task or message is sent. Do not paste secrets or private customer records.
97 / 6000 characters
Try an example
Text stays in this page's memory. Copying or exporting saves only the proposed planning result to your device. Refreshing the page restores the example.
Proposed result · nothing executed
Local preview: Billing or finance. No external action has run.
No provider specified. Nothing is inferred as connected.
Classification rules · Reply content and approval
Thanks for explaining the billing issue. Please share a non-sensitive reference and the outcome you are requesting so the authorized team can review it.
This script prints the proposed map in the Browser Preview. It is not an implementation of the external actions.
// Planning preview: prints a proposed map; no external actions.
let trigger = "Message supplied in this preview"
let workflow_type = "Billing or finance"
let review_required = true
print("Review this proposed workflow before connecting production")
print(trigger)
print(workflow_type)
print("Proposed: Create a support or follow-up task")
print("Proposed: Prepare a reply draft for review")
print("Proposed: Hold financial changes for explicit human review")
print("Review: Urgent language detected")
print("Review: Financial or payment action")
print("Review: Risk is not verified by this preview; authorize live connections separately")The intended production flow is automatic ingestion, policy-based triage and authorized task or reply handling, with durable duplicate protection and an audit trail. That live integration is a separate implementation and activation step—not something this demo silently turns on.
Receive only events from the approved inbox and verify their identity.
Apply explicit ownership and allowed-action rules; do not treat keyword guesses as permission.
Record actual provider results and stop safely on uncertain, duplicated or unauthorized actions.