Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.leedab.com/llms.txt

Use this file to discover all available pages before exploring further.

When a load arrives short, gets refused, or goes undelivered, POD Recon spots the exception the moment it’s recorded and prepares the customer email and credit note draft before anyone on your team is notified.

​
Sources

SourceWhat it monitors
Carrier portalsDelivery status, exception codes, POD uploads
Driver appsDelivery confirmations, refusal notes, partial deliveries
Client POD systemsInbound POD records, missing-POD flags, discrepancies

​
Triggers

  • Short delivery — Carrier or driver records a partial delivery
  • Refusal — Customer refuses a load, in full or in part
  • Missing POD — Delivery window closes with no POD on file
  • Claim window — A dispute deadline is approaching

​
Outputs

OutputDescription
Reconciled sheetException log with load, reason, customer, and status
Customer email draftReady-to-send, written in your tone
Credit note draftCalculates the short or refused quantity value — ready for finance to approve

​
Memory

POD Recon keeps per-driver and per-customer dispute history. Patterns surface in the escalation when relevant. History builds automatically from day one.

​
Usage

Mention @pod-recon in Slack, Teams, WhatsApp, or Telegram. 
@pod-recon  What exceptions are open as of this morning?
@pod-recon  Flag load TRK-4421 as refused — customer turned it away at the dock at 09:15.
@pod-recon  Show me the dispute history for driver ID D-2204.
@pod-recon  Which claim windows are closing in the next 48 hours?
You retain approval authority for every outbound customer communication. Non-standard carrier exception schemas are mapped during onboarding.