ForemanOS™ Setup Wizard
Dial in your digital foreman once, and every call, job, and dispatch runs to spec. This guided, three-step setup locks in your revenue rules while keeping the experience fast enough to finish between jobs.
You stay in control while ForemanOS handles the busywork—revenue, intake, and dispatch, all to your playbook.
Premium color system
Primary · Foreman Orange (#F97316)
Use for the main CTA buttons ("Confirm baseline", "Advance to Step 2"), active step indicators, and key revenue numbers. It signals action and output.
Accent · Dispatch Blue (#38BDF8)
Use for links, secondary buttons ("Back", "Skip for now"), field focus states, and inline helper highlights.
Background · Ops Black (#020617)
Full-page background and nav. Creates a control-room feel and lets cards glow in the foreground.
Surface · Panel Navy (#0B1220)
Wizard cards, field groups, and confirmation panels. Pair with subtle border and shadow for a premium, hardware-grade panel look.
Text Main (#F9FAFB)
Headlines, field labels, and button text. High contrast against dark surfaces.
Text Muted (#94A3B8)
Helper copy, placeholders, legal language, and secondary labels.
Typography & interaction
Headlines · var(--headlinefont)
- H1 (page title): 56px desktop / 40px mobile
- Step titles (H2): 32px / 26px
- Group labels (H3/H4): 20–22px / 18px
Body & labels · var(--contentfont)
- Body: 16–18px, 1.6–1.8 line-height
- Field labels: 14–15px, all-caps optional with slight letter-spacing
- Helper text & legal: 13–14px in muted color
Buttons
- Label: 15–16px, medium or semibold weight
- Primary: Foreman Orange background, white text, full-width on mobile
- Secondary: Ghost button with Accent Blue border and text
Interaction states
- Focus ring: 1px border in #38BDF8 + subtle glow
- Disabled: Reduced opacity, but never gray on gray—maintain readability.
Step 1 · Universal Setup
(Architect’s Baseline)
Lock in the non-negotiables. This is where you define the infrastructure ForemanOS will follow on every call, job, and dispatch—before we get into advanced logic.
Form title
Recommended: "ForemanOS™ Infrastructure Blueprint"
Why: Signals that this is a one-time, high-leverage configuration—not just another form.
Welcome message
Current: "You manage the job site. ForemanOS manages the revenue. Let’s get your digital foreman ready to clock in."
Upgrade:
"You run the crew. ForemanOS runs the revenue.
Set your baseline once and your digital foreman will handle intake, routing, and revenue protection on every call—exactly to your standards."
Legal consent checkbox (mandatory)
Label (concise):
"I agree to receive automated SMS/voice updates for ForemanOS installation and system management."
Inline helper (muted, below checkbox):
"Used only for configuration updates, go-live alerts, and critical system notices. No marketing blasts."
UX tweaks for Step 1:
- Show an estimated time: "~60 seconds to complete this step."
- Disable the primary button until the checkbox is checked and show a small inline error if they try to proceed without it.
- Primary button label: "Confirm baseline & continue"
- Secondary link (top-left of card): "Exit setup" with a confirmation modal, not an immediate exit.
Completion-rate boosts for Step 1
- Keep this step to a single, clean card with minimal scroll.
- Show a single, reassuring line beneath the primary button: "You can edit these settings at any time from your ForemanOS dashboard."
- Auto-focus the first field on load and allow Enter to advance once fields are valid.
- If abandonment is high, add a subtle "Save & finish later" link in the lower-left corner.
Step 2 · Interactive Logic (Gatekeeper, Intake & Dispatch, Revenue)
This step teaches ForemanOS how to behave in the field. Present each section (A, B, C) as its own compact card with a clear label, short description, and tight field groupings. Conditionally show sections based on Pro/Elite tier, but keep the progress bar global so users always feel momentum.
Section A · The Gatekeeper Core (All plans)
Frame this section as the rulebook your digital foreman will enforce on every call—when to pick up, where to send jobs, and what to refuse automatically.
Operating Hours (multi-select)
Label: "When should ForemanOS cover your lines?"
Options copy:
- "24/7 primary coverage"
- "After-hours only"
- "Backup during business hours"
Helper text: "We’ll only answer and route calls during the windows you select."
Service Zip Codes (open text)
Label: "Where do you want jobs?"
Placeholder: "Example: 75001, 75002–75005 (comma or range)"
Helper text: "We’ll auto-filter out calls outside this service area profile."
The "Hard No" List
Label: "Jobs you never want booked"
Placeholder: "Example: Septic, new construction, warranty-only calls"
Helper text: "ForemanOS will politely decline these so your techs stay on profitable work."
Emergency Triggers (multi-select)
Label: "What counts as an emergency for your team?"
HVAC examples: "No heat", "No cool", "System won’t turn on"
Plumbing examples: "Burst pipe", "Active leak", "No water"
Helper text: "We’ll fast-track these jobs according to your dispatch rules in the next section."
UX tweaks: Use short, inline chips for multi-selects and show a small summary line at the bottom: "Emergencies defined: 3 • Zip profiles: 2 ranges • Hard ‘no’ jobs: 4".
Section B · Rapid Intake & Dispatch (Pro/Elite)
This card only appears for Pro and Elite accounts. Use a subtle "Pro feature" pill in the top-right corner to set expectations.
CRM Bridge (dropdown)
Label: "What system should ForemanOS sync with?"
Options: Jobber, Housecall Pro, ServiceTitan, Other
Helper text: "We’ll match jobs, customers, and revenue back to your source of truth."
UX: If "Other" is selected, slide down a short text field: "What platform do you use?"
Dispatch Fee (short text)
Label: "Standard dispatch / diagnostic fee"
Placeholder: "$89 diagnostic fee"
Helper text: "Shared on calls and SMS so customers know what to expect before booking."
Technical Specs (3 questions)
Label: "What should we ask before we book?"
Helper text: "Add up to 3 questions your techs need answered before rolling a truck."
Examples: "How old is the unit?", "Is the system currently running?", "Any previous repairs in the last 12 months?"
Human Failover Contact
Label: "Emergency human escalation number"
Placeholder: "(555) 555-1212"
Helper text: "We’ll route edge cases and system exceptions here so no critical call is ever dropped."
UX tweaks: Use a small inline counter like "Questions added: 2 / 3" and allow reordering via drag on desktop and simple up/down controls on mobile.
Section C · The Revenue Drive (Elite only)
Elite users get a revenue command center. Highlight this with an "Elite" pill and a subtle glow or gradient border.
Review Timing (slider)
Label: "When should we ask for a review after the job?"
Helper text: "Too soon feels pushy. Too late gets forgotten. Most shops perform best between 2–6 hours."
UX: Show a live readout like "Ask for a review: 4 hours after job completion" above the slider handle.
Slow Season Activation (month picker)
Label: "When should we ramp tune-up/reactivation campaigns?"
Helper text: "We’ll warm up your customer list ahead of your slow season so techs stay booked."
UX: Allow selecting one or multiple months and show a short summary line below.
Revenue Benchmarks
Label: "Current average ticket" & "Weekly job volume"
Placeholders: "$650", "25 jobs/week"
Helper text: "We use this to calibrate your ForemanOS HUD so you can see lift, not just activity."
UX: Consider showing a small projected impact hint: "Even a +10% lift here adds ~$X/week."
Step-level UX: Keep a single primary CTA at the bottom of the whole step: "Lock in logic & continue", and a secondary text button: "Back to Universal Setup".
Step 3 · Installation Complete
The final screen should feel like a system handoff, not a generic "thanks" page. Use confident language, clear next steps, and reassure them the system is live or going live shortly.
Redirect URL
Keep: https://foremanos.net/installation-pending
Style this page as a status HUD that confirms their configuration is in the queue and clearly states what happens next.
Final screen text
Current: "Configuration received. We are plugging in your infrastructure now. Expect a 'System Live' SMS within 24 hours."
Upgrade:
"Configuration received. Your digital foreman is clocking in.
We’re wiring your rules into ForemanOS—intake, dispatch, and revenue guardrails.
What happens next:
- You’ll get a ‘System Live’ SMS within 24 hours.
- We’ll send a quick test call/SMS so you can see your rules in action.
- Your ForemanOS dashboard will update with your new revenue HUD once live."
UX refinements on completion
- Replace the final button label with "Return to dashboard" or "View ForemanOS console" instead of a generic "Done".
- Show a subtle summary of their key choices: coverage hours, CRM, dispatch fee, and review timing.
- Add an unobtrusive link: "Need to adjust something? Edit your setup in Settings → ForemanOS Wizard."
- Consider a small, single-question NPS-style prompt: "How clear was this setup?" with 1–5 rating, to inform future iterations.
Global UX improvements across all steps
- Persistent progress indicator: Keep the hero-style progress pill at the top of the wizard card on every step with "Step X of 3" and a visual bar.
- Mobile-first layout: Stack cards vertically with full-width buttons. Keep primary CTA pinned to the bottom viewport on mobile for thumb reach.
- Error handling: Use inline, field-level errors in muted orange with clear fixes ("Add at least one zip code" instead of "Invalid input").
- Autosave: Autosave on blur and step change. If a user returns, drop them back into their last incomplete step with a subtle banner: "We saved your previous setup—picking up at Step 2."
- Action-focused button labels:
• Step 1: "Confirm baseline & continue"
• Step 2: "Lock in logic & continue"
• Step 3: "View ForemanOS console"
- Keyboard + accessibility: Ensure logical tab order, visible focus states in Accent Blue, and ARIA labels on progress and step headings.
INDUSTRIES
INDUSTRIES
