NoeVault Snip My Requests and Conversation Guide

SoR: SupportTicket list/detail + comments
Transport: Soft polling via createConversationPoller — no SignalR in v1

My Requests

Surface	Implementation
External SDK	Overlay list + client search (`listMyRequests`)
Native Panel	SnapWorkspace My Requests / organisation requests

Continuity is based on ExternalRequester identity for external hosts, not on a Panel UserUID.

Request detail

Detail projection includes status, description, attachments, and conversation comments. Activity/timeline may be richer for staff than for customer projections — do not invent a second timeline store in the client.

Conversation

Customer comment (ExternalRequester, empty UserUID)
Operator reply (NoeUser UserUID)
        │
        ▼
createConversationPoller → GET detail (soft interval)

Rule	Behaviour
Live updates	Polling
Edit/delete/reactions in SDK	Not required for v1 customer path
Actor labels	PR-8.7E.4A precedence (ExternalRequester ≠ System)

Operator workflow (Panel)

Open SnapWorkspace / Support ticket.
Review evidence download.
Reply in conversation.
Update status (Open / In Progress / Resolved / Closed / Escalated) as process requires.

NoeVault Snip

NoeVault Snip My Requests and Conversation