Which AskVault plans support rich UI cards?

Growth and above. The Generative-UI feature that lets the agent dynamically select and populate card templates is a Growth+ capability. Starter workspaces see plain text fallbacks.

Do AskVault rich UI cards work on all channels?

Yes, with automatic degradation. The widget and hosted page render the full card UI. WhatsApp renders interactive reply buttons. Slack uses Block Kit. SMS and email fall back to readable text, never raw JSON.

Can I create custom card types in AskVault?

On Enterprise. Custom card schemas can be registered and then emitted by custom skills. The rendering pipeline applies the same cross-channel serialization logic as the built-in card types.

Rich UI cards: one definition, every channel

The idea

Most chat platforms render rich UI in their web widget only; everywhere else the customer gets a wall of text. AskVault's Universal Card System defines each card once, in a single canonical model, then serializes it to each channel's native format, so the same "where's my order?" answer renders as:

a timeline card in the web widget and hosted page,
inline keyboard buttons on Telegram,
a Block Kit message on Slack,
an interactive reply (or a link in-text) on WhatsApp,
styled HTML in email,
clean markdown with citations inside ChatGPT, Claude Desktop, or Cursor (via MCP),
and a Google A2UI surface for A2UI-aware clients.

A channel that can't express a particular card degrades gracefully to readable text, never raw JSON, never a dropped card.

Card types

AskVault ships 10 built-in card kinds today. The table below lists each one and what it renders.

Kind	What it shows
`product_card`	A product/result with image, price, action buttons
`carousel`	A row of product cards
`form`	A small data-capture form
`action_chip`	A single inline action button
`info_card`	A titled card with markdown body + footer actions
`cart_recovery`	Abandoned-cart card with a concession + checkout CTA (not emitted yet: the Shopify cart lookup is not wired)
`scheduler`	A booking card with selectable time slots
`wismo_timeline`	An order-tracking timeline ("where is my order?")
`confirmation`	A propose-then-confirm prompt for mutating actions
`collect_info`	An editable intake form (name/email/phone by default) that posts straight to lead capture

These are emitted by the built-in skills (order status, cart recovery, scheduling, and others) and by the Generative-UI feature for Growth+ workspaces. See Business DNA vs. flow builder for how the agent decides which skill to invoke.

Confirmations for mutating actions

When the agent is about to do something that changes state (apply a discount, cancel a subscription, modify an order) it does not act immediately. It emits a confirmation card ("I'll apply a 10% discount. Proceed?") with Yes/Cancel. Only after the customer confirms does the action run. Because it's a canonical card, that confirmation renders as native Yes/Cancel reply buttons on WhatsApp, a Block Kit prompt on Slack, inline buttons on Telegram, and the widget's confirmation card, not just in one place. The mutating action only runs when the agent re-issues that exact request with the customer's confirmation attached. An unanswered card just sits there; nothing fires on its own.

Rolling out: AskVault runs the confirmed action itself. The customer's own Yes (a tap, a typed "yes" in their language, or CONFIRM by SMS) is checked by AskVault, not by the AI, and runs exactly the action shown on the card, once. The AI can't confirm on the customer's behalf, a second tap finds nothing left to run, and a No cancels the card. Any other reply runs nothing, and the card expires after 10 minutes. The agent also remembers what it did earlier in the conversation, so it doesn't ask again or repeat an action it already ran.

Theming

Cards in email replies are themed per workspace using W3C Design Tokens (DTCG 2025.10): your brand colour sets the accent for all 10 card kinds. The same token theming for web widget cards is still rolling out; until then widget cards use the widget's built-in style. (Chat platforms like WhatsApp, Slack, and Telegram are styled by the host app, not the sender, so theming there is structural only: which buttons, how many; never colours.)

Compliance-strict workspaces can switch specific card kinds off in Settings → Agent Surfaces. Today a switched-off card arrives as plain text on WhatsApp, Slack and Telegram, and is left out of email replies; the web widget, the hosted chat page and the dashboard chat follow when that rollout completes.

A2UI compatibility

Not generally available AskVault can export any card as a Google A2UI surface (pinned to v0.9, the current feature-complete version) for agent-native clients that render A2UI. This is an optional, version-pinned output target, isolated so the spec's pre-1.0 churn never affects the rest of the platform, not our internal model. It is off unless we switch it on for your account. When it is on, A2UI-aware agents discover it at:

GET  /api/a2ui/{workspace_id}          # discovery (protocol + pinned version)
POST /api/a2ui/{workspace_id}/ask      # answer + A2UI v0.9 surfaces for any cards

The answer text is always returned, so non-A2UI clients still get a usable reply; the a2ui array carries one v0.9 surface envelope per rich card. We'll re-evaluate deeper A2UI investment once the spec reaches a stable v1.0 release.

Why this matters

Competitors render rich UI in their widget and fall back to text everywhere else. AskVault speaks each channel's native language: tappable buttons where the medium supports them, clean markdown where it doesn't, from one card definition. Your agent's intelligence reaches the customer in the right shape on every surface they actually use.