Identify Bottlenecks
identify_bottlenecksRead-onlyIdempotent
Identifies revenue, operations, customer experience, and trust bottlenecks from business context, returning a public-safe summary.
Instructions
Identifies likely revenue, operations, customer experience, and trust/control bottlenecks from the supplied business context and returns a public-safe summary.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| aiIdea | No | Optional AI or automation idea the user is considering. | |
| metrics | No | Known metrics such as response time, conversion, close rate, cycle time, churn, cost, or error rate. | |
| businessType | No | Type of business being reviewed. | |
| riskConcerns | No | Concerns about customer trust, brand risk, money, privacy, compliance, or quality control. | |
| currentProblem | No | Main problem or bottleneck the user suspects. | |
| teamPainPoints | No | Internal pain points such as repetitive work, slow handoffs, rework, or unclear ownership. | |
| businessContext | No | Short description of the business model, customers, offer, team, and operating context. | |
| currentWorkflow | No | Current workflow steps, handoffs, tools, and review points. | |
| customerComplaints | No | Known customer complaints, friction points, refunds, or support issues. |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| confidence | Yes | Confidence level based on the clarity and completeness of the provided business context. | |
| bottleneckSummary | Yes | Concise public-safe summary of the most important bottlenecks. | |
| missingInformation | Yes | Information the user should provide to improve diagnostic confidence. | |
| revenueBottlenecks | Yes | Likely issues that reduce sales, conversion, qualified calls, deal speed, or revenue growth. | |
| mostLikelyRootCause | Yes | Most likely underlying cause connecting the visible bottlenecks. | |
| operationalBottlenecks | Yes | Likely issues that slow delivery, increase manual work, create rework, or reduce efficiency. | |
| trustControlBottlenecks | Yes | Likely gaps in review rules, approvals, escalation triggers, data boundaries, or quality control. | |
| customerExperienceBottlenecks | Yes | Likely issues that create customer friction, unclear expectations, slow responses, or inconsistent service. |