Simple Issue Reporting Promise¶
Date: 2026-06-25 Status: Accepted for the first paid pilot. Roadmap item: EP9-T1.
Decision¶
The launch promise is simple in-app issue reporting only.
MamNajem may say that owners and tenants can submit simple in-app reports when something in the app or rental workflow needs support. It must not promise lease-linked repair management, repair timelines, contractor assignment, landlord-versus-tenant responsibility decisions, SLAs, quotes, invoices, or a vendor maintenance suite.
Product Contract¶
The existing problem-report fields map directly to the launch promise:
| Existing field or state | Launch meaning |
|---|---|
topic |
Simple title/category. |
message |
Plain description from the reporter. |
photoAssetId |
Optional screenshot/photo attachment. |
OPEN |
Open support work. |
IN_PROGRESS |
Open support work. |
RESOLVED |
Closed support work. |
DISMISSED |
Closed support work. |
Copy Boundary¶
Public and product copy should use simple wording:
- "simple issues"
- "simple in-app reports"
- "support/problem report"
Avoid wording that implies a maintenance workflow:
- lease-linked repair management
- repair timelines
- contractor assignment
- responsibility resolution
- vendor marketplace or work orders
Evidence¶
- Mobile landing tenant copy says tenants can "submit simple issues".
- Mobile invitation copy now says tenants can send "simple in-app reports" instead of broad issue-reporting wording.
- Polish and Ukrainian invitation copy use equivalent "simple in-app reports" wording.
- Mobile guard:
language utilities > keeps launch issue-reporting copy scoped to simple in-app reports. - Existing support screen:
Account -> Support -> Report problem. - Existing admin status model maps
OPENandIN_PROGRESSto open work, andRESOLVEDandDISMISSEDto closed work.
Remaining Boundary¶
This closes the EP9-T1 promise-alignment gate. The broader maintenance/repair copy audit is closed in Maintenance promise audit.