Lesson 1 of 10 · 3 min

The Agent's Job View: My Orders at a Glance

Understand how agents (real-estate customers) see their jobs in the My Orders view, including the stats bar and tab-filtered list.

The Agent's Job View: My Orders at a Glance

Video coming soon

1/10

Lesson Notes

01

When you sign in as an agent — a real-estate professional who books media services — the jobs surface is labeled 'My Orders,' not 'Projects.' This distinction matters: from the agent's perspective, each job is an order they placed, not an internal production task. The view lives at /jobs and is driven by the AgentJobsView component, which the backend scopes entirely to projects where the signed-in user is the customer or project manager. No additional frontend filtering is applied — the backend already returns the right slice.

02

At the top of the My Orders page, a stats bar displays four live counts: Pending (booked but no technician confirmed), Assigned (technician locked in), In Progress (shoot underway), and Completed (delivered). These counters update each time the page loads, giving agents an instant read on their pipeline health without scrolling through the list. The stats are derived directly from the backend-provided jobs array so they always match the tab counts below them.

03

Below the stats bar is a tab strip with five tabs: All, Pending, Assigned, In Progress, and Completed. Each tab is a filtered view of the same dataset — the count in parentheses next to each label updates live. Agents can switch tabs to focus on one stage without losing the full picture. The table headers visible in list mode are: Property, Client, Scheduled, Media Types, Priority, Status, Payment, Technician, and Actions. The Payment column is unique to the agent view and shows the invoice status (paid, outstanding, etc.) alongside the job status.

04

Agents can also see a 'Create Order' button in the top-right corner. Clicking it navigates to /booking, beginning a new job request. This is the only action-oriented button agents see at the list level — agents cannot change job status, assign technicians, or delete jobs from this view. Those mutations are gated to provider-side roles. On the iOS app (OrderDetailView), the agent experience mirrors this: the app fetches /projects/mine and presents the same four-stage breakdown with the same restriction that agents cannot mutate status or team assignments.

05

Each job card in the My Orders list has a 'Book Again' shortcut. Tapping it prefills the /booking flow with the same address and package as the source project, letting agents quickly re-order for a second visit or a follow-up shoot without starting from scratch. On mobile, the same flow is triggered from the Order Detail's action row.

Key Takeaways

  • Agents see 'My Orders,' not 'Projects' — the backend scopes the list to jobs where the agent is the customer.
  • The stats bar (Pending / Assigned / In Progress / Completed) gives a four-number pipeline summary without scrolling.
  • Five tabs filter by stage; the Payment column shows invoice status alongside job status.
  • Agents cannot change status or assign technicians — those controls appear only for provider-side roles.
  • The 'Book Again' button lets agents re-order with one tap, prefilling address and package from the original job.
Related documentation at docs.vremly.com