Skip to content

docs(support-request-triage): require deep-linked conversation URLs in support Slack posts #176

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
dembrane-sam-bot wants to merge 3 commits into from
Closed

docs(support-request-triage): require deep-linked conversation URLs in support Slack posts #176

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
8d80de4
docs(support-request-triage): require deep-linked conversation URLs i…
dembrane-sam-bot Jul 25, 2026
87c7863
fix(trivy): ignore transitive npm brace-expansion CVE-2026-14257
dembrane-sam-bot Jul 27, 2026
1ca7e84
Merge branch 'main' into sam/update-triage-include-conversation-urls
dembrane-sam-bot Jul 27, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions src/recipes/product-support/skills/support-request-triage/skill.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -61,6 +61,7 @@ and concludes goes there, with receipts.

- Reads only; every rule in `echo-readonly-postgres` applies.
- Keep raw UUIDs and conversation/participant titles or names out of conversational Slack posts. Raw UUIDs clutter the threads, and titles/names like "John" are often PII (GDPR). Refer to them anonymously or by index (e.g. "two conversations", "first recording") instead.
- Always provide direct, deep-linked URLs to the affected conversations or chats on the echo dashboard if they are relevant to the investigation (e.g. `https://dashboard.echo-next.dembrane.com/en-US/w/<workspace_id>/projects/<project_id>/conversations/<conversation_id>`), so developers can quickly open and view them. Use Slack-style links (`<url|label>`) with descriptive labels (e.g. `<url|conversation link>` or `<url|first conversation>`).
- When resolving and presenting support request references (Project, Workspace, Org, App User) in Slack, use human-readable names and hide/omit their raw UUIDs to keep the threads clean.
- No promises about timelines to anyone; state what IS (ticket exists,
fix merged, waiting on X).
Expand Down
Loading