get_featurebase_stalled_promises
Find feedback posts where the customer last replied and the admin has been silent for a set number of days, enabling teams to follow up on stalled conversations.
Instructions
Find posts where admin replied, customer spoke last, admin silent for N+ days.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of stalled promises to return (1-50). Default: 20. | |
| sortBy | No | Sort order for returned stalled promises. 'staleness' (default): customerLastReplyDate desc — most-recent stalled promises first. 'freshness': adminLastReplyDate desc — most-recent admin replies first (catch up on what you just said). 'upvotes': upvotes desc — focus on high-impact items regardless of staleness. | staleness |
| status | No | Restrict candidates to posts with these statuses (e.g. ['in_progress', 'in_review'] to exclude Completed and Planned). When omitted, all statuses are eligible. | |
| teamUserIds | No | Optional override for the team-user-id set. When provided as a NON-EMPTY array, these IDs REPLACE the FEATUREBASE_TEAM_USER_IDS env var for this call only — the env var is ignored. Use this together with find_featurebase_user to run a stalled-promise query without env-var configuration. An EMPTY array ([]) is treated as ABSENT — the env var team is used if configured; otherwise stalled-promises returns immediately with teamSource='none' and a warning. Engagement fields are re-computed on the fly from cached comments using this set. | |
| minDaysSinceAdminReply | No | Minimum number of days since the admin's last reply for a post to qualify as a stalled promise. Default: 7. Set to 0 to surface every post where the customer spoke last, regardless of age. |