01
Start digitally
Write the message and add the paperwork from the phone or computer you already use.
What Handpost is
Keep the work connected, even when the other side still runs on paper.
Handpost is a business Exchange layer between modern senders and real-world workflows. The sender can stay digital. A supported receiving office can keep fax, paper, or its existing routine. Handpost keeps the matter continuous in between.
The handoff
Nobody has to adopt the other side's system.
Handpost is valuable because the business matter survives the change in transport. The user works with the relationship and the Exchange; delivery complexity stays underneath.
02
Handpost carries the handoff
The routing code identifies the intended Destination. Handpost applies the supported delivery, compliance, and review path underneath.
03
Keep the return connected
When supported paper or digital work comes back, trusted routing and reference evidence reconnect it to the Exchange it belongs to.
What stays connected
One underlying truth, whichever way you enter.
Start from an Exchange, Destination, Project, File, or notification. Handpost should bring you back to the same authorized work—not create another copy of reality.
The matter
Message, documents, delivery, return, and follow-up remain one Exchange instead of becoming separate tasks.
The relationship
A Destination is the other side of the work. The sender does not need to understand the transport machinery behind it.
The scope
A routing or reference code identifies context; it is not an access credential. Authorization stays separate.
The evidence
Important delivery and return evidence stays connected so Handpost can explain what happened later.
Useful automation, not blind automation
The system should stop when certainty stops.
Handpost uses routing evidence, document intelligence, and workflow rules to reduce repetitive work. When ownership, source, or matching evidence is weak, the right behavior is to stop or require review—not invent certainty.
A routing code can identify a Destination. Protected access still depends on the authorized Handpost identity and object scope.
Find the Handpost. Then let it show you the way.
Enter the routing code you were given, or explore Help to understand the workflow before you begin.