Product Support and Feedback Platform: End-to-End Sample Workflow

Purpose

This end-to-end workflow demonstrates every documented Product Support and Feedback Platform capability through one fictional resilient-community-retrofit case. The objective is not to prove a real-world conclusion; it is to verify the complete product workflow with controlled data.

Prerequisites

• The current product release
• A new synthetic workspace
• The all-feature CSV and JSON
• No production or private information
• Time to review every checkpoint

Sample data

This article uses a fictional Resilient Community Retrofit Program. The files contain one demonstration row for every documented feature, so each capability can be tested without private or production data.

Download CSV feature examples · Download JSON workspace example

Preview

The downloadable files include all 22 feature rows.

Procedure

Scenario

A community center is assessing energy, comfort, financing, implementation, evidence, and monitoring needs. Use only the supplied fictional records.

1. 1. Product Taxonomy: assign Product, Version, Component, Issue Type, and Release. Confirm consistent routing context.
2. 2. Support Articles: create detailed guides as sc_support_article drafts. Confirm searchable product documentation.
3. 3. Documentation Collections: group six guides into a hierarchical product collection. Confirm a browsable documentation set.
4. 4. Article Types: classify Getting Started, How-to, Troubleshooting, and Technical Reference. Confirm filtered content.
5. 5. Guided Resolution: match an endpoint error to articles, issues, releases, and next steps. Confirm a product-aware route.
6. 6. Known Issues: publish symptom, severity, state, workaround, and resolution. Confirm a public issue record.
7. 7. Release Intelligence: connect current, planned, maintenance, superseded, and retired releases. Confirm a release record with related guidance.
8. 8. Public Ideas: publish a moderated feature proposal. Confirm a public idea and official status.
9. 9. Voting: record advisory support without automatic prioritization. Confirm a bounded support signal.
10. 10. Forms and Surveys: run a documentation-usefulness survey. Confirm private responses and reviewed analysis.
11. 11. Article Feedback: collect helpful/not-helpful and step-specific comments. Confirm a quality signal.
12. 12. Failed Search Intelligence: track searches such as restore workspace. Confirm a documentation-gap signal.
13. 13. Documentation Gaps: combine search, issue, support, and feedback evidence. Confirm a ranked editorial opportunity.
14. 14. Product Onboarding: register product owners, routes, versions, components, and readiness. Confirm a support profile.
15. 15. Content Import and Export: import this JSON corpus as drafts and export governed records. Confirm an integrity-tracked batch.
16. 16. Editorial Governance: assign standards, lifecycle, reviewers, freshness, and approval. Confirm a human publication trail.
17. 17. Repository Sync: compare repository documentation with Knowledge Base coverage. Confirm a synchronization finding.
18. 18. Reliability Analytics: combine issue, incident, support-demand, and product evidence. Confirm an advisory reliability dossier.
19. 19. Platform Incidents: coordinate a cross-product public incident. Confirm an incident record and affected products.
20. 20. Cross-Product Journeys: guide users from data to analysis to decision. Confirm a connected support journey.
21. 21. Connected Operations: review dossiers, blockers, readiness, actions, and snapshots. Confirm an operations report.
22. 22. Private Support Handoff: send consented product/version/problem context to Contact and Engagement. Confirm a short-lived private handoff.

Save and review

1. Save the final workspace under the sample workspace ID.
2. Close and reopen it in a clean session.
3. Compare every feature result with the sample expected_result field.
4. Document unresolved differences and do not hide warnings.
5. Export one complete artifact bundle.
6. Send one supported handoff to an integration and verify its receipt.

Supported integrations

• Contact and Engagement Platform
• All Sustainable Catalyst products
• GitHub
• Platform Core

Expected output

• consistent routing context
• searchable product documentation
• a browsable documentation set
• filtered content
• a product-aware route
• a public issue record
• a release record with related guidance
• a public idea and official status
• a bounded support signal
• private responses and reviewed analysis
• a quality signal
• a documentation-gap signal
• a ranked editorial opportunity
• a support profile
• an integrity-tracked batch
• a human publication trail
• a synchronization finding
• an advisory reliability dossier
• an incident record and affected products
• a connected support journey
• an operations report
• a short-lived private handoff
• A complete saved workspace
• A portable export
• A validated cross-product handoff receipt

Verification

• Every CSV feature row has a corresponding saved result.
• The JSON workspace ID and product version are preserved.
• The export can be inspected without temporary browser state.
• The receiving product identifies source, destination, schema, artifact, and review state.
• A human reviewer can reproduce or audit the demonstration.

Responsible use

Public support records must exclude identity, private cases, correspondence, documents, credentials, and confidential details.

Replace synthetic data only with information you are authorized to use, after reassessing licensing, privacy, uncertainty, and review obligations.