Jun 12, 2026

Changelog — Week of June 08, 2026

New features and improvements

Brand your Teams bot in a click — the New Channel dialog now has a Branding section where everything is optional (Neo supplies sensible defaults, including its own icons), so the downloadable Teams app package works the moment you create the channel. Set a display name and welcome message, and upload bot color/outline icons straight from your computer — no hosting required. A "View default" link shows the fallback.
Install your branded Teams bot with a link — from a channel's White-label installs, pick the client and click Generate install link; the client's M365 admin approves once and Neo publishes your branded app into their tenant and switches on message routing automatically. Changed branding later? Click Push update to re-publish to every tenant that installed via a link — no client re-consent. Manual zip upload remains as a fallback.

Dispatch around Teams shifts & breaks — connect the new Microsoft Teams — Workforce Availability integration, pick the Team(s) your service desk uses, and Neo skips technicians who are Away, Offline, or out of office when booking work (Busy / In a call / Presenting still count as working). Checks are time-scoped, and if Teams is unreachable dispatch falls back to its normal logic. Point it at a Shifts rotation and Neo also prefers technicians whose shift covers the slot. Configurable from the dashboard or public API.
SLA-aware dispatch for Autotask — Ticket Dispatch now books Autotask tickets against their first-response, resolution-plan, and resolution SLA targets (as it already did for ConnectWise), and retries for an earlier slot if its first pick would miss the deadline. Tickets without an SLA are unaffected; nothing to configure.
Name the booked schedule entry — control the name of the calendar entry Dispatch books via your dispatch custom instructions (e.g. "Name every entry 'NEO - [client] - [short summary]'"), so Neo-booked work is easy to spot in your PSA calendar. Works across ConnectWise, Autotask, and Halo.

A code sandbox for every agent — every agent now has an isolated code sandbox (nothing to enable). Agents reach for it on their own to parse exports, reshape data, or run bulk scripts. And when an integration returns more data than the agent can read at once, Neo automatically saves the full result to a file and filters/aggregates it there — so big data pulls no longer force the agent to drop results or re-query.
One-step password resets with forced change at next sign-in — agents can reset an M365 user's password and require a change at next sign-in in a single step, including delivering temp credentials by SMS during onboarding. Re-run Grant access for a company under End Companies to unlock it (tenants connected from June 2026 onward have it automatically).

Smarter RMM device-to-company matching — when Neo syncs devices from your RMM, it now also maps a site to a PSA company by recognizing the devices themselves (if a site's machines already exist as configurations/assets under a company), not just exact name matches. Only decisive evidence is used — ambiguous sites are left unmatched rather than guessed. Works across ConnectWise, Autotask, and Halo.

Chat Agents docs — a dedicated Chat Agents section now covers the technician chat experience, the Neo Support Agent, building your own chat agents, and Channels, including a step-by-step guide for deploying a branded Teams support bot into your clients' tenants.

Fixed a notification flood from the nightly Exchange-admin and daily M365 token-refresh sweeps — these maintenance checks no longer spam your team with repeated alerts, and dead delegated tokens are cleared automatically.
Fixed technician-approval (TIL) cards — resolved cards now show the real responder's name, the agent's approval description appears on the card, and an already-resolved card is handled gracefully instead of erroring.

Fixed Ingram Micro credentials — Neo now verifies marketplace credentials when you save them and notifies you if they stop working at runtime.
Fixed ConnectWise permission errors — a 403 from a missing security permission now surfaces as an actionable inbox item, and "resource has no company access" on a schedule entry is handled gracefully.
Fixed PSA ticket filters rejecting valid empty / "Unassigned" values.

Fixed several on-prem PowerShell failures — malformed string interpolation is now caught before sending, Set-ADUser attribute updates no longer fail, and Exchange Online sessions are hardened against partial dependency upgrades.
Fixed chat resilience — chat now self-heals from context-window overflow and transient streaming errors instead of failing the turn.

Improved reliability across PSA note posting and integration calls — many transient errors (timeouts, edge 403s, throttling) that previously surfaced as failed runs are now retried or handled gracefully.