Capture triage ship notify
The loop closes by construction not by someone remembering
Every Signal carries forward through the workspace records that pick it up. When the linked deploy lands, the originator hears about it automatically. No human "did we tell the customer?" moment.
- 01T+0m
Captured
Source, channel, raw text, requester identity, attachments. Lands in the Signal inbox with the channel permalink intact.
SIG-441 created from #feedback · karri@acme.co - 02T+22h
Triaged
Owner, status, priority, tags, SLA. Same workspace rules, same private-team scoping, as everything else.
Owner Maya · ops.workflows · priority P2 · SLA 14d - 03T+3d
In flight
An issue, project, or sprint picks the Signal up. The Signal shows the work blocking on it; the work shows the Signal that drove it.
SIG-441 ↔ ENG-2189 · Sprint 14 · PR #2847 - 04T+9d
Shipped
The deploy that included the merged PR closes the loop. Originator gets the close-the-loop email with the change summary and deploy reference.
deploy 2026.05.14 · karri notified · loop closed
Eight intake channels one triage queue
Wherever signal lives today it lands in the same inbox tomorrow
Multi-channel intake is the point: a single triage flow over Slack, support, Zendesk, Salesforce, sales, analytics, internal notes, and public submissions, so no channel becomes its own silo with its own backlog.
Slack threads
How React with the configured emoji or run the slash command. The Signal carries thread permalink, channel, and reactor identity.
Why it matters Captures the conversation context, not just the headline. The originator can be DM'd back from the workspace.
Protected email
How Forward to signal@yourworkspace.vector.app. Threading and sender attribution are preserved.
Why it matters Customer support and partner email feed Signal without anyone copy-pasting between tools.
Zendesk
How Send signed ticket webhooks to the workspace integration endpoint. Ticket title, requester, priority, ID, and source URL become the Signal record.
Why it matters Support tickets stay connected to the engineering work that resolves them.
Salesforce
How Send signed JSON record webhooks from Salesforce Flow, Data Cloud, or a controlled relay. Record subject, contact, priority, ID, and source URL become the Signal record.
Why it matters Deal and customer-account pressure enters the same triage queue as product and support signal.
Internal notes
How Slash command in any workspace view. Capture leadership, sales, support, or internal notes before the source is forgotten.
Why it matters Internal direction stops surfacing weeks later as 'urgent priorities' with no provenance.
Analytics anomalies
How Wire an alert webhook to the Signal endpoint. The Signal carries metric, threshold, and time window.
Why it matters Quantitative signal sits next to qualitative signal. Triage one queue, not two.
Sales calls
How Drop call notes via CLI or the workspace composer. Becomes a triageable record with deal context attached.
Why it matters Deal-stage requests get prioritized against actual revenue, not just request frequency.
Public form
How Embed a Signal form in your docs or changelog. Submissions dedupe and attribute to a known customer when matched.
Why it matters Self-serve public requests without exposing the tracker or paying for a separate intake tool.
The artifact
What lands in the customer inbox the day their Signal ships
One email, sent automatically when the linked deploy closes the issue. No marketing template. No tracker URL the customer can't open. Subject, summary, deploy reference, and a reply address that files a new Signal if they have follow-up.
VectorGraph <updates@vector.app>Your request shipped: bulk-archive workflow for ops teams
Tue 14:02 · 2026-05-14Hi karri,
The change you flagged in #feedback on May 5 is now live. Bulk archive runs from the keyboard shortcut and against saved filters, so the ops team can clear a queue without opening every issue.
Reply to this email if it didn't land the way you expected. Replies file a new Signal attributed to you, so we'll see it.
Defensible attribution
Why we built that gets a one screen answer six months later
Every initiative carries the signals that drove it, the customers attached to those signals, and the deploy that satisfied them. Roadmap defenses stop being a memory exercise.
| Initiative | Signals attributed | Shipped in | Source channels |
|---|---|---|---|
| Bulk-archive workflow | 12 signals · 8 customers | ENG-2189 · deploy 2026.05.14 | Slack · Email · 1 internal note |
| Permission-map canvas guest sharing | 4 signals · 3 customers | ENG-2031 · deploy 2026.05.06 | Slack · 1 sales call |
| Doc backlinks across projects | 9 signals · 6 customers | ENG-1987 · deploy 2026.04.22 | Public form · Email |
Get started
Bring your team onto the shared work graph
Create an account, name a workspace, invite your team, connect your code, and point your agents at MCP. Start turning company context into shipped work from one shared workspace.