Using Team Chat to Communicate on Shoot Day

Every job in Vremly has two chat channels: Team (internal) and Client (customer-facing). As a technician you have access to the Team channel — this is where you communicate with your dispatcher, project manager, and any co-technicians assigned to the same job. The Client channel is visible to customers (agents) and to managers; as a field tech you will primarily use Team unless your manager also shares the Client channel with you.

To open Team chat on the webapp: inside the job detail, click the Discussion sub-tab inside the Task tab. By default the chat view shows. If the job has both channels visible, a sub-tab strip shows 'Client' and 'Team'. Click Team. The message composer appears at the bottom — type your message and press Enter or click the send button. Messages support rich text (bold, italic, links) via the Tiptap editor toolbar. You can also @mention any team member to trigger a notification — type @ and start typing their name.

On iOS, the chat is accessible from the Appointment tab of OrderDetailView. A 'Messages' section shows the last three messages as a preview. Tapping 'Open chat' or the preview rows opens a full-screen ChatView sheet. The sheet shows all channels available to your role (Team for technicians, Team + Customer for company managers). Tap the channel you want, compose your message, and send. Messages appear in real time for all connected users via the WebSocket gateway — your dispatcher sees your message the moment you send it.

Common field-day messages to send through Team chat include: confirming your arrival, flagging a property-access issue (locked gate, wrong address), reporting that a room needs to be skipped (furniture mover still present), or noting that you have finished and are packing up. These messages become the audit trail for the job. Avoid using text messages or WhatsApp for shoot-day comms — if a dispute arises about timing or instructions, the Vremly chat log is the authoritative record.

Replies support threading — long-press (iOS) or hover + click the reply icon (web) on any message to reply in a thread. Threads keep long conversations collapsed so the top-level channel stays readable. Use threads for multi-message back-and-forth about a specific issue (e.g., a rescheduling discussion) and keep the top-level feed for quick status updates.