Sample data. Every customer and rep name below is invented. The structure is real
(real field names, real result distribution), the people are not. Nothing here is deployed and
nothing is live.
What it is
One page a rep opens on their phone between appointments: their day, their week, their projects, and their own numbers. Intended to replace the rep-facing side of the Service Pipeline. The config screens and PipelineConfigBuilder are untouched.
- Auth0 session and AccessControlProvider, behind a new
view_fieldhousepermission - Schedule and scorecard come from the existing sales board Worker through a server-only proxy, the same pattern
/performanceand/reidalready use - Projects come from the existing pipeline configs via
/api/iwjd31ol/pipeline/pipeline-data, so rep filtering andlimited_rep_accessbehave exactly as in/servicepipeline - Sit % and Sale % are read from the sales board, never recomputed, so the two tools cannot drift on the numbers reps are judged by
- Styling uses the sales board's own tokens, so the two read as one product
Desktop
1280px, full page, scroll inside the frame
Phone
390px, full page, scroll inside the frame
Known, already on the list
- The weekly section currently renders a day strip and every row of the week, which is why the phone view runs long. It is being cut back to the strip, with a tap loading that day.
- Projects is being widened from a pending list into a full ledger with status filtering. Pending becomes one status within it.
- The disposition dropdown renders disabled on purpose. This build is read-only, with no writes to GoHighLevel, Podio or the board. Turning it on is separate work with its own design.