Quick RFQ
Enter a known part number. No QR tag needed.
HALO RFQ DEMORecreated practice · Fictional data · No camera or submission
Try Quick RFQ →Halo RFQ / Halo Business SystemsProtect distributor relationships.
Protect distributor relationships.
Capture RFQs faster.
Capture the part and request details in the field. Keep distributor attribution visible for the person reviewing the next step.
Type a part number · Scan a QR · Read a label photo ↓
2-minute synthetic walkthrough · No sign-in or real data needed
Try the app buttons · Recreated demo · Nothing sent
Compare current app scope →
Compare the actual app Home screenshot
Enlarge screenshot ↗Three ways to start / from your phoneType it. Scan a QR.
Type it. Scan a QR.
Read a label photo.
Choose any app button in the phone above. For a shorter introduction, open the method walkthroughs below.
Try the three short phone walkthroughs
HALO RFQ DEMO
Scan-to-RFQ
Frame a QR code, then review the identifier.
HALO RFQ DEMORecreated practice · Fictional data · No camera or submission
Try Scan-to-RFQ →Read Label
Photograph a tag, then check the suggestion.
HALO RFQ DEMORecreated practice · Fictional data · No camera or submission
Try Read Label →
Keep the conversation connectedBranded notifications.
Branded notifications.
The right context for each person.
The request should carry its context beyond the phone. Halo RFQ’s email designs give the requester, distributor and representative a message shaped around their role in the handoff.
- Requester confirmationA clear reference for the request and what happens next.
- Distributor notificationKeep the distributor relationship visible in the follow-up.
- Rep / team notificationBring the request and its context into human review.
Halo RFQILLUSTRATIVE EMAIL · FICTIONAL DATA · NOT SENT
Requester confirmation
Your request. Ready for human review.
A branded message keeps the reference and captured details together.
- Reference
- RFQ-DEMO-001
- Part identifier
- DEMO-VLV-204
- Quantity
- 2
SMS is a future option.
A proposed short alert linking to the request. Provider, consent and delivery acceptance remain future work.
Illustrative concept only. SMS sending is not implemented or demonstrated.Salesforce role-specific email: demonstrated in the demo. Standalone email: previews available, live acceptance pending. SMS: planned. See capability details →
At the equipment. With the context.
Capture the request where the work happens.
A facilities professional can start with the identifier in front of them, record what is needed and leave suitability decisions for human review.
Explore the field-to-review demo ↗For the product interface, view the actual app screenshots.
Choose your implementation pathOne workflow to evaluate.
One workflow to evaluate.
A scope that fits your team.
Explore standalone capture or a Salesforce-native workflow. Capabilities and acceptance requirements differ by track.
Put the handoff to the testSee the context.
See the context.
Explore the conversation.
A synthetic walkthrough today. A scoped pilot conversation next.