Changelog

Follow up on the latest improvements and updates.

RSS

You asked, we delivered.
image (3)
What's new: You can now set a default Board and Source for each Voice AI agent directly in your settings.
Why this matters: Until now, Voice AI tickets used your Messenger default settings. This meant calls often landed in the wrong queue and were hard to filter in your PSA. No more.
With this update, you can:
  • Route tickets to the right board from the start: support calls to Support, sales inquiries to Sales, vendor calls to Vendor
  • Distinguish Voice AI tickets in your PSA: filter and report on AI-handled calls separately (e.g., "AI Phone" vs "Phone" vs "Voicemail")
  • Build cleaner views: create Inbox views filtered by source to see all voice tickets at a glance
How it works:
  1. Go to your Voice AI agent settings (Attendant or Overflow)
  2. Select your preferred Board and Source from the dropdowns
  3. New agents default to your Messenger settings. Override only when needed.
Works across all supported PSA platforms.
Your feedback made this happen:
"We would want to be able to distinguish between chat-created tickets and Thread Voice–created tickets within ConnectWise. So, I have two different sources." — Kurt, WBM
"Based on what they choose here, you might want them to go through a different experience and create it on a different board." — Wil
"Source is the main thing I need... I can filter out and be like, hey, these are voicemails, these are active calls." — Cole, CCS Technology Group
Questions or feedback? Drop them below.
Inbox Teams provide a structured way to
organize team members and manage which Views
they can access. Teams let you group people once and assign Views at the team level, reducing the need to manually update View access as your organization changes.
What’s new:
  • Create Teams to group team members who work together
  • Add or remove members, with their access to Team Views updated automatically
  • Nest Views inside a Team, and manage them using the same patterns you’re already familiar with in Inbox
  • Duplicate existing Views into a Team, creating a separate copy of the View for that Team
  • Admins can manage any Team—even if they are not members, and can remove themselves from a Team after creation while still making updates to its Views
  • View Teams in Inbox, where they can be expanded or collapsed—helping keep your workspace more organized and condensed
Why this matters
As teams grow and change, managing View access one person at a time doesn’t scale. Inbox Teams reduce the ongoing setup and maintenance work for Admins by letting access be managed at the team level—making it easier to keep the right people working from the right Views as your organization evolves.
Learn more about Inbox Teams.

improved

Inbox

Inbox 2.21

Planner updates
Planner: Improved scheduling & better real-world flexibility
What’s new:
  • Planner now allows overlapping schedule entries, removing hard blocks when conflicts exist.
  • Planned threads show a conflict indicator when schedules overlap, so conflicts are visible but not blocking.
  • Scheduling is now available in 15-minute increments.
  • Improved error handling when scheduling outside of work hours.
Conflicting-events
Why we're excited:
Real-world schedules aren’t perfectly clean—technicians often juggle overlapping work, and last-minute changes. These updates make Planner more flexible and realistic, giving teams a more wholistic view of their day without blocking progress, while still clearly surfacing conflicts when they matter.
We've improved how Voice AI transfers calls to your technicians.
What changed:
When the AI transfers a call, the technician now hears a prompt and presses 1 to accept before the caller is connected.
Why this matters:
Previously, the AI could mistake IVR systems, voicemail prompts, or recording disclosures for a live person — leading to awkward situations where the AI started talking to an automated message. Now, the handoff only continues once a real person confirms they're ready.
How it works:
  • Technician's phone rings → they hear "Press 1 to accept this call"
  • Press 1 → caller is connected
  • No response → caller hears "Our team isn't available right now, but we'll reach out soon" and a ticket is created
This should make technician handoffs more reliable, especially for teams using phone systems with IVRs or call recording announcements.
Questions or feedback? Let us know in the comments!
We've just released a new feature that gives you control over how your AI agent pronounces specific words.
Screenshot 2025-12-04 at 06
Where to find it:
Voice → Agents tab → Set up (on any agent) → General tab → Custom Pronunciations (under Communication Style)
How it works:
You can map any word to exactly how you want it pronounced. This is especially useful for company names, acronyms, or unique brand terms. For example, you could map "ABC" to "A B C Technologies" or "Acme" to "ACK-mee." These mappings apply to everything your agent says.
Quick tip:
We recommend using this for unique identifiers only—things like your company name or product abbreviations. Avoid mapping common words like "Technologies" or "Solutions," since those would get replaced everywhere in conversation.
Coming soon:
A preview feature so you can hear the pronunciation before saving.
Let us know how it works for you!
💡 Technician Feedback on Triage Agent 🔔
Technicians and service desk managers can now give direct feedback on the Triage Agent’s work, either on the overall thread or on specific messages. This helps us continuously improve the agent’s accuracy, behavior, and usefulness over time.
What this enables:
  • 🚦 Provide quick signal when the Triage Agent handled something well or missed the mark.
  • 🎯 Give targeted feedback on individual AI messages to highlight what needs refinement.
  • 📈 Help the agent get better with every interaction - the more insight we receive, the smarter it becomes.
  • 📊 Lay the foundation for upcoming analytics dashboards that will soon be available to admins.
How it works:
  1. Open any thread handled by the Triage Agent.
  2. Use the feedback options on the thread or next to individual AI messages.
  3. Submit your review, the Magic team uses this data to improve future agent performance.
This is our first step toward deeper visibility and continuous ML-driven improvement. More analytics and admin-facing insights coming soon.
.
🚀 Ask Magic Update: Expanded Search History (200 Threads) 🏴‍☠️💬
Ask Magic can now search up to 200 past threads for both contact-level and company-wide questions (400 total!), up from the previous limit of 10.
This gives technicians far deeper historical context when investigating patterns, recurring issues, or past user behavior.
The experience remains safe and controlled: Ask Magic will never surface all 200 threads at once. Guardrails ensure only relevant examples are shown, while the LLM uses the broader context to generate more accurate insights.
What this improves:
  • 🔁 Better pattern detection (e.g., recurring hardware issues across users)
  • 🧠 Richer answers for “similar issues,” “recent problems,” and “user history”
  • 🌐 More complete company-wide analysis on demand
No UI changes, this enhancement is entirely behind the scenes and available now.
.
📎 Image & PDF Uploads in Ask Magic 🔔
Technicians can now upload images and PDFs directly in Ask Magic while working from Inbox. This makes it easier to reference files as you Ask Magic for help during a conversation with a contact.
What this enables:
  • 🖼️ Add screenshots, error messages, or supporting PDFs to give Ask Magic additional context.
  • 📂 Bring files into Ask Magic as you’re troubleshooting or exploring a question.
  • 💻 Stay fully in Inbox: no switching between tools.
How it works:
  • Open Ask Magic from Inbox.
  • Drag and drop an image or PDF into Ask Magic, or use the upload option.
  • The file becomes part of your Ask Magic query, helping you dig deeper into the issue you’re working on.
.
🧠 Triage Agent Update: Smarter, More Targeted Questions Using Contact Intelligence 🔔
The Triage Agent now uses stored contact intelligence more effectively to shape its clarifying questions. This allows the agent to reduce noise, skip redundant queries, and focus on what actually matters for faster, more accurate triage.
What’s improved
The agent is increasingly leveraging memory even in very short conversations:
  • 1+ message threads → 53% memory usage
  • 2+ message threads → 58% memory usage
  • 3+ message threads → 65% memory usage
  • 4+ message threads → 72% memory usage
➡️ Strong upward progression: the more conversation context available, the more intelligently the agent uses stored memory.
Contact Intelligence Usage - Triage Agent
This results in sharper questions, fewer unnecessary follow-ups, and more context-aware triage.
🏴‍☠️ Triage Agent 2.0 New System Prompt 🎉 🚀
After months of beta testing and micro-adjustments, we’re releasing the 
new Triage Agent system prompt
 to General Availability for Pro Partners.
The foundation of a stronger, ITIL-aligned triage model built for the agentic era.
What’s New
  • Redesigned system prompt + guardrails
     built around the 
    Issue Identification Framework (IIF):
     a lightweight structure that ensures the agent captures the essentials (scope, symptoms, environment, access path, recency) before choosing a resolution path.
  • Valid for both break/fix incidents and service requests:
     the agent identifies first, then selects the safest, most accurate resolution path.
  • Sharper role definition:
     identify the issue → find the best resolution path (intent or escalation).
  • Confidence checks
     added for safer intent matching and more reliable automation triggers.
  • Improved tone
     that is more natural, human, and partner-friendly.
  • More consistent questioning
     with predictable stop rules and fewer unnecessary follow-ups.
  • Better escalation behavior
     and reduced premature handoffs.
Why It Matters
  • +15% improvement in IIF completeness
  • −7% reduction in conversation length
  • → sharper questions, shorter threads, and more actionable escalations.
Impact on Existing Partners
  • No changes required. And NO BEHAVIOR IMPACTS on existing workspaces with custom rules.
  • Your custom rules and configurations remain untouched.
Better Out-of-the-Box for New Partners
  • Strong triage performance from day one.
  • Fewer custom rules needed to get to “good.”
  • Built-in guardrails, tone presets, and ITIL-aligned flows increase predictability and trust.
TA 2
🚀 Contact Intelligence
We’re excited to announce the
General Availability of Contact Intelligence
, a feature that uses
past resolved threads
to build a contact memory. This gives technicians and the triage agent valuable insights for a
more personalized and efficient support experience.
Contact Intelligence captures key details about users - including their
setup, devices, and preferences
- helping your team better understand who they’re supporting.
Where to find it:
  • In Inbox:
    Under the contact card within a thread.
  • In the Contacts section:
    You can filter by contacts or companies that have Contact Intelligence enabled.
  • In Admin:
    A new
    Client Access page
    is available under the Intelligence menu. From there, you can control which
    clients, boards, and sources
    build contact intelligence data.
  • In Ask Magic:
    Users can ask questions like “
    What do we know about this contact?
    ” or “
    Show me this contact’s setup
    ”, and Contact Intelligence data will be included in the response.
What you can do:
  • Edit, delete, or copy
    contact intelligence data directly from Inbox.
  • For partners using the
    Triage Agent,
    it will
    automatically leverage this data
    to get richer context and ask more targeted questions.
Admins now have full control over where Magic Agents operate with the new Client Access page, live today for Triage Agent and Reminder Agent.
Here’s what’s new:
🔹
Granular access control:
Choose or exclude specific clients, boards, or sources for each agent.
🔹
Familiar experience:
The setup mirrors what’s already available in AI Essential, ensuring a consistent experience across all Magic features.
🔹
Simplified management:
Update permissions directly from each Agent’s settings, no extra Flows or steps needed.
This highly requested update gives admins precision and flexibility in managing access, so every Agent works exactly where it should. ⚙️💫
Magic Sentiment
Magic Sentiment
is officially live for all partners, introducing AI-powered mood tracking and actionable insights across every thread.
Here’s what’s new:
.
  • Actionable insights:
    When a thread’s sentiment turns negative, you can now ask Magic why to see the reasons, summary, and suggested resolutions — plus an option to create a Flow for alerts.
  • Flow templates:
    Prebuilt templates help teams track sentiment changes and automate notifications for both positive and negative experiences.
  • Views and filters:
    Admins can now filter and group threads by sentiment score to monitor customer health and spot trends over time.
  • Company sentiment:
    A new overview shows how each company is scoring across all their conversations.
Sentiment scoring turns every interaction into measurable feedback, helping teams understand tone, act faster, and strengthen customer relationships.
Other Improvements:
Triage Agent
now
parses inline screenshots/images embedded in emails
, not just attachments.
Previously, this limitation meant the agent was missing a lot of valuable context from emails, leading to a poor triage agent experience. With this update, even small details shared via pasted screenshots are now recognized, making for a smoother, more accurate triage agent conversations.
A small improvement with a big impact.
Load More