1
No standard login
Requesters do not need to navigate the full REQQER interface or maintain a normal user workflow just to report an issue.
Quick Entry & request intake
Make reporting a problem easier than ignoring it.
Quick Entry gives facility staff and other ordinary requesters a simplified way to submit a one-time Work Order without signing into the full REQQER system. The requester sees only the information needed to report the issue, while REQQER brings the resulting Work Order into the normal management process.
Simple requester experience
Collect enough structure to create useful work—without exposing the full application.
Quick Entry can present the fields and defaults appropriate to the Organization or Facility, giving requesters a focused path from “something is wrong” to a trackable Work Order.
2
Structured request information
Depending on configuration, the form can ask for Area, Location, Item, Req Type, Priority, requester information, and Description.
3
Mobile image capture
On a mobile device, the requester can capture or attach supporting imagery so the maintenance team can see the problem before arriving.
Configurable by facility
Keep the request form simple by hiding what the requester does not need.
Quick Entry can differ from one facility to another. Fields may be shown, hidden, or given defaults so the experience matches how the organization wants ordinary requests to enter the system.
- Organization- and Facility-level configuration
- Adaptable Area, Location, Item, Req Type, Priority, and requester fields
- Configurable defaults reduce unnecessary choices
- Valid requester email can be used for creation and completion notifications
- Every submitted issue becomes a one-time Work Order in the normal REQQER workflow
Desktop or shared-device use keeps the form focused on structured issue submission.
Mobile requesters gain an image-capture option without becoming full REQQER users.
Multiple intake channels
Different ways to report the work. One managed process afterward.
Quick Entry is only one way a one-time request can reach REQQER. The best intake method can vary by audience and setting.
Email and voicemail intake
Meet requesters where reporting the issue is easiest.
Email-to-Req
A user can submit a Work Order by email without a REQQER login. The email body becomes the issue description, and attached pictures, videos, or documents remain with the resulting Req.
- One-time Work Order creation
- Attachments retained with the Req
- Sender email can receive creation/completion notifications
- Useful from phones, tablets, or ordinary email clients
Voicemail-to-Req
An optional configured service lets a caller leave a message at a dedicated facility number. REQQER creates a one-time Work Order and attaches the voicemail recording for staff to review.
- No REQQER login for the caller
- Dedicated number identifies the participating facility
- Recording stays attached to the Work Order
- Useful where callers may not have convenient web access
Quick EntryStructured form
EmailMessage + attachments
VoicemailRecorded request
→
Requests ConsolePrioritize · assign · perform · document · close
The important part happens next
Request intake is useful because the issue becomes accountable work.
Once created, a Work Order can be prioritized, assigned, documented through Activity, coordinated with an External Vendor, supported by attachments, and ultimately closed with a permanent history.
Explore Work Order ManagementQuick Entry versus Mobile Batch Entry
Simple request submission is not the same as a managed walkthrough.
Quick Entry
Best when an ordinary requester has one issue to report and should not need the full REQQER workflow.
Mobile Batch Entry
Best when an authorized REQQER user is systematically walking an Area and recording multiple issues across Locations.
Explore Mobile Batch EntrySee REQQER in action
See how request intake can fit the people who actually report facility problems.
A demonstration can compare logged-in entry, Quick Entry, Mobile workflows, and supported email or voicemail intake.