Support

Get unstuck without sending sensitive freight data into a ticket.

Use the guidance below to prepare files, understand findings, and give a support investigation enough context to help safely.

Support contact: UnknownConfirm the support email address, help desk URL, and response-time commitment before publishing this page. The product does not provide a confirmed public contact channel in the repository.

Prepare an upload

Start with a freight invoice PDF or CSV. Include the invoice number, line items, currency, and shipment reference when available. Supporting evidence can include a rate card, bill of lading, proof of delivery, appointment record, or carrier correspondence.

Understand a finding

Open the finding and check the calculation, amount at risk, confidence, reason, source references, and missing evidence. Treat the result as a reviewable suggestion until a human confirms it.

Handle a processing issue

Use the retry action when a supported file needs another processing attempt. If the issue persists, record the organization, approximate time, filename, and request or error ID shown by the application.

Protect customer data

Do not paste invoice contents, credentials, payment details, private file URLs, or carrier account numbers into a support request. Share only the minimum safe context needed to investigate.

When you need help

A safe support handoff has four parts.

  1. 01
    Identify the workspace

    Provide the organization name or workspace identifier, without attaching private invoices.

  2. 02
    Describe the action

    Tell support whether the issue occurred during upload, extraction, normalization, review, dispute preparation, or recovery tracking.

  3. 03
    Reference the event

    Include the approximate time, filename, request ID, or error ID shown by the product.

  4. 04
    Keep the decision human

    Do not ask support to approve a finding, send a dispute, or treat a suspected amount as recovered.