Add New Driver Page (ACE and ACI eManifest): Difference between revisions

No edit summary
No edit summary
 
Line 1: Line 1:
{{note|This article is part of the [[BorderConnect_Software_User_Guide|BorderConnect Software User Guide]]|info}}
{{note|This article is part of the [[BorderConnect_Software_User_Guide|BorderConnect Software User Guide]]|info}}


{{#ev:youtube|JRNan7CgZpI|960|center|How to create a driver profile in BorderConnect}}
<div class="bc-wrap">


[[File:Adddriverpage1.png|360px|thumb|right|The Add New Driver page in BorderConnect]]
<div class="bc-article-hero">
<h1>Add New Driver Page</h1>
<p>Create and configure driver profiles for use across ACE and ACI eManifests.</p>
<div class="bc-article-meta">
<span class="bc-article-pill"><i class="fas fa-user-plus"></i> Type: Data Entry</span>
<span class="bc-article-pill"><i class="fas fa-cog"></i> System: General Data</span>
</div>
</div>


This guide walks through how to create and configure a '''Driver Profile''' in BorderConnect. Driver profiles are used across ACE and ACI eManifest workflows and allow the system to:
<div class="bc-card">


* Assign drivers to manifests and shipments 
<div class="bc-float-video" style="margin-top: 0;">
* Auto link PARS, PAPS, and in bond shipments 
  <div class="bc-video-trigger" data-video-id="JRNan7CgZpI">
* Send real time clearance notifications 
    <div class="bc-play-icon"><i class="fas fa-play-circle"></i></div>
* Maintain compliance ready driver data 
  </div>
</div>


You can open the '''Add New Driver''' page in three ways:
<h2 style="margin-top: 0;">Overview</h2>
<p>The <strong>Add New Driver Page</strong> allows you to create and configure a <strong>Driver Profile</strong> in BorderConnect. These profiles are used across both ACE (US) and ACI (Canada) eManifest workflows.</p>


* '''Manage Data → Create Driver''' 
<p>Creating a profile allows the system to:</p>
* '''Driver Search Page → Create Driver''' 
<div class="bc-cleanlist">
* From the '''Add Driver/Crew''' screen within an ACE eManifest 
* Assign drivers quickly to manifests and shipments.
* Automatically link PARS, PAPS, and in-bond shipments to the correct driver.
* Send real-time clearance notifications via SMS or Email.
* Maintain compliance-ready data (FAST IDs, Citizenship, etc.).
</div>


== Page Controls ==
<div class="bc-did-you-know" style="margin-top: 15px;">
<strong>How to Reach This Page:</strong><br>
* Navigate to <strong>Manage Data</strong> and select <strong>Create Driver</strong>.
* From the <strong>Driver Search Page</strong>, click <strong>Create Driver</strong>.
* Click the "Quick Add" (+) icon when assigning a driver inside any eManifest.
</div>


{| class="wikitable"
<div style="clear: both;"></div>
! Button
! Function
|-
| Save
| Creates the driver profile once all required fields are completed
|-
| Cancel
| Discards all entered data and returns to Driver Search
|-
| Clear
| Empties all fields so new data can be entered
|}


== General Driver Information ==
<div style="text-align: center; margin-top: 20px;">
[[File:Adddriverpage1.png|360px|thumb|center|The Add New Driver page in BorderConnect]]
</div>
</div>


This section captures the core identity and compliance details for each driver.
<h2 style="margin-top: 40px; border-bottom: 2px solid #eee; padding-bottom: 10px;">Page Controls</h2>


{| class="wikitable"
<div class="bc-card">
! Field
<p>These buttons control the saving and clearing of data on the form.</p>
! Required
! Description
|-
| Driver Number
| Always
| Internal identifier such as employee number or initials
|-
| First Name
| Always
| Legal first name of the driver
|-
| Middle Name or Initial
| Optional
| Middle name or initial if applicable
|-
| Last Name
| Always
| Legal last name of the driver
|-
| Gender
| Conditional
| Required if no FAST or ACE ID is provided for ACE manifests
|-
| Date of Birth
| Conditional
| Required if no FAST or ACE ID is provided for ACE manifests
|-
| Citizenship
| Conditional
| Must match travel documents used at the border
|-
| Terminal or Office
| Always
| Location the driver is assigned to within your company
|-
| ACE ID or FAST ID
| Conditional
| Required if driver is FAST approved and used in ACE
|}


'''Tip:''' If your terminal or office is missing, it can be created from the [[Company Details Page]] using the '''New Terminal''' option.
<table class="wikitable" style="width: 100%;">
<tr>
<th style="width: 20%;">Button</th>
<th>Function</th>
</tr>
<tr>
<td><strong>Save</strong></td>
<td>Creates the driver profile once all required fields are completed.</td>
</tr>
<tr>
<td><strong>Cancel</strong></td>
<td>Discards all entered data and returns you to the Driver Search page.</td>
</tr>
<tr>
<td><strong>Clear</strong></td>
<td>Empties all fields so entirely new data can be entered.</td>
</tr>
</table>
</div>


== Notification Settings ==
<h2 style="margin-top: 40px; border-bottom: 2px solid #eee; padding-bottom: 10px;">General Driver Information</h2>


[[File:driver-notification-options.png|800px]]
<div class="bc-card">
<p>This section captures the core identity and compliance details for the driver.</p>


Driver profiles can automatically notify drivers when shipments clear customs.
<table class="wikitable" style="width: 100%;">
<tr>
<th style="width: 25%;">Field</th>
<th style="width: 15%;">Required?</th>
<th>Description</th>
</tr>
<tr>
<td><strong>Driver Number</strong></td>
<td>Always</td>
<td>Internal identifier (e.g., employee ID, payroll number, or initials).</td>
</tr>
<tr>
<td><strong>First / Last Name</strong></td>
<td>Always</td>
<td>Legal names as they appear on travel documents.</td>
</tr>
<tr>
<td><strong>Gender / DOB</strong></td>
<td>Conditional</td>
<td>Required for ACE manifests <em>unless</em> a valid ACE ID or FAST ID is provided.</td>
</tr>
<tr>
<td><strong>Citizenship</strong></td>
<td>Conditional</td>
<td>Must match the travel documents used at the border.</td>
</tr>
<tr>
<td><strong>Terminal / Office</strong></td>
<td>Always</td>
<td>The company location the driver is assigned to. <br><em>(Tip: If missing, add it via [[Company Details Page|Company Details]] → New Terminal).</em></td>
</tr>
<tr>
<td><strong>ACE ID / FAST ID</strong></td>
<td>Conditional</td>
<td>Enter the ID number if the driver is FAST approved. This speeds up processing in ACE.</td>
</tr>
</table>
</div>


Notifications improve dispatch flow by letting drivers know when loads are ready to cross.
<h2 style="margin-top: 40px; border-bottom: 2px solid #eee; padding-bottom: 10px;">Notification Settings</h2>


=== Supported Notification Types ===
<div class="bc-card">
[[File:driver-notification-options.png|800px|thumb|center|Configuring driver alerts]]
<p>Driver profiles can be configured to automatically notify drivers when shipments clear customs. This improves dispatch flow by alerting drivers instantly when they are clear to cross.</p>


{| class="wikitable"
<h3>Supported Notification Types</h3>
! Notification Type
<table class="wikitable" style="width: 100%;">
! Trigger
<tr>
! Requires
<th style="width: 25%;">Type</th>
|-
<th>Trigger</th>
| ACI or PARS Alerts
<th>Requirement</th>
| When PARS is accepted or linked to driver
</tr>
| PARS Checking subscription
<tr>
|-
<td><strong>ACI or PARS Alerts</strong></td>
| ACE Alerts
<td>When a PARS is accepted by CBSA.</td>
| When PAPS or QP In Bond is accepted
<td>Requires "PARS Checking" subscription.</td>
| ACE eManifest
</tr>
|}
<tr>
<td><strong>ACE Alerts</strong></td>
<td>When a PAPS or In-Bond is accepted by CBP.</td>
<td>Requires "ACE eManifest" subscription.</td>
</tr>
</table>


All notification fields are optional.
<h3>Contact Details</h3>
<div class="bc-cleanlist">
* <strong>Email Alerts:</strong> Enter a <strong>Primary Email</strong> (and optional Secondary) to receive clearance emails.
* <strong>SMS Text Alerts:</strong> Enter a <strong>Primary Cell Phone</strong> and select the <strong>Carrier</strong> to receive text messages.
</div>
</div>


=== Email Alerts ===
<h2 style="margin-top: 40px; border-bottom: 2px solid #eee; padding-bottom: 10px;">Best Practices</h2>


;Primary Email
<div class="bc-card">
:Main email address for shipment clearance updates. Select ACI/PARS and or ACE alerts as desired.
<h3>Tips for Success</h3>
<div class="bc-cleanlist">
* <strong>Legal Accuracy:</strong> Ensure First and Last names match border documents exactly to avoid "Driver Not Found" errors at the booth.
* <strong>FAST IDs:</strong> Always enter the FAST ID if the driver has one; it reduces data entry requirements on the manifest.
* <strong>Notifications:</strong> Enable SMS notifications to reduce the number of check-calls dispatchers receive.
* <strong>Maintenance:</strong> Keep profiles updated immediately when a driver changes their phone number or moves terminals.
</div>
</div>


;Secondary Email
{{AppPromo}}
:Backup email address for additional notifications.


=== SMS Text Alerts ===
</div>
 
;Primary Cell Phone
:Driver’s mobile number for SMS alerts. Carrier selection is required.
 
;Secondary Cell Phone
:Optional backup mobile number for SMS alerts.
 
== Best Practices for Driver Profiles ==
 
* Use legal names exactly as on border documents 
* Always assign a terminal or office 
* Enter FAST ID for FAST approved drivers whenever possible 
* Enable notifications to reduce dispatcher workload 
* Keep profiles updated when drivers change contact info 
 
== Summary ==
 
Driver Profiles are a core component of BorderConnect workflows. Once created, they allow:
 
* Faster manifest creation 
* Automated shipment linking 
* Real time clearance communication 
* Improved compliance accuracy 
 
Setting them up correctly ensures smoother border crossings and fewer operational delays.


[[Category:BorderConnect Software User Guide]]
[[Category:BorderConnect Software User Guide]]