How Messaging Fits Into a Job

Every Vremly job carries exactly two chat channels: Customer and Team. The Customer channel is the direct line between the provider company and the booking agent. The Team channel is an internal-only thread for the company's own staff — technicians, editors, and project managers. These two channels share a single chat interface but their audiences never overlap, which means your shoot-day coordination notes stay invisible to the customer, and the customer's delivery questions stay off the internal team feed.

The separation exists for a practical reason. Real-estate media jobs involve at least three parties: the agent who booked the shoot, the technician who shows up on-site, and the back-office team (PM, editor, owner) managing delivery. Each party needs to talk to different people about different things. Blending them into one thread creates noise and erodes trust — customers do not need to read internal status debates, and technicians should not be distracted by customer billing questions.

Access to each channel is role-gated. On the provider side, Owners and Admins see both channels on every job. Project Managers see both channels only on jobs they are assigned to manage. Technicians and Editors see only the Team channel on jobs they are assigned to — they never see the Customer channel. Agents (the customers) see only the Customer channel — there is no Team tab visible to them at all. This ensures the channel split is enforced by the product, not by trust.

The two channels are colour-coded throughout the interface. In the webapp's job detail view, the Customer tab has a blue indicator and the Team tab has an amber indicator with a 'Private' badge next to it. This visual cue makes it hard to accidentally send internal notes to a customer. On the iOS app, the same colour logic applies inside the ChatView sheet that opens from an order detail.

Messages are tied to a specific job (project), not to a global inbox. You open a job and find its chat there — there is no separate messaging page. This keeps context intact: when you are reading a thread, you are always looking at it alongside the job's status, schedule, and assigned people. This is especially useful for threaded replies, where a follow-up message is visible right next to the original request without losing context about the shoot.