How can we help?

Sign up for a free account, then copy your branded onboarding URL from the dashboard (something like carrierpacket.link/p/yourcompany). Send that link to any carrier by email, text, or post it on your website. They click, fill out the packet, upload their documents, and sign — on phone or desktop — and you get an email with their completed record.

No. The Free plan gives you 1 user and 30 verified carriers with no card on file. Upgrade only when you outgrow it. Paid plans come with a 30-day trial — still no card required up front.

Most brokers are live in under five minutes. Sign up, paste your logo, save your default packet, and start sending links. There's no install, no contract, and nothing for your IT to configure.

Yes. We use PAdES — the same e-signature standard used by major commercial signing platforms — with an RFC 3161 timestamp from a public TSA. The carrier's email is verified by one-click before the PDF is produced, and the verification click is what mints the signed file. Every signed PDF embeds a verification URL on its Certificate of Completion page; pasting that URL into a browser returns an independent confirmation of the signature. Our public signing certificate is available at /app/cert.php.

USDOT-only carriers can still complete the packet. Our FMCSA lookup runs against either an MC or a DOT number, and the form gracefully degrades to manual fields if the carrier has neither (e.g. for an intrastate operation).

Yes. If the carrier signs up for a free Carrier account at /app/carrier/register.php, they can claim their MC/DOT record and reuse the same documents and contact info every time another broker sends them a CarrierPacket.Link onboarding URL.

After they fill out the form, we send them a one-time verification link. Clicking it confirms the email is theirs and triggers the signed PDF to be generated. The verification token is encoded into the cryptographic signature so the signed record proves they controlled that email at signing time.

W-9, Certificate of Insurance (COI), Operating Authority letter, Voided Check / ACH form, References, Notice of Assignment, plus up to 4 "Other" attachments per submission. All are stored against the carrier's record and downloadable from your dashboard.

When a COI or Operating Authority hits its expiration date, the carrier gets an automated email asking them to upload a fresh copy via a one-click reupload link. You'll see expired flags in your dashboard so you don't accidentally tender a load to a carrier whose insurance lapsed.

Files live on the same managed Bitnami host that runs the app, outside the web docroot and content-addressable by SHA-256. Identical files uploaded by two carriers under the same broker dedupe naturally. We don't ship documents to any third-party storage you haven't explicitly connected.

Yes. Drop a single <script> snippet (from your dashboard's Embed page) onto any page on your domain and the carrier-onboarding form appears inline, branded with your colors and logo. No iframe gymnastics.

If your TMS can consume a webhook or import a CSV, yes. Completed carrier records are pushed to whatever webhook URL you configure, and the dashboard exports CSV for systems that don't have a webhook listener. Specific known-good integrations include McLeod, AscendTMS, and Tailwind. Don't see yours? Ask us — we'll usually have a path.

Yes — a REST v1 API for listing submissions, fetching individual records, and managing packets programmatically. See /docs/api for the full reference. Authentication is bearer-token; tokens are issued from your dashboard's Connections page.

On Pro and Scale plans, every carrier submission is automatically scored against an FMCSA-derived risk rubric — safety rating, authority status, insurance status, new-entrant flags, and a handful of other signals. The score shows up next to the carrier in your dashboard so you can flag suspicious profiles before signing.

Yes. Click into the carrier record and the rubric breakdown shows every factor that contributed to the score, so you can override or audit a result rather than treating the number as a black box.

Yes. Invite teammates from your Team page; they get an email with a one-click accept link to set their password. Seat caps depend on plan (Free = 1, Starter = 3, Pro = 10, Scale = 25, Enterprise = unlimited).

The first user on an account is the admin (org founder) — they manage billing, branding, API tokens, and team seats. Invited teammates can build packets, send onboarding links, and view all carriers your org has onboarded, but can't change billing or branding.

Hit /app/forgot.php and enter your email. We'll send you a reset link that's valid for one hour. If you don't see it, check Junk and mark us Not Junk so future emails land in your inbox.

Yes. Plan changes take effect at the end of your current billing period. There are no contracts, no termination fees, and no setup fees. Cancel any time from the Billing page.

All major credit and debit cards via Stripe. We don't store card details on our servers — Stripe handles that side. Invoiced billing is available on Enterprise plans; contact us to set it up.

You'll get a heads-up email a few days before the 30-day trial expires. If you don't add a payment method, the account stays accessible but onboarding-link creation pauses until you subscribe. Your existing carrier records aren't deleted — they're preserved for when you come back.

All traffic is HTTPS-only with HSTS. Passwords are salted and hashed; auth cookies are HttpOnly + SameSite-Lax. Carrier documents are stored outside the web docroot. See our Privacy Policy for the full rundown.

Only users on your organization. Carriers aren't shared between brokers; each broker's onboarded carrier list is fully tenant-isolated at the database query level.

From Profile → Delete Account, or just write to us at dev@ninjatms.com and we'll take care of it. Deletion is permanent and removes all of your packets, links, and carrier submissions.