POR One | Driver Communication Call Logs

POR One requires version 2026.10.1 or later

Counterpersons and drivers often need to pass along stop-specific instructions like which driveway to use, which building to drop at, or where equipment was left for pickup but a standard call log doesn't automatically surface to the driver working that stop. The Driver Communications call log type solves this by tying a note directly to a contract and pushing it to the driver automatically, without requiring acknowledgment. After following this article, you'll be able to set up the Driver Communications call log type and create notes that appear automatically on the Task Actions page, the Stop, and the Call Logs accordion for the driver handling that stop.

Applies To

Delivery and pickup drivers are the primary audience for this feature, with counterpersons as the ones typically creating the notes. Requires POR One version 2026.10.1 or later and a call log type named exactly Driver Communications already set up in your system. No special permissions required.

Driver Communications is built for two scenarios:

• Counterperson to driver: a counterperson leaves a note for a delivery or pickup driver, for example, letting them know which driveway to use or which building to drop items at.

• Driver to driver: a delivery driver leaves a note for the pickup driver on the same stop, for example, flagging that pallets, jacks, or tie-downs were left in a specific spot, or that the pickup driver needs to contact a specific person on-site.

Topics Included in This Article

• Before You Begin

• Setting Up the Driver Communications Call Log Type

• Creating a New Call Log on a Contract (In Elite)

• Creating a New Call Log from POR One

• Where Drivers See Driver Communications Notes

• More Information / FAQ

Before You Begin

Before this feature works, confirm the following:
 

• POR One must be on version 2026.10.1 or later.

• Elite has no version requirement. All Elite versions support call logs.

• This feature only works if a call log type named exactly Driver Communications (capital D, capital C) already exists in your system. If it doesn't yet, set it up first or they won't trigger the automatic workflow described in this article.

Setting Up the Driver Communications Call Log Type

1. Press the Gear Icon (top-right) > Press App Configurations > Transaction Configuration > Call Log Types
   
    

2. Press Add and enter "Driver Communications" (capital D, capital C). 
    
3. Press OK to save.
   

Once a call log type with this exact name exists, any call log created under it will automatically trigger the Driver Communications workflow described in this article.

Creating a New Call Log on a Contract (In Elite)

1. Open the contract for the stop you want to leave a note on.
    

2. Go to the Add Call tab and press New Call. 
    

3. Click New Call to create a new call log.
    

4. Set the call log type to Driver Communications.

   
    

5. Enter your note. For example, the driveway to use, the building to drop at, or where equipment was left for pickup.
    

6. Click OK to save. Once saved, this note is tied to the contract and surfaces automatically to the driver, as described below. 

   

Creating a New Call Log from POR One

1. Open the contract for the stop you want to leave a note on.

2. Go to the Call Logs accordion on the contract.

3. Add a new call log.

4. Set the call log type to Driver Communications.

5. Enter your note, for example, the driveway to use, the building to drop at, or where equipment was left for pickup.

6. Save the call log.
   

Where Drivers See Driver Communications Notes

Once a Driver Communications call log exists on a contract, it surfaces automatically for the driver in POR One in three places:

On the Task Actions page, when the driver hits Arrived and moves through the routes flow.	On the Stop itself, if the driver navigates there directly.	On the Call Logs accordion on the contract.

These notes display with a red exclamation point , the same visual treatment used for force-acknowledged call logs (call logs that require the reader to confirm they've seen the note before proceeding). Unlike force-acknowledged logs, Driver Communications notes don't require acknowledgment. They appear automatically so the driver sees them without an extra tap.

More Information / FAQ

What happens if my call log type isn't named exactly "Driver Communications"?

The workflow won't trigger. The name must match exactly — including capitalization ("Driver Communications," capital D, capital C) — for call logs created under that type to surface automatically to drivers.

Does this replace force-acknowledged call logs?

No. Force-acknowledged call logs require the driver to confirm they've seen the note before proceeding. Driver Communications notes surface automatically but don't require acknowledgment. Use force-acknowledged logs when you need confirmation the driver saw the note; use Driver Communications when you just need the information to appear without blocking their workflow.

Does a driver need to hit "Arrived" before they can see a Driver Communications note?

No. While the note does surface on the Task Actions page once the driver hits Arrived, it also appears on the Stop itself if the driver navigates there directly, and on the Call Logs accordion on the contract — so it's visible regardless of where the driver is in the routes flow.