Back to the team dashboard

RESQ-X · TECHNICAL & OPERATIONS HANDOFF

LIVE TRANSACTION CONNECTION PENDING

A feed for the team.
A screen for everyone.

The office display has a dedicated operational data contract. The next step is a read-only staff feed from the system that records actual deliveries, completed Rescue jobs and Fleet OS usage. The dashboard currently shows no live actuals; its separate example mode is explicitly illustrative.

1. Connect the existing admin

Noel / Alfred: confirm the current source behind admin-fleet.resqx.ng. The documented fuel-order, Rescue-job and Fleet OS activity modules are the starting point. Their current API access has not been verified.

  1. Expose a dedicated read-only staff endpoint with the staff audience marker.
  2. Include phone, WhatsApp and partner jobs using the same stable record IDs.
  3. Return explicit status and timestamps for each source.
  4. Configure a separate staff-scoped endpoint and secret on this server.

2. Capture completion at source

Refuel: confirmed PMS/AGO litres physically delivered and customer accepted under a paid or approved-credit order.

Rescue: a unique agreed job or vehicle movement completed, customer accepted and supported by proof of delivery. Keep truck journeys and vehicles moved as separate measures.

Fleet OS: count meaningful customer workflows. Logins, test accounts and background heartbeats do not establish useful activity.

3. Preserve time and freshness

  • Use Africa/Lagos for business dates.
  • Weekly reporting runs Sunday–Saturday.
  • Output belongs to its actual completion time. Current stock and dispatch state remain separate from period totals.
  • Provide a last successful source sync and latest business-event timestamp.
  • The display checks every 30 seconds. This does not make an old spreadsheet current.
  • Never substitute zero for missing data.

4. Verify before calling it live

  1. Confirm one completed fuel delivery appears once, in the right day and product.
  2. Confirm one completed tow, its journey and vehicle count.
  3. Repeat and correct a record; totals must stay accurate.
  4. Disconnect the source; retained figures must be marked delayed or unavailable.
  5. Reconcile one day of completed jobs with the source records.
  6. Test the real TV resolution, reconnect and Lagos midnight.

The office display gets a restricted feed.

This application accepts only operational fields. Revenue, cash collections, costs, subscription billing and financial trends are excluded from its strict schema. Alerts, activity and area labels come from fixed templates. A separate owner-private management application holds the financial view. This staff application is currently private to the owner until a dedicated read-only office display session is arranged.

Product: orders, channels and people

Noel / Alfred: connect production order records and product activity with one stable order ID, a canonical customer ID, creation channel, service, event time and test/staff flags. The Product screen separates the mobile app, web dashboard and WhatsApp AI, and compares Refuel, Rescue and Fleet OS usage.

A WhatsApp order that appears in the admin queue is still one order. Registered users, active users, new users and ordering users are different measures. Active usage must represent a meaningful action; exclude test accounts, staff activity and background events.

Marketing: platform activity and real bookings

Connect Meta Ads, Google Ads, TikTok Ads, Instagram and Google Search reporting with explicit date coverage and sync times. Connect CRM enquiries, qualified leads and confirmed bookings separately. Platform conversions and messaging starts must not be relabelled as completed orders.

The connected marketing accounts can be read in ChatGPT, but a continuous connection to this application still requires an authorised reporting endpoint or export with server-side read access. Product analytics and CRM attribution also need their own verified source. Missing values remain blank.

The office contract contains aggregate activity only. Campaign costs, revenue, customer identities and unrestricted campaign names are excluded.

Developer connection contract

The existing server route is GET /api/dashboard?period=today|week|month. It reads RESQX_STAFF_FEED_URL and an optional RESQX_STAFF_FEED_TOKEN from server-side configuration. No credentials belong in the browser. The upstream adapter must return a version 2 snapshot with audience set to staff. The old combined business snapshot is rejected. Use a token scoped to this staff endpoint.

Download the integration specification

Approved target baseline

November 2026: 51,700 L PMS + 36,300 L AGO = 88,000 L; 44 completed Rescue jobs/movements. Actual figures remain blank until connected. Later months must use their own approved targets.