Library-style rows with a fixed name, optional narrative, optional link, and dynamic metadata fields. Sections are grouped by a configurable key (default: Department) so cards stay organized as your taxonomy evolves.
Catalog Grid is for a uniform row shape: entry name, optional description, optional link, plus labeled metadata pairs (keys and values are CMS-defined). Sections are built from the metadata key chosen as groupByKey (e.g. Department). Use Icon Cards Grid for generic marketing tiles, Content Listing for dynamic page lists, and Detail Cards Grid when each card holds multiple sub-bullets.
Cards are shown in a responsive grid at all breakpoints—no sideways scroll. Section headings sort alphabetically.
Thirteen sample rows across departments—most include a narrative description; WPB-006 includes the link example.
Illustrative catalog: grouped by Department metadata. Optional description on a row complements the labeled fields.
Aligns evidence requests, control tests, and owner sign-off so audit periods feel predictable instead of reactive. Helps teams show a clear trail from policy to proof when regulators or customers ask how controls are operating.
Surfaces the next best reply and relevant policy snippets in the agent workspace so handle time drops without sounding scripted. Learns from resolved tickets to keep suggestions fresh and on-brand.
Keeps articles from multiplying into conflicting versions by suggesting merges, retirements, and owners when content goes stale. Reduces “which article is right?” moments for agents and customers.
Offers consistent answers and handoffs across chat and voice so simple issues resolve without a queue, and complex ones escalate with context intact. Designed for after-hours coverage without a second quality bar.
Routes work by skill, urgency, and customer segment so the right team sees it first and SLAs reflect real priority—not FIFO noise. Gives ops a lever to rebalance load when volumes spike.
Use product usage, support history, and customer engagement signals to identify accounts that may be at risk earlier, explain the likely drivers, and trigger more consistent save plays. This WPB shows how Customer Success teams can combine health scoring, churn-risk detection, workflow automation, and guided interventions to improve focus, protect renewals, and reduce surprises near renewal time.
Pulls the last quarter’s signals—usage, tickets, stakeholders—into a structured QBR draft so CSMs spend time on strategy, not slide assembly. Keeps account notes consistent so transitions between reps don’t reset the story.
Automates lineage-friendly pipelines with checks at ingest and publish so dashboards don’t quietly drift. Surfaces anomalies before they become executive surprises.
Lets leaders ask questions in plain language and get governed answers tied to approved metrics—without filing tickets to analytics for every iteration.
Scores orders and payment patterns in real time to block obvious fraud while avoiding blanket declines that hurt good customers. Balances loss reduction with checkout conversion.
Combines behavioral signals with margin-aware rules so recommendations feel helpful, not random. Tunes to seasonality and inventory so you don’t push what you can’t fulfill.
Improves search relevance and category landing experiences so shoppers find intent-fast matches. Merchandising rules stay testable without a full site redeploy for every tweak.
Delivers a concise weekly view of the metrics leadership agreed matter—same definitions everywhere, less time in reconciliation meetings. Supports “what changed and why” without a slide deck factory.