From equipment to a reviewable request

One request. Three connected steps.

01 / Capture

Start with what’s in front of you.

Type a known identifier, take a QR snapshot or check a label-photo suggestion.

Read Label entry screen — Actual desktop capture in an illustrative phone frame

Actual entry controls. No label image was uploaded in this capture.

Try the capture methods →

02 / Preserve context

Keep the request together.

Quantity, notes and relationship context give the reviewer a clearer starting point.

Quick RFQ part details — Actual desktop capture in an illustrative phone frame

Actual form with fictional, unsaved values. Distributor context is illustrated below.

See the relationship handoff →

03 / Human review

Make the next decision human.

Check suitability, distributor ownership and missing information before follow-up.

HALO RFQ RECREATED

Internal reviewer

Request ready to examine

Needs human review

Part identifier: DEMO-VLV-204
Quantity: 2
Distributor context: Example Industrial Supply
Next question: Confirm suitability and relationship ownership.

Recreated review illustration · Fictional data · No record or routing executed.

Try the reviewer perspective →

The context-and-review handoff illustrates Salesforce-native scope. Compare current implementation evidence.

The distributor stays in the conversation

The relationship travels
with the request.

Distributor / Sold By context remains visible for a person to check before commercial follow-up. An unknown relationship stays an open question.

Illustrative distributor professional reviewing a phone request at an industrial supply counter — AI-generated illustrative scenario · Fictional people and screen

01 / Field user

Capture the need

“Two valve assemblies for training line 03.”

Fictional request

02 / Relationship context

Keep attribution visible

Example Industrial Supply
Existing distributor relationship

Fictional distributor · Not contacted

03 / Internal reviewer

Confirm before follow-up

Check ownership, missing details and suitability.

Human decision required

Illustrated Salesforce-native handoff; no live routing or notification. Standalone parity is not implied.

Follow the request in the demo →

Keep the conversation connected

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.

Compare email and SMS status →

Halo RFQ

ILLUSTRATIVE 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

View request — preview onlyA confirmation is not a quote, an approved replacement or a delivery commitment.

SMS · Planned option

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.

What is available today?

Demonstrated · Salesforce demo

Role-specific email

Requester, distributor and rep email versions have documented demo-inbox receipt. That evidence does not establish production delivery or acceptance across external organizations.

Previewed · Standalone

Branded email designs

Account verification, password reset, RFQ confirmation, team notification and status-update previews exist. Live authentication and delivery acceptance remain pending.

Planned · SMS

Text notifications

A future option requiring provider selection, consent, sender registration, opt-out controls and delivery acceptance. No SMS is sent by this site or demo.

For a pilot, agree on brand treatment, sender identity, recipients, message content and channel scope. Customer-specific branding and live delivery need implementation and acceptance review. Discuss implementation →

The app as it exists today

Actual screens.
Salesforce admin reference.

Captured directly from the deployed development app on October 16, 2026. Larger previews focus on the app itself. Open any screenshot for the complete original, including Salesforce navigation.

Browse all actual app screenshots

Halo RFQ Admin home — app-focused crop of the actual deployed Salesforce-native interface — **Halo RFQ Admin home**Salesforce-native dev app · Captured October 16, 2026App-focused preview · Full original available above

Quick RFQ contact entry — app-focused crop of the actual deployed Salesforce-native interface — **Quick RFQ contact entry**Actual form · Empty contact fields · Nothing submittedApp-focused preview · Full original available above

Read Label entry — app-focused crop of the actual deployed Salesforce-native interface — **Read Label entry**Actual entry screen · No image uploaded or camera usedApp-focused preview · Full original available above

Keep the evidence in scope.

These images show the Salesforce-native admin experience. They do not establish standalone feature parity, OCR accuracy, production readiness or live email delivery. The interactive walkthrough remains a separately labeled synthetic illustration.

Implementation choices / Evidence reviewed October 16, 2026

Choose the scope.
Then agree on the handoff.

Two implementation tracks to evaluate with your team. The website demonstrates the journey; it does not establish that every feature is available in both tracks.

Verified locally · Bounded evidence

Standalone capture

Start by evaluating part and request capture outside Salesforce.

Known-part entry, quantity and notes
Editable QR/OCR suggestions applied by the user
Requester-scoped saved requests, search and receipts

Confirm the next step

No live Salesforce connection. The distributor-context and internal-review journey shown in the demo is not implemented standalone parity.

Discuss standalone scope →

Implemented source · Validate scope

Salesforce-native workflow

Evaluate request context and human review within Salesforce.

Quick RFQ and request-line components
Distributor context and internal-review components
Assignment/status controls and permission boundaries

Confirm before a pilot

Licensing, configuration, catalog behavior and end-to-end acceptance need validation. Successful matching must not be assumed.

Discuss Salesforce scope →

Acceptance stays specific.

Standalone email: live authentication and delivery acceptance pending. SMS: planned. Connectors: proposed future scope. Managed packaging and AppExchange approval are not established.

Compare notification status →

Read detailed capability evidence and limitations

“Verified” means bounded implementation evidence, not production certification. The synthetic website interactions remain separately demonstrated.

Standalone

Verified locally

Known-part capture, quantity and notes; requester-scoped saved requests, search and receipts. Local QR image/camera decoding and OCR suggestions require explicit user application; phone acceptance is recorded.

Standalone has no live Salesforce connection. Distributor-context handoff and reviewer actions shown in this website are illustrative, not implemented standalone features.

Salesforce-native

Implemented source

Separate Quick RFQ, request-line, distributor-context and internal review components exist, including assignment/status controls and permission boundaries.

Subscriber configuration, license fit, catalog behavior and current end-to-end pilot acceptance require validation. A prior controlled matching issue means successful matching must not be assumed.

This demo

Demonstrated

Editable synthetic capture → distributor context → request review → demo receipt → internal review recreation.

Browser memory only. No request record, email, routing, camera access, authentication or backend execution.

Email

Acceptance pending

Standalone HTML/plain-text previews and owner-run local authentication and delivery test tools exist.

ST-67 live authentication and delivery acceptance remain pending. A preview is not proof of delivery.

Connectors

Planned / proposed

Optional ERP, PIM, PLM, Sales Cloud, Service Cloud, Field Service and Manufacturing Cloud adapters are future scope.

No connector is represented as active here. Managed packaging and AppExchange listing/approval are not established.

Put the handoff to the test

See the context.
Explore the conversation.

A synthetic walkthrough today. A scoped pilot conversation next.

Explore the Demo ↗

Capture the part.
Keep the relationship.

One request. Three connected steps.

Start with what’s in front of you.

Keep the request together.

Make the next decision human.

Request ready to examine

The relationship travels
with the request.

Capture the need

Keep attribution visible

Confirm before follow-up

Branded notifications.
The right context for each person.

Your request. Ready for human review.

SMS is a future option.

What is available today?

Role-specific email

Branded email designs

Text notifications

Actual screens.
Salesforce admin reference.

Choose the scope.
Then agree on the handoff.

Standalone capture

Salesforce-native workflow

Acceptance stays specific.

Standalone

Salesforce-native

This demo

Email

Connectors

See the context.
Explore the conversation.

Start with the handoff.

Capture the part.Keep the relationship.

One request. Three connected steps.

Start with what’s in front of you.

Keep the request together.

Make the next decision human.

Request ready to examine

The relationship travelswith the request.

Capture the need

Keep attribution visible

Confirm before follow-up

Branded notifications. The right context for each person.

Your request. Ready for human review.

SMS is a future option.

What is available today?

Role-specific email

Branded email designs

Text notifications

Actual screens. Salesforce admin reference.

Choose the scope.Then agree on the handoff.

Standalone capture

Salesforce-native workflow

Acceptance stays specific.

Standalone

Salesforce-native

This demo

Email

Connectors

See the context. Explore the conversation.

Capture the part.
Keep the relationship.

The relationship travels
with the request.

Branded notifications.
The right context for each person.

Actual screens.
Salesforce admin reference.

Choose the scope.
Then agree on the handoff.

See the context.
Explore the conversation.