Support/Docs Artifact: Documentation is outdated, incomplete, and missing for key features

Problem Statement

Users across SMB, Startup, and Solo/Freelancer segments cannot reliably self-serve through the help center due to outdated screenshots, missing coverage for key integrations like HubSpot and Gmail, and absent explanations of core concepts such as triggers, conditional logic, and error codes. The absence of a getting started guide forces new users into trial and error, YouTube searches, and direct support contact. This compounds onboarding friction and increases support load, as evidenced by 18 distinct feedback items spanning multiple severity levels.

Evidence Summary

The evidence shows systemic gaps across four categories: (1) Outdated content, two Solo/Freelancer users (one MEDIUM, one LOW) explicitly report screenshots do not match the current UI; (2) Missing integration documentation, HubSpot coverage is absent per one MEDIUM SMB and one LOW Solo/Freelancer report; Gmail setup documentation is missing per one MEDIUM Startup and one LOW SMB report; (3) Missing conceptual documentation, one MEDIUM Solo/Freelancer cannot find a clear explanation of the trigger model, two Startup users (one MEDIUM, one LOW) spent over 20 minutes unable to find conditional logic setup, and one MEDIUM SMB reports no documentation on error codes; (4) Missing onboarding structure, two users (one MEDIUM Startup, one MEDIUM Solo/Freelancer) report no getting started guide, one MEDIUM SMB resorted to a YouTube video for basic features, and two users (one MEDIUM Startup, one MEDIUM Solo/Freelancer) report the FAQ feels written for power users rather than new users. Secondary signals include slow support response times reported by two Solo/Freelancer users (both MEDIUM), suggesting self-serve failure is escalating to support. Help center search returning irrelevant results is noted by one MEDIUM Startup user, reducing discoverability of any existing content.

Priority Rationale

The signal scores 75/100 with medium confidence, reflecting broad impact across all three primary user segments, SMB, Startup, and Solo/Freelancer, rather than a single edge case. The frequency of MEDIUM-severity items (13 of 18 evidence items are MEDIUM) indicates this is not isolated dissatisfaction. The compounding effect is notable: missing onboarding structure leads to support escalation, which is already showing strain via slow response times reported independently. Addressing documentation gaps is a high-leverage intervention because it simultaneously reduces support ticket volume, improves onboarding conversion, and unblocks integration adoption for HubSpot and Gmail users who currently have zero documentation coverage.

Acceptance Criteria

• A Getting Started guide exists and is accessible from the help center homepage, covering account setup, first workflow creation, and the trigger model, such that a net-new user can complete initial setup without contacting support or consulting external resources.
• All screenshots in existing documentation are updated to match the current production UI, with a verified audit trail confirming no legacy screenshots remain in published articles.
• Dedicated integration documentation pages exist for HubSpot and Gmail, each covering authentication, configuration steps, and at least one common use case, with zero open feedback items citing missing coverage for these integrations within 60 days of publication.
• A conditional logic setup article exists and is surfaced as a top-three result when a user searches 'conditional logic' in the help center search.
• An error code reference page exists documenting all workflow failure error codes with plain-language explanations and recommended resolution steps, such that users can self-diagnose a failed workflow without submitting a support ticket.

Recommended Changes

• ·Create a 'Getting Started' guide as the primary entry point in the help center, covering account setup, core concepts (triggers, actions, conditional logic), and first workflow creation, explicitly written for new users rather than power users.
• ·Audit and replace all outdated screenshots across all published articles to match the current UI, prioritizing articles about workflow setup and integration configuration based on reported user paths.
• ·Write a dedicated HubSpot integration article covering OAuth authentication, available triggers and actions, field mapping, and a step-by-step example use case.
• ·Write a dedicated Gmail integration article covering authentication, available triggers and actions, and a step-by-step example use case.
• ·Write a conditional logic setup article with step-by-step instructions, annotated screenshots, and at least two worked examples (e.g., branching based on form input and branching based on contact property).
• ·Write a trigger model explainer article clarifying what triggers are, how they fire, supported trigger types, and common configuration mistakes.
• ·Create an error code reference page listing all workflow failure codes with plain-language descriptions and actionable resolution steps.
• ·Rewrite FAQ content using progressive disclosure, basic questions first, advanced topics clearly labeled, to address the repeated feedback that the FAQ is written for power users.
• ·Audit help center article metadata (titles, tags, descriptions) for all articles covering integrations, triggers, and conditional logic to improve search result relevance for the terms users are demonstrably searching.

Open Questions

1. Is the help center search relevance issue a content discoverability problem (missing metadata, tags, or article titles) or a search engine configuration problem, and which fix is prerequisite to the documentation content work?
2. What is the current ownership model for documentation, is there a dedicated technical writer, or is this owned by product/engineering, and what process will ensure screenshots and content stay current after future UI changes?
3. Should in-app contextual guidance (e.g., tooltips or walkthroughs for triggers and conditional logic) be pursued in parallel with help center documentation, given that one MEDIUM SMB user explicitly requested in-app guidance, or is that a separate workstream?