Changelog
Follow up on the latest improvements andΒ updates.
RSS
new
Voice
Admin
Full Call Transcript Sent to PSA as an Attachment
The complete call transcript now lands directly on the PSA ticket as a .txt file, so partners get the full back-and-forth in their PSA without us fighting note-body character limits.
Where to find it:
Open the Voice AI ticket in your PSA β the transcript is in the ticket's attachments/filesWhy it matters:
Now you can use the full transcript in your custom workflows, work right inside the PSA without context switching, or download it and run it through your preferred AI.new
Magic
Admin
Magic 2.5
π§± π§ New Triage Agent Custom Rules π€
Custom Rules just leveled up. Instead of one freeform block of text, you can now build structured, testable rules.
What's new?
- Structured rule cards: draft up to 10 rules, 5,000 characters each
- Targeted scope: scope each rule to specific clients or contact types
- Test before you ship: validate in the Emulator before publishing
- Safe migration: your existing freeform rules stay live until you choose to move over
Where to find it:
Admin -> Triage Agent -> Custom RulesDefault: nothing changes until you opt in. Current freeform rules keep working as-is.
.
ποΈ Triage Agent Client Access: Contact Filtering + Request Blocking π€

You now have finer control over which requests the Triage Agent engages with, beyond companies, boards, and sources.
What's new?
- Contact filtering: exclude specific contacts, or include/exclude by ConnectWise contact type. Contact-level rules take precedence over company access.
- Request blocking: block by sender domain (wildcards supported, e.g. *.example.com), specific email address, or keywords in the thread title.
Good to know
- Blocked requests still create a thread. The Triage Agent just won't respond or act on it, so a human can pick it up as usual.
Where to find it
: Admin -> Triage Agent -> Client access

How to enable it
1. Go to PSA Sync settings
2. Integrations β PSA β PSA Sync β Manage Sync
3. Open Boards & Categories
4. Find the board you want to exclude using the search bar or scroll the paginated list.
5. Uncheck to exclude
6. Click Save β done
new
Voice
Admin
Released: Voice AI Custom Farewell Message
You can now customize what their voice agent says to sign off at the end of a call, instead of the default goodbye.
What's new
- Custom farewell field: set your own closing message per voice agent
- Works across flows: applies consistently to Attendant, Overflow, and Attendant β Overflow handoffs
- Reset to default: revert to the standard farewell anytime with one click
Where to find it:
Voice β Agents β select an agent β Overflow/Attendant SettingsNotes:
- Existing agents keep the default farewell unless a partner sets a custom one.
- Per-agent setting β changes apply only to the selected voice agent.
Attendant:

Overflow:

new
Voice
Admin
Released: Voice AI Speech Speed & Volume Controls

Partners can now configure speech speed and volume per voice agent from the agentβs General tab.
Whatβs new
- Speech speed slider: adjust from 0.6x to 1.5x, default 1.0x
- Speech volume slider: adjust agent voice volume from the same section
- Preview support: preview reflects the selected voice and pending speed/volume changes before saving
- Per-agent settings: changes apply only to the selected voice agent
Where to find it:
Voice β Agents β select an agent β General β Voice settingsNotes:
- Speech speed applies to previews and live calls.
- Speech volume works reliably in preview and is sent to Cartesia for live calls, but perceived volume on phone calls may vary because downstream telephony systems can normalize audio.
Existing agents keep their default behavior unless a partner updates the settings.
new
Inbox
Magic
Magic 2.4
β¨ Three new ways for Ask Magic to surface the right knowledge
This release brings two new integration paths and a proactive drafting feature to Ask Magic. They ship together but each works on its own. Pick the ones that fit your shop, skip the ones that don't.
π Hudu Integration
Connect your Hudu workspace and Ask Magic instantly references your articles in real time, no syncing, no waiting. Up to 5 relevant articles surfaced per question (configurable up to 10), full content available to the AI, not just titles. Smart fallback search retries with different phrasings so you don't lose results to a wording mismatch. Results are scoped to the client on the thread.
π IT Glue Integration
Connect your IT Glue account once and Thread keeps your library aligned every night, fully automatic, no manual touch needed. Incremental sync touches only what changed.
Need an immediate refresh after publishing something? Hit Sync now on the Document Sync tab.
π Thread Admin β Integrations β IT Glue/Hudu β connect your API key and toggle on Knowledge Articles
.
πͺ Proactive Messaging in Ask Magic
When a technician opens an eligible ticket, Ask Magic now drafts a suggested resolution in the background. Context, troubleshooting steps, and relevant KB articles, all queued up before they type a thing.
The draft is internal-only, so customers never see it. Pulls from your Knowledge Base, past related tickets, and any connected documentation (IT Glue or Hudu, if enabled).
π€ New Triage Agent Setting: Silent Inactivity Mode π€«
You can now prevent the Triage Agent from sending any follow-up message when a thread goes inactive, including the well-known "just checking in" and any custom timeout message you've configured.
What's new?
- ποΈ Toggle it on under the Silence timeout message section in your Triage Agent settings
- π When enabled, the agent still observes the inactivity window and transitions the thread into Listening Mode (if enabled), it just does so without messaging the contact
- π€ Works alongside Listening Mode whether it's on or off
- β Overrides any custom timeout message you've set
π― Who this is for
Teams that want the agent to monitor silently and leave all outreach to their technicians.
βοΈ Default: off. Existing workspaces keep their current timeout messaging behavior until they opt in.
new
Voice
Admin
[Voice AI] Advanced AI Contact Mapping for Overflow
Contact mapping has always been one of those features that sounds simple but carries a lot of weight. Getting the right ticket connected to the right person saves technicians real time and reduces the guesswork that slows down support queues.
What changed?
Contact mapping is now controlled by agent β
meaning Attendant and Overflow each have their own independent contact mapping settings
, rather than Overflow inheriting Attendantβs settings (what used to happen).
Why this matters
Previously, contact mapping in Overflow was tied to Attendant's settings.
This created a real gap for MSPs running Attendant in Minimal Mode.
If a call timed out (no tech available) and routed to Overflow, there was no opportunity to collect caller information. Tickets created through this flow arrived without advanced contact mapping, leaving technicians to manually investigate who called if the number was unknown.Some partners found a workaround by adding a custom question, but that only leaves a note in the ticket, it doesnβt actually map the ticket to the correct contact.
What's new?
Attendant and Overflow now each control contact mapping independently
Partners using Attendant in Minimal Mode can now enable AI caller identification in Overflow, so missed calls that route there still capture caller identity from unknown numbers.
If a call flows from Attendant β Overflow, contact mapping is not asked twice β the handoff is seamless
What happens to your current settings?
No action is required. Settings have been migrated automatically based on your current configuration:
- Using Advanced AI with βAI caller identification ONβ β Overflow AI caller identification defaults to ON, preserving your existing behavior
- Using Minimal Mode or βAI caller identification OFFβ β Overflow contact mapping defaults to OFF
If you want to take advantage of the new per-agent controls, head into your Overflow settings to update anytime. Otherwise, everything works exactly as it did before.
new
Inbox
Admin
Magic 2.3
π Flow Folders: You can now organize your Flows into folders
What's new?
- Folder organization:Group Flows by client, team, use case, or however makes sense for your shop
- Cleaner Flows list:No more digging through a flat list of 90+ Flows to find the one you need
- Easier troubleshooting:Logical groupings make it faster to locate the right Flow when something needs attention
Create your Flow Folders today:
π Thread Admin -> Flows -> Folders tab π Inbox: Resizable Panels π
You can now resize the left nav and right Details panel in the inbox. Drag the edges to make them wider or narrower. Your preferences save automatically.
Min/max constraints keep things from getting out of hand, but you've got plenty of room to customize your workspace however you like.
new
Magic 2.27
π€ New Emulator: All AI Features β¨
The emulator has been fully redesigned across all Magic AI features: Triage Agent, Auto-Priority, Auto-Category, Generate Title, Recap, Reminder Agent, and Intent edit.
What's new?
- Full-width panel:takes up the entire right panel instead of floating as a chat bubble overlay
- Sticky while you scroll:stays fixed as you scroll through settings, no more back and forth
- Refreshed chat bubbles:new bubble design with the welcome animation preserved
- On the Triage Agent, you can now simulate as aspecific contact: The emulator loads their known intents and applicable custom rule.Use Testing As β One Personcontact to try it.
new
Magic
Admin
Magic 2.26
π€ Pia Smart Forms - Triage Agent Re-engagement
The Triage Agent now stays active after sending a Pia smart form and drives the conversation to a resolution.
What's new
- Agent confirms form submission and either closes the ticket (if contact confirms) or escalates to a technician, based on your intent config
- Agent handles cancellations and errors by escalating automatically
- If the contact messages while the form is pending, normal triage continues uninterrupted
How to configure
Two new optional fields on any Pia smart form intent:
- External Reply - prompt the agent on what to say after submission.
- Resolution checkbox - check to close on contact confirmation, uncheck to auto-escalate

No changes needed to existing intents to get the base behavior.
Load More
β