Signal Customer Portal
Your delivery work. One clear view.
Create an order, follow its progress and return to the proof without piecing the story together from messages, spreadsheets and separate tracking links.
Delivery work in one view
Request details, progress and completion stay connected.
Signal Intelligent Intake
Start with what you already have.
Delivery information rarely arrives as a perfect form. It may begin as a note from a branch, a purchase order, an invoice, a multi-page PDF or a group of photos. Signal Intelligent Intake helps turn those existing sources into structured delivery details instead of asking the customer to type the same information again.
Describe the work in plain language or attach supported documents and images. Signal identifies candidate route, shipment, timing, contact and requirement details, then prepares them for review. Multiple source files and multi-delivery packets can be evaluated together when the source material supports that workflow.
Nothing is placed automatically. The customer reviews decisions, corrects uncertain information and completes anything missing before continuing into the same Order Builder used for manual entry. The result is less repetitive delivery order entry without giving up customer control.
“Pick up 4 pallets from our Denver branch tomorrow morning and deliver them to the Aurora jobsite before 2 PM. Liftgate required.”
Describe the delivery in your own words.
Signal identifies useful delivery details and prepares them as structured information. The customer remains in control: every field can be reviewed, corrected or completed before continuing.
ORIGINDenver branch
DESTINATIONAurora jobsite
SHIPMENT4 pallets
SCHEDULETomorrow morning · before 2 PM
REQUIREMENTSLiftgate requested
Request creation
Start with a request the field can use.
A useful delivery request contains more than an address and a pickup time. It explains the route, what is moving, who can release it, what the receiving location needs and when the work must happen. The Customer Portal keeps those decisions in one Order Builder.
Single-delivery and multi-stop requirements stay attached to the relevant locations and shipment. Saved addresses reduce repeat entry, while contacts, access notes, handling needs and proof expectations remain available for review before the customer proceeds.
Put every stop in the right order.
Define pickup, delivery and additional stops with contacts, saved addresses, access notes and location-specific instructions.
Progress in context
Know what is happening without reconstructing the job.
A delivery can involve a requester, a branch team, a receiving contact and the people performing the work. The customer view connects visible progress to the original order so those participants are not relying on different versions of the story.
Confirmed milestones explain whether the order is preparing, assigned, at pickup, in transit or delivered. Relevant fulfillment context appears only when governed execution evidence supports it; private operational details and unverified ETAs are not inferred.
When an issue needs attention, the record shows that Signal is reviewing it while keeping the customer focused on the next useful action.
The original request stays in view.
Route, shipment, timing and requirements remain connected to the same customer record.
The completed handoff remains readable.
Completion status, receiving context and the final delivery result stay connected to the order.
Delivery record
Proof belongs to the delivery, not an inbox.
After the handoff, available receiving evidence remains associated with the correct order and stop. Depending on the agreed requirements and records captured, that may include photos, a signature, a delivery document or receiving detail.
The order record connects that evidence to what was requested and the progress that preceded it. Teams can return later to review the delivery result, distinguish one stop from another and resolve a question without rebuilding the history from disconnected messages.
Proof is not a decorative completion moment. It is the documented outcome of the work and part of the order’s durable customer context.
Organization context
Keep company visibility and location detail together.
Business delivery often spans more than one requester or branch. Company Management, Locations, Saved Addresses and User Management help distinguish which business requested the work, which operating location it belongs to and who is authorized to see or manage it.
Reusable location context reduces repetition without flattening every destination into an address. Receiving instructions, contacts and access conditions remain specific, while configured roles and location assignments shape the customer view. Available controls follow the organization’s current product configuration.
Keep delivery work with the right business.
Company context gives authorized users a shared operating view while respecting the configured account structure.
Next action
From a prepared request to the right next action.
The Customer Portal distinguishes preparation from commitment. A draft can be edited. A submitted request may need delivery options or a quote. A confirmed order carries the same context into execution, progress and proof.
That continuity matters when a load, timing window, equipment need or service requirement changes the applicable path. The customer does not have to abandon the request and begin again simply because the next step requires review.
Keep working before the request is submitted.
A draft preserves entered details while the customer reviews missing information or returns to an earlier Order Builder step.
Can our branches use the same Customer Portal?
Company, location and user context can support a shared customer experience. Signal reviews the required visibility and account structure for the program; exact access depends on the configured roles and permissions.
Does preparing a request confirm the delivery?
No. A draft or prepared request is not an accepted order. The applicable pricing, option review and operating confirmation remain part of the workflow.
What can I attach to Intelligent Intake?
The current product accepts supported PDFs and images, including JPEG, PNG and HEIC files. Multiple sources can be added to one Intake Session, then reviewed before information continues to the Order Builder.
What proof can be shown?
The order can retain available stop-level evidence for the agreed service, including photos, a signature or a delivery document when those records are captured and customer-visible.
Connected platform
See what happens beyond the customer view.
The Customer Portal is the customer-facing part of a wider delivery process. Follow how an order connects to capacity, field execution, human oversight and the final record.
See how Signal works