The right entry point
Residents enter through a building-specific QR route or a secure survey link connected to a planned job.
How FSEngage works
Better information in.Clearer action out.
FSEngage gives residents the right digital journey for the situation, then turns their answers into structured records that property teams can assess and progress.
- Two resident journeys
- Protected evidence
- Role-based review
One platform, two clear starting points
Something needs reportingScan the building sign, choose the relevant task and describe what has happened.
A visit is already plannedOpen the secure survey link and provide the details that will help the attending team prepare.
The shared workflow
Five stages turn resident input into operational context.
The exact questions and records differ by journey, but the handover from resident to property team remains structured and controlled.- 01
Start
A resident scans a building QR code or opens a secure link for a planned appointment.
- 02
Guide
The platform presents the task and questions relevant to that building or job type.
- 03
Capture
Structured answers and optional private evidence create a more useful operational record.
- 04
Assess
Authorised teams review the submission, understand context and decide the appropriate response.
- 05
Progress
Work is assigned, communicated and moved towards resolution through the relevant workflow.
Designed around the handover
Every layer supports a clearer decision.
The platform combines simple resident access with configurable questions, protected evidence and role-appropriate review.Relevant questions
Configured tasks, templates and decision rules keep the journey focused on the information actually needed.
Useful evidence
Optional photographs add visual context while remaining outside the public web root and behind protected routes.
Authorised review
Office users and permitted engineers see the operational information appropriate to their role and access level.
Communication activity
Configured email, status and optional WhatsApp delivery can support residents without blocking the core submission journey.
A clearer record
Consistent submissions make demand, ownership, progress and recurring service needs easier to understand.
Two journeys, one purpose
Reduce uncertainty before teams act or attend.
Communal building reporting
A resident scans the sign, chooses a task and submits building-linked information for office triage and progression.
Planned pre-visit survey
A resident opens a secure job link and provides access, property and evidence details before the appointment.
One operating principle
Both journeys reduce uncertainty by collecting better information before the property team decides what happens next.
How it works FAQs
Common questions about journeys, access and handover.
Are resident reporting and pre-visit surveys the same workflow?
No. They use different entry points and operational records, but share the same principle of guiding residents to provide relevant information securely and consistently.
Can the resident see private engineer information?
No. Public resident routes are separated from protected engineer site packs, documents and access information. Private portal content requires authentication and permission.
What happens when communication delivery fails?
Delivery attempts can be logged for review, but an email or messaging-provider failure does not prevent the resident’s core report or survey submission from being recorded.
Can workflows vary by organisation or job type?
Yes. Resident task cards can be configured by organisation, while survey questions, groups, rules and templates can be configured for different job types.
Where do office teams review information?
Authorised office users use the protected administration area to review jobs, reports, resident submissions, evidence, status and communication activity.
See the workflow in context