Creating Document Requirement Rules

Modified on Tue, 9 Sep at 6:50 PM

Basic Rule Creation


To create a simple document requirement rule, use natural language in the chat interface:


Example Commands:

  • "Require a Proof of Delivery for all customers"

  • "Require a Scale Ticket for loads picking up in Los Angeles"

  • "Set up a rule requiring BOL for export loads"

Required Elements: Every rule must include:

  1. Rule Name: Either specify one or let the AI generate it

  2. Document Type: At least one recognized document type

  3. Conditions: Specify the conditions under which the document is required (e.g., load type, location, customer, charge code, bill-to party).


Advanced Rule Creation with Conditions


Create more sophisticated rules by adding conditions:


Load Type Conditions:

  • "Require POD for all export loads"

  • "Require Scale Ticket for import containers only"

  • "Set BOL requirement for road moves"

Location-Based Conditions:

  • "Require detention pics when picking up at Port of Los Angeles"

  • "Require dock receipt for deliveries to Long Beach terminals"

  • "Set Scale Ticket requirement for loads originating from Oakland"

Event-Based Conditions:

  • "Require TIR OUT when container exits terminal"

  • "Require chassis documentation for chassis transfer events"

  • "Set seal verification for container pickup events"


Customer-Specific Rules


Create rules that apply to specific customers:


Single Customer:

  • "Require POD for customer ABC Logistics"

  • "Set Scale Ticket requirement for XYZ Shipping only"

Multiple Customers:

  • "Require BOL for customers ABC Logistics and XYZ Shipping"

  • "Require detention documentation for all tier-1 customers"


AR Charge Code Integration


Link document requirements to specific charge codes:

Examples:

  • "Require POD when Base Price charge is present"

  • "Require Scale Ticket for any load with fuel surcharge"

  • "Set detention documentation requirement for detention charges"


Process: The agent will map natural language descriptions to specific charge codes in the account and confirm the mapping before creating the rule.


Bill-to Party Requirements


Create rules based on billing parties:

Examples:

  • "Require signed BOL for loads billed to ABC Corporation"

  • "Require additional documentation for government bill-to parties"

  • "Set enhanced requirements for high-value customers"


Clarification Process: If multiple organizations have similar names, the agent will display options and ask for clarification.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article