Documentation is outdated, incomplete, and missing for key features
Users across skill levels struggle to find clear, current documentation, screenshots don't match the current UI, core concepts like triggers and conditional logic are poorly explained, and entire integrations like HubSpot have no coverage. Many users resort to YouTube videos, trial and error, or external searches to complete basic setup tasks. This compounds onboarding friction and increases support load.
Evidence (showing 18 of 18)
"The FAQ doesn't answer basic questions. It feels like it was written for power users."
"Searched the docs for 20 minutes and couldn't find how to set up conditional logic."
"The docs don't cover the HubSpot integration at all."
"The help center search returns irrelevant results."
"I can't find clear documentation on how to set up the Gmail integration."
"The help docs are outdated. The screenshots don't match the current UI."
"The FAQ doesn't answer basic questions. It feels like it was written for power users."
"Support response time is slow. I've been waiting 3 days for a reply."
"Searched the docs for 20 minutes and couldn't find how to set up conditional logic."
"The docs don't cover the HubSpot integration at all."
"There's no getting started guide. I had to figure everything out by trial and error."
"There's no getting started guide. I had to figure everything out by trial and error."
"I can't find clear documentation on how to set up the Gmail integration."
"Support response time is slow. I've been waiting 3 days for a reply."
"The help docs are outdated. The screenshots don't match the current UI."
"I had to watch a YouTube video to understand basic features. You need better in-app guidance."
"Docs are thin. I wanted to understand the trigger model better but couldn't find a clear explanation."
"No documentation on error codes. When a workflow fails I have no idea what the error means."
Why this action type?
A score of 75 with medium confidence indicates a real, recurring pain point but not enough validated specificity yet to justify engineering or product prioritization. Routing to a Support/Docs Artifact lets the team audit what's actually missing, create or update the relevant content, and gather more precise user feedback before escalating. This keeps the issue moving forward productively without over-committing resources to a problem whose exact scope isn't fully clear.
Signal score
Scores above 75 warrant immediate action. Between 50 and 75, investigate or plan. Below 50, monitor and collect more evidence.