Webhook 500s on Stripe sandbox
from support@acme · 3m agoENG · Payments · @maya
Capture from Slack, email, and public forms; route intelligently with rules and AI; auto-dedupe against an active backlog of millions.
Sources
Webhook 500s on Stripe sandbox
Add dark mode to public dashboards
SAML login fails for enterprise.io
Bulk import CSV for projects
Intake in short
How intake works
Every request — feature ask, bug report, customer escalation, design feedback — lands in the same calm inbox. The AI gateway reads the body, scans your existing backlog with semantic search, suggests duplicates, attaches the most likely team and label, and proposes a priority. Your triager confirms in one keystroke, or rewrites with full context already drafted. No more 6am pings asking who owns this. No more "I already filed that one." Triage that used to eat the first hour of the day finishes before your second coffee, and every decision is auditable — model, prompt, output, reviewer, timestamp. Nothing gets routed silently. Nothing gets lost.
A rule engine that reads like English: when a request mentions "auth" or "SSO", assign Maya; when source is "support@", set SLA to 4 hours; when reporter belongs to enterprise tier, escalate to the on-call. Compose with AND/OR, scope by workspace or project, attach actions in any order — assign, label, link, comment, move, notify. Rules run inside the same transaction as the write, so you never see the unrouted state. Dry-run mode previews matches against the last 30 days of intake before you ship the rule live. Every fire is logged with the matching condition tree, so debugging a misroute takes seconds, not afternoons.
A public intake form with the calm of a marketing page and the rigor of an issue tracker. Brand it with your logo, accent color, and helper copy; add typed fields (single-select, multi-select, text, date, attachment); require sign-in or accept anonymous. Submissions arrive in your workspace as draft issues with submitter metadata, attached files preserved, and the original form values pinned for context. Embed the form on your docs site, your status page, or your CRM — the realtime channel is the same as your internal flow. Customers see what you see.
Every request links back to the customer record — contract value, plan, last NPS, open incidents, named CSM. Triage decisions weigh customer context automatically: a feature request from a Pro account routes through one path, an enterprise blocker through another. Aggregate by customer to see total open asks, by feature to see voting weight, by team to see who owes whom. Close the loop with a single click — the issue resolution emails the requester with your release notes and changelog entry attached.
FAQ
How capture, AI triage, routing rules, and dedupe actually work on a real backlog.
Stop losing requests. Triage them.— Free plan, no card.