Successful-job referral moment
A0000366
Confirm the prompt is private, non-pushy, after-service only and does not promise rewards, discounts or automatic outreach.
A0000354
Admin-only operational memory for pilot launch notes, known issues, limitations, workarounds and manual decisions. This page does not publish complaints, score providers, auto-send messages or trigger automated escalation.
Admin dashboardPilot launch QAManual review queueSupport templates
Enhances public trust messaging for local recommendations: human review, device privacy, provider checks, support escalation, permissioned real stories and safe referral confidence. This is a copy and QA layer only.
NEEDS REPAIR
8 passed / 27 warnings / 20 failures
6 trust sections, 8 guardrails.
Helpful note
Adds manual after-service follow-up prompts for check-ins, repeat help, safe referrals and future story candidates. It strengthens referral growth without automatic outreach or marketplace mechanics.
NEEDS REPAIR
25 passed / 0 warnings / 19 failures
Manual, private, repeat-use and referral-friendly.
Helpful note
Adds a private, non-pushy referral prompt after helpful customer moments. It encourages word-of-mouth without rewards automation, public reviews, auto-send outreach, rankings or marketplace mechanics.
NEEDS REPAIR
22 passed / 12 warnings / 6 failures
Optional, private, trust-led and human-reviewed.
Helpful note
Turns private pilot feedback, customer confusion, support confidence notes, provider readiness signals and route friction into a manual admin insight view. Nothing is published, escalated or sent automatically.
NEEDS REPAIR
21 passed / 7 warnings / 7 failures
Helpful note
Checks whether customer-facing local coverage copy is clear, human-reviewed and connected to admin QA without implying automatic dispatch or guaranteed availability.
NEEDS REPAIR
13 passed / 12 warnings / 6 failures
Helpful note
A single admin starting point for existing pilot QA pages, support checks, route confidence, provider readiness, trust/safety and handover notes. It consolidates links and visibility only; it does not automate operations.
NEEDS REPAIR
11 passed / 25 warnings / 7 failures
Plain-English customer request wording for what to include, what not to include, how human review works, and how to add details later. It improves confidence without changing booking, dispatch, quote, provider or escalation mechanics.
NEEDS REPAIR
15 passed / 13 warnings / 5 failures
5 customer-facing guidance sections and 6 guardrails.
A customer-facing trust layer for human review, safe detail handling, permissioned proof, support clarity and manual resolution paths. It improves public confidence without adding ratings, rankings, quote comparison, public complaint walls, auto-booking or auto-dispatch.
NEEDS REPAIR
11 passed / 0 warnings / 18 failures
5 trust and safety sections, 6 guardrails.
A private admin handover layer for launch position, daily operator rhythm, customer support memory, provider follow-up, known issues and end-of-day closeout. It helps humans keep operational context without automating escalation, assignment, outreach or publishing.
NEEDS REPAIR
17 passed / 0 warnings / 13 failures
6 manual sections and 5 reusable note templates.
Provider-facing completion guidance across profile, services, verification, availability, proof and support paths. This is manual readiness support, not ranking, bidding, auto-booking or automatic assignment.
NEEDS REPAIR
29
11
0
18
Provider-facing completion guidance across profile, services, verification, availability, proof and support paths. This is manual readiness support, not ranking, bidding, auto-booking or automatic assignment.
NEEDS REPAIR
29
11
0
18
Plain-English support reassurance across support, Quick Help, customer journey and next-step pages. All actions remain human-reviewed and manually handled.
NEEDS REPAIR
28
10
5
13
One operator-facing launch-day view for readiness, support, route confidence, provider checks and known issue handling. It summarises existing manual tools without creating automation.
NEEDS REPAIR
0 passed / 28 warnings / 2 failures
Customer-facing service, Quick Help, support, journey and next-step confidence copy for the controlled pilot.
NEEDS REPAIR
10 passed / 22 warnings / 3 failures
Use this as the pilot team's retained note trail for issues, workarounds and launch decisions before changing customer-facing copy or workflows.
New / needs first look
Watching during pilot
Workaround available
Fixed, pending re-check
Resolved / note retained
| Issue | Status | Category | Impact | Manual workaround | Owner/source |
|---|---|---|---|---|---|
| Customer unsure what happens after submitting help request MEDIUM | WATCHING | Customer confusion or wording gap | May create duplicate support messages or anxiety during pilot. | Point customer to the What Happens Next timeline and keep replies in the same support thread. | Support/admin A0000352 timeline polish |
| Pilot feedback needs manual triage before reply MEDIUM | WORKAROUND | Support or triage flow issue | Useful feedback may sit beside urgent support issues unless reviewed daily. | Use Manual Review Queue QA and Support Triage Response Templates before sending any reply. | Admin reviewer A0000347/A0000351 |
| Route health should be checked after launch changes LOW | WATCHING | Route, page or fallback issue | A broken public or customer route could reduce trust during pilot. | Review the Post-Launch Route Health Monitor after each upload or live config change. | Site admin A0000350 route health monitor |
| Provider profile confidence needs human review before wider use MEDIUM | WATCHING | Provider readiness or profile confidence | Provider pages should feel trustworthy without implying scores or rankings. | Use provider readiness and commercial confidence QA before sharing provider profile links. | Provider ops A0000353 provider confidence polish |
| Pilot operating decisions need one retained admin note trail LOW | NEW | Admin manual workflow friction | Decisions and workarounds can be lost across support, feedback and QA pages. | Record known issues, decisions and limitations here before changing customer-facing copy. | Pilot lead A0000354 known issues register |
| Area | Status | Check | File | Detail |
|---|---|---|---|---|
| A0000354 | FAIL | Canonical pilot known issues helper exists | source/thefixersapp/includes/pilot_launch_known_issues_helper.php | Missing canonical helper. |
| A0000354 | WARN | Old-root helper wrapper exists | source/includes/pilot_launch_known_issues_helper.php | Wrapper missing. |
| A0000354 | FAIL | Admin known issues register exists | source/thefixersapp/admin/pilot-launch-known-issues/index.php | Missing admin register page. |
| A0000354 | WARN | Old-root admin register wrapper exists | source/admin/pilot-launch-known-issues/index.php | Wrapper missing. |
| status | PASS | Register status available: New / needs first look | known issue statuses | Manual status supports admin review without automation. |
| status | PASS | Register status available: Watching during pilot | known issue statuses | Manual status supports admin review without automation. |
| status | PASS | Register status available: Workaround available | known issue statuses | Manual status supports admin review without automation. |
| status | PASS | Register status available: Fixed, pending re-check | known issue statuses | Manual status supports admin review without automation. |
| status | PASS | Register status available: Resolved / note retained | known issue statuses | Manual status supports admin review without automation. |
| category | PASS | Register category available: Customer confusion or wording gap | known issue categories | Category supports operational triage. |
| category | PASS | Register category available: Support or triage flow issue | known issue categories | Category supports operational triage. |
| category | PASS | Register category available: Route, page or fallback issue | known issue categories | Category supports operational triage. |
| category | PASS | Register category available: Provider readiness or profile confidence | known issue categories | Category supports operational triage. |
| category | PASS | Register category available: Admin manual workflow friction | known issue categories | Category supports operational triage. |
| category | PASS | Register category available: Pilot decision, limitation or operating note | known issue categories | Category supports operational triage. |
| seed note | PASS | Starter note pattern: Customer unsure what happens after submitting help request | seed known issue notes | Starter note has safe title and workaround. |
| seed note | PASS | Starter note pattern: Pilot feedback needs manual triage before reply | seed known issue notes | Starter note has safe title and workaround. |
| seed note | PASS | Starter note pattern: Route health should be checked after launch changes | seed known issue notes | Starter note has safe title and workaround. |
| seed note | PASS | Starter note pattern: Provider profile confidence needs human review before wider use | seed known issue notes | Starter note has safe title and workaround. |
| seed note | PASS | Starter note pattern: Pilot operating decisions need one retained admin note trail | seed known issue notes | Starter note has safe title and workaround. |
| connection | WARN | Admin dashboard navigation connected | source/thefixersapp/admin/index.php | Optional page missing. |
| connection | WARN | Admin readiness summary connected | source/thefixersapp/admin/live-readiness-dashboard-summary/index.php | Optional page missing. |
| connection | WARN | Pilot launch QA pack connected | source/thefixersapp/admin/pilot-launch-qa-pack/index.php | Optional page missing. |
| connection | WARN | Manual review queue QA connected | source/thefixersapp/admin/admin-manual-review-queue-qa/index.php | Optional page missing. |
| connection | WARN | Support triage templates connected | source/thefixersapp/admin/support-triage-response-templates/index.php | Optional page missing. |
| connection | WARN | Post-launch route health monitor connected | source/thefixersapp/admin/post-launch-route-health-monitor/index.php | Optional page missing. |
| connection | WARN | Customer timeline QA connected | source/thefixersapp/admin/customer-what-happens-next-timeline-qa/index.php | Optional page missing. |
| connection | WARN | Provider confidence QA connected | source/thefixersapp/admin/provider-profile-commercial-confidence-qa/index.php | Optional page missing. |
| database | FAIL | Current-only SQL file exists | source/database/a0000354_pilot_launch_notes_known_issues_register.sql | Current build SQL missing. |
| database | WARN | Database folder only carries current build SQL | source/database | SQL files found: 0. |
| guardrail | PASS | Admin-only known issues and launch notes; do not publish customer complaints or private feedback publicly. | manual-only | Preserved. |
| guardrail | PASS | Manual register only: no automatic escalation, auto-send, dispatch, provider assignment or external monitoring dependency. | manual-only | Preserved. |
| guardrail | PASS | Known issues must record safe workaround language without requesting passwords, card details or sensitive data. | manual-only | Preserved. |
| guardrail | PASS | Provider-related notes must not become public scores, rankings, ratings, quote comparisons or lowest-price competition. | manual-only | Preserved. |
| guardrail | PASS | Use safe fallback messages if database, config or optional helper files are unavailable. | manual-only | Preserved. |
| guardrail | PASS | Preserve support email/thread continuity and keep customer updates in the same reference where possible. | manual-only | Preserved. |
Helpful note
Gives launch operators a single manual checklist for customer follow-up, provider readiness, support issues and handover notes without creating automated outreach or escalation.
NEEDS REPAIR
13 passed / 6 warnings / 7 failures
One admin checkpoint for the successful-job referral moment, manual follow-up, local trust/safety, support confidence and real-story readiness before referral growth is encouraged.
A0000366
Confirm the prompt is private, non-pushy, after-service only and does not promise rewards, discounts or automatic outreach.
A0000367
Confirm follow-up is a manual admin/operator prompt and not an automated SMS, email or campaign.
A0000368
Confirm story templates do not create fake testimonials, public proof, public complaint walls or automatic publishing.
A0000369
Confirm trust/safety pages are linked from referral and support moments and do not create scores, rankings or quote comparison.
A0000357
Confirm support copy avoids automatic escalation, pressure, blame, public complaints or unsafe detail requests.
A0000362
Confirm this referral readiness pack is linked from the admin dashboard, QA index, launch command centre and handover notes.