We're excited to share that the new Load Creation experience is becoming the standard across the Alvys platform. Over the coming weeks, we will be retiring the legacy Load Creation workflow for all users.

What's changing?

The legacy Load Creation page will be removed and replaced entirely by the modern Load Creation experience. If you're already creating loads using the new workflow — no action is needed on your part. The transition will be seamless.

Why this change?

The new Load Creation workflow is faster, more reliable, and built to support upcoming features and improvements. Consolidating to a single experience allows us to deliver updates and enhancements more quickly while also speeding up your efficiency!

What should I expect?

• Over the next few weeks, the legacy Load Creation option will be removed from your account.
• All existing loads and data are unaffected — this is a UI change only.

Need help or want to learn more?

User Management has its own page now. Find it at Settings → Organization → Users. It is faster, searchable, and sortable, with filters by subsidiary.

The bigger change sits underneath. You can draw much sharper lines around who sees what.

• See your whole team at once. Every user, role, and status on one page. Change a reporting role without leaving the list.
• Set access by category, down to the individual action. Permissions group by area of the platform — rates, billing, dispatch, reporting, privacy. Grant a role its defaults, then tighten individual actions from there.
• Keep sensitive data behind its own permission. Tax ID and SSN, PII, and ACH account and routing numbers each sit behind their own permission, in a dedicated privacy group. For ACH, we go further than hiding the field: without the permission, our server never sends the account and routing numbers at all. The page shows only that details are on file.
• Separate viewing from editing. Let someone see a customer, carrier, or driver rate without letting them change it. Each is a separate permission.
• Manage multi-company users per company. Add or remove company access, and set different permissions in each one.
• The same rules follow your data into reporting. Permissions are enforced in our analytics layer too, so a user without them does not see masked fields surface in a report or an AI-assisted answer.
• Reset a locked-out user's MFA. An admin can do this without a support ticket. Limits below.
• Handle offboarding in seconds. Send a password reset. Remove access. Delete the user.
• My Profile got the same treatment. Every user manages their own details, integrations, notification settings, locale, and password in one place.

Why we rebuilt it this way

The way freight companies get breached has changed. Permissions are now the control that decides how bad it gets.

Trucking's own standards body spent the last year tracking the shift. NMFTA's 2026 Transportation Industry Cybersecurity Trends Report names AI-assisted social engineering as a defining trend, and warns it is becoming difficult to detect by traditional means. The report also ties digital compromise to physical cargo theft: identity fraud and account hijacking have become standard tools for cargo crime networks. NMFTA's cybersecurity director Ben Wilkens covers the same ground in The Trucker.

Why MFA reset has limits

Locked-out users are a real problem. Left unsolved, they push your team toward exactly the workaround attackers exploit: an urgent call, a rushed identity check, a reset granted under pressure. So we built the reset into the product, and we scoped it three ways.

1. The admin proves it is them. Resetting someone else's MFA requires the acting admin to confirm with their own authenticator code. An attacker who talks their way into an admin's session still cannot clear anyone's MFA without that admin's own second factor.
2. Rank is enforced. An admin can only reset a user below them. An Admin cannot reset another Admin. A Partner Admin cannot reset an Admin or another Partner Admin. Users on a custom role are not eligible. Those cases route to our support team.
3. The user re-enrolls themselves. The reset clears their enrolled authenticators; they set up a new one at next login. Nobody, including us, hands out a working second factor.

The second restriction matters most. No single account inside your company can take over every other privileged account.

Hi there,

Every dispatcher knows the feeling. A load is rolling, everything looks fine, and then the call comes in. A highway shut down. A winter storm closing in on a lane you dispatched yesterday. A theft hotspot where your driver just parked for the night.

By the time you hear about it, you're reacting instead of deciding.

Alvys Intel changes that. Intel is a real-time risk and event intelligence layer built directly into your TMS. It monitors millions of public signals for events that disrupt freight, then automatically connects them to the specific trips and lanes you're running right now.

What Intel watches for

• Cargo theft and hijackings — including emerging hotspots near your stops and layover points
• Severe weather — hurricanes, floods, tornadoes, winter storms, high winds, extreme temperatures
• Accidents and roadway incidents — closures and major slowdowns along active routes
• Infrastructure disruptions — road, rail, bridge, and port closures; facility and warehouse outages
• Hazmat and industrial incidents — fires, spills, explosions, evacuations

Where you'll see it

🗺️ On the Asset Map

Risk events appear as a live signal layer over your active trips. One glance shows which loads are exposed and where. Click any marker for full detail.

🚨 In the trip sidebar

Every trip now has a Risk Alerts tab showing what's happening along that load's route, with location and context.

💬 Through Ask AI

Ask "Show me my trips at risk" and get a prioritized list of affected loads with a recommendation for each. No dashboards to build, no filters to configure.

Why it matters

Reroute before you're forced to. Catching a closure an hour early is the difference between a routing decision and a service failure.

Stop hunting for information. Your team no longer scans news sites, weather apps, and driver groups to piece together what's happening.

Protect your freight and your drivers. Theft awareness at the stop level, before a driver parks for the night.

Get ahead of the customer call. Know about the disruption before your shipper does — and tell them what you're already doing about it.

Getting started

Intel is live now and included at no additional cost with Alvys Insights. Nothing to install, enable, or configure. It's already running against your active trips, and any user with Insights access has it today.

Open the Asset Map or any active trip to see it in action.

Not using Alvys Insights yet?

Insights is the AI analytics layer inside Alvys. Ask questions about your operation in plain English and get instant answers from your live data — and Intel is included at no extra cost.

Hi there,

Alvys now lets each subsidiary decide whether a Bill of Lading can satisfy a Proof of Delivery requirement when releasing or invoicing a load. Until now, if a load required a POD but only had a BOL attached, Alvys accepted the BOL automatically — with no way to turn that off. That default is changing.

Starting August 4, subsidiaries that haven't opted in will require an actual Proof of Delivery before a load can be released or invoiced.

Want a BOL to keep standing in for a POD?

1. Go to Settings → Subsidiaries → Invoice Settings, find Proof of Delivery under Required Documents.
2. Enable "Use Bill of Lading as Proof of Delivery" before August 4.

Prefer strict separation? Leave it off and a BOL alone will no longer release or invoice the load. When both documents are present, the POD is always used.

Hi there,

You can now set a credit limit on any customer and see how much of it they've used, right on the customer profile and on the Load Details Page.

Make sure to enable your view and manage credit limits permissions to use this.
​
The outstanding balance combines overdue unpaid invoices and the revenue on open, in-transit, or delivered loads that haven't been invoiced yet — so you're looking at real credit exposure, not just what's been billed.
​
When a limit is set, a color-coded bar shows the percentage used: blue up to 74%, yellow from 75–89%, and red at 90% and above. No limit set? You'll still see the outstanding balance as a standalone figure.

We launched the Alvys MCP server — one secure connection that lets AI assistants like Claude work directly with your Alvys data. Ask about open loads, driver hours, or invoice status in plain language and get answers from your live operation instead of a stale export.

🧪 In beta. The Alvys MCP server is available on request while we work with early customers. Contact your account representative, or the Alvys Partnership team if you're a software vendor.

What You Can Do

Ask about your operation in plain language — Search loads, trips, drivers, carriers, customers, trucks, and trailers without writing a single API call.

Pull money and tracking details — Look up invoices, fuel transactions, deductions, and inbound or outbound tracking history for any load.

Run guided workflows — Built-in prompts walk an agent through covering a load, dispatching a driver, onboarding a carrier, and reconciling settlements.

Connect in minutes — Sign in from Claude, Claude Desktop, or the MCP Inspector. No client secret to manage.

Stay in control of what agents can do — Every tool requires a permission you granted, write tools stay off unless you turn them on, and every call is rate-limited and logged

How to Access

Available on request during beta — contact your account representative to be added. Once enabled, point your MCP client at https://mcp.alvys.com/mcp.

Learn More

• Alvys MCP — Getting Started
• Available MCP Tools

We updated API Keys — you can now limit a credential to specific subsidiaries instead of your whole company. If you share API access with a partner, a broker, or an outside software vendor, they only see the subsidiaries you pick.

What You Can Do

• Scope a key to up to 3 subsidiaries — Choose which subsidiaries a credential can reach when you create it, or select All subsidiaries for company-wide access.
• Keep your data separated on every request — A scoped key can't read or change loads, trips, invoices, customers, drivers, or trucks outside its subsidiaries.
• Limit webhooks the same way — A scoped key only subscribes to events and reads delivery logs for its own subsidiaries.
• Find the right key faster — Filter your key list by subsidiary and by status; expired keys are hidden until you ask for them.
• Set an expiration on every new key — Every credential now needs an expiry date, and you can extend it later from the key's detail page.

Already using the API? Your existing credentials keep working exactly as they do today. Nothing changes until you choose to scope a key.

How to Access

Navigate to Settings > API Keys from the side navigation.

Learn More

• Getting Started with API Keys
• Using Subsidiary Scoped Tokens

Coming Soon!

On Monday, July 13, 2026 you will see the option for bulk action in the Dispatch Planner. Bulk Actions lets you select multiple trips in the Dispatch Planner and act on all of them at once. Six operations are available: Bulk Assign, Bulk Dispatch, Bulk Assign & Dispatch, Bulk Unassign, Bulk Change Dispatcher, and Bulk Set Priority.

How is it used?

Open the Dispatch Planner → Trips table.

• Select trips using the checkbox column — click individually, shift-click to select a range, or select all on the page.
• Choose an operation from the Actions menu that appears in the bulk action header.
• Confirm in the modal. Bulk Actions applies the change to every selected trip.
• When choosing Find Drivers, select a driver from the bottom table; when you take action from the side panel, it will bulk apply to all trips.

Coming Soon!

Managing your load templates just got easier. The Load Templates page will works exactly like the rest of Alvys — the same filtering, sorting, and column controls you already use everywhere else in the platform. No setup required; these updates will go live for everybody.

What's new

• Saved Views — Save, name, and recall your filtered and sorted template setups. Jump straight to the templates you use most without re-applying filters every time.
• Build templates while you build loads — From the load creation flow, you can now create a load and save it as a template at the same time, or just save it as a template for later.
• Create loads from a template, your way — Pick how many loads to create and set the dates — perfect for repeat lanes and recurring freight.

How to use Load Templates

Load Templates let you save reusable load setups for repeat lanes and recurring freight, then create loads from them in seconds.

• Finding your templates. Open the Load Templates page. The grid works like every other grid in Alvys — filter, sort, and manage columns the same way. It opens with an alert/issue indicator, Customer, Template Name, Lane (origin → destination), Contract, and Equipment. Add columns such as Created By or Last Updated from the column management sidebar.
• Saved Views. Apply the filters and sorting you want, then save it as a named view. Recall any saved view at any time to return to that exact setup.
• Creating a template. From the load creation flow, choose Create load & make template to create a load and save it as a reusable template, or Only make template to save a template without creating a load.
• Editing a template. Editing a template opens it in the load creation flow, where you have full visibility and editing capabilities.
• Creating loads from a template. Choose how many loads to create and set the dates for those loads, then create them.

Keep unapproved carriers off your loads — automatically.

You can now stop carriers from being assigned to a load until they're properly vetted. When you document a carrier or add a carrier quote, that carrier is recorded as pending — not yet onboarded. Previously, assigning a pending carrier only triggered a warning you could click past. Now you can turn that warning into a hard block.

What's new

A new company setting lets you choose exactly which carrier statuses are blocked from being assigned to a load. Pick any combination of:

• Pending
• Do Not Load
• Expired Insurance
• Interested
• Invited
• Packet Sent

Once configured, carriers in those statuses simply can't be assigned — no override, no accidental rate con to the wrong carrier. Only carriers you've approved make it onto a load.

Why it matters

Brokers have told us they avoid documenting carriers in Alvys because of the risk of a bad carrier accidentally ending up on a live load. Now you can document and quote carriers freely, knowing the system won't let an unvetted one be dispatched. It's a guardrail that lets you use carrier quotes as the powerful brokering tool they're meant to be.

Good to know

• You're in control. This is off by default. Turn it on and choose your blocked statuses in company settings whenever you're ready.
• Live loads aren't disrupted. If a carrier's status changes after they're already assigned and moving (for example, insurance lapses mid-transit), your dispatchers can still edit that load. They'll see a warning rather than being locked out — so tracking and updates keep flowing.
• Works across your workflow. The block applies when assigning or changing a carrier on a load and during bulk import.

Want this enabled for your team? Reach out to your Admin and have them update Settings!