Public proof status

Proof and capability status for safe commerce automation.

This page separates what is ready to show, what is approval-gated, and what still needs a live proof clip before stronger public claims.

Capability matrix

What can be claimed and what still needs proof.

Capability

Status

Current proof

Next proof target

AI website widget

Proven

Public widget, install paths, and deterministic checks exist for storefront support.

Keep running production smoke checks after each deploy.

Knowledge-grounded support

Local/static proven

Answers can use store knowledge and show when a source is missing.

Add more merchant-specific policies before deeper automation.

WordPress / WooCommerce setup

Local-only / proof gated

WooCommerce page and WordPress plugin path exist, but each real store still needs connection evidence.

Capture real store setup, inbound message, inbox, and review evidence before stronger claims.

Shopify merchant workflow

Gated proof needed

Commerce workflow copy is approval-first and avoids blind risky actions; live submission evidence is still required.

Attach Shopify submission status and dev-store UAT evidence.

Approval-gated commerce actions

Gated by default

Refunds, cancellations, order edits, and discounts stay behind merchant approval rules.

Record action receipts from live merchant workflows.

WhatsApp Business

Gated proof needed

WhatsApp is not claimed self-serve production until a real session, webhook, AI reply, outbound delivery, and takeover are proven.

Prove approved sender, inbound webhook, AI reply, outbound delivery, and human takeover.

Inbound phone agent

Gated proof needed

Voice runtime and health checks exist, but live call-quality clips still matter.

Capture English and Arabic call-quality evidence.

Agent notification and reports

Local/static proven

Escalation and digest paths exist for agent review.

Tie channel notifications to verified sender and inbox proof.

Meeting booking

Controlled workflow

Booking can be treated as a low-risk support workflow with human-visible context.

Add one concrete voice or chat booking proof clip.

Review rules

Proof clips must match the public claim.

Aserva can move fast, but each public claim has to stay tied to evidence a merchant or reviewer can inspect.

Do not call a channel live until the inbound event, AI handling, outbound delivery, and human takeover path are verified.

Do not execute risky commerce actions unless the merchant has approved the workflow rule or specific action.

Do not use proof clips that hide the setup state, provider, or required verification step.

WhatsApp proof target: QR session linked, inbound webhook received, AI response created, outbound delivery confirmed, and human takeover visible in the inbox.

Start with one workflow proof.

Scan a store, connect the first channel, and keep risky actions under merchant control.

Start scan