Discussion: Commenting on the Delivery

The delivery page includes a floating Discussion bubble fixed to the bottom-right corner of the screen. Clicking the bubble opens a slide-up panel labeled 'Discussion' with a comment count in parentheses. If there are existing comments, a red badge on the bubble shows the count so clients can see at a glance that there is something to read. The bubble stays visible while scrolling the gallery, making it easy to jot a comment while reviewing a specific photo without losing place.

Comments are chronological and show each commenter's avatar, display name, and a relative timestamp (e.g., '3 minutes ago'). The comment body supports basic HTML formatting rendered via dangerouslySetInnerHTML, which means links, bold text, and lists are all readable. Adding a new comment requires being signed into Vremly — unsigned visitors see a 'Sign in to add comments' prompt with a login button that redirects back to the delivery page after authentication. Only the linked customer (the canComment flag) can post comments; org members reading the delivery page cannot comment here, though they can see all existing comments. Internal team discussion happens through the job's built-in chat channel.

The discussion thread is the recommended channel for informal back-and-forth between the client and the team while a revision is in progress. For example, a client might write 'Can you brighten photo 4?' without formally requesting changes through the approval button. The media team sees these comments by opening the delivery page preview from the job panel. A formal change request (via the 'Request Changes' button) is still the workflow to use when you want the approval status badge to change and a structured workflow to kick off; the discussion bubble is supplementary and conversational.

On the iOS app, there is no direct equivalent of the delivery discussion bubble in the current release. Team and customer communication for a job flows through the in-app chat surface in the Appointment tab of OrderDetailView, which separates team messages and customer messages into distinct channels. Agents (customer-side users) can message the team through the Customer channel. Any comments posted on the web delivery page are visible only via the web — so if a client posts a delivery comment and the team needs to respond, they should open the delivery page preview from the job detail rather than looking in the iOS chat.