Hello Rescue Community,
Over the last few months, there have been several updates for LogMeIn Rescue. This post will inform you on what went live, so you're up to speed on the latest improvements available.
Microsoft Teams Integration: Calling Card, Zero Download & Localizations
We've made starting a Rescue session from Teams faster, more secure, and more accessible for enterprises worldwide. Three enhancements landed:
- Calling Card launch by default — clicking a Rescue link from Teams now launches the installed Calling Card automatically, instead of forcing an applet download.
- Zero Download session support — a browser-native join experience that requires no installation at all, as a complementary session type.
- Localizations — non-English end users are now prompted in their own language, removing a long-standing adoption barrier.
How does it work?
1. Faster Session Launches with Calling Card: When you share a Rescue session link through Teams, it automatically launches the Calling Card if it's installed—no extra steps or downloads needed. If the Calling Card isn't installed, your end users are guided to get it seamlessly. It's the quickest way to get connected.
2. Browser Based Sessions for Instant Access: Need to support someone without the Calling Card installed? You can now offer Zero Download sessions that run entirely in a web browser, no installation required.
Your end users can join instantly, and you maintain full control over which session types your team uses.
3. Support for Multiple Languages End users now experience the session join flow in their own language, not just English. Invitations and prompts appear in French, Spanish, German, Portuguese, Hungarian, and more—making the experience feel natural for everyone.
These enhancements are available to Rescue customers using the Microsoft Teams integration, at no extra cost.
Calling Card Installation Tab
The Rescue team is thrilled to announce the release of the Calling Card Installation Tab for the WebTC.
The Calling Card tab appears in the Technician Console during an active session. It lets a technician deploy the Calling Card — a small branded client app — directly to the customer's computer, so future support sessions can be started with one click instead of a PIN code or website visit.
WebTC Calling Card installation helps for the following uses:
- Ad-hoc Calling Card Installation requests
- When the Calling Card bulk installation does not work or the device was not present by the bulk deployment
- The Calling Card was deinstalled by mistake and re-installation is needed
Check out the Calling Card Guide for more information.
If you want to know the latest, check out this community post detailing the current feature parity status.
Nexthink-Powered AI: Smarter Recommendations in Rescue Sessions
We are excited to announce Phase 3 of the Rescue–Nexthink integration! Rescue AI now uses live Nexthink device telemetry to generate more precise root cause hypotheses and actionable recommendations — automatically, from the moment a session starts.
How does it work?
Nexthink data enriches three key moments in the AI-assisted support workflow:
1. Device Analysis — richer historical context from the start
At session start, the AI automatically pulls Nexthink telemetry alongside the ticket and in-session data. Rather than relying on what the technician can observe in the moment, the AI has weeks of device history to work with.
2. On-demand Recommendations — higher-confidence, targeted guidance
When the technician requests a recommendation, the AI cross-references Nexthink's historical telemetry with live session context to form a root cause hypothesis. The result is more precise, higher-confidence recommendations with clear reasoning.
3. AI Session Summary — insights and inferences carried forward
Nexthink-sourced data and the AI's inferences are captured in the session summary, giving technicians and subsequent support tiers a complete picture of what was analyzed and why — without having to reconstruct the diagnostic context from scratch.
Phase 3 is available to customers with both a Rescue Remote Device Support license and a Nexthink license with API and NQL capabilities, plus an active Rescue AI Assistant license with credits. Phase 2 must already be configured.
Know Exactly Where Your AI Credits Go — Usage Overview Live in GoTo Admin for Rescue
Enjoy complete, real-time visibility into AI credit usage — directly inside GoTo Admin → Billing → Usage Overview.
This self-serve dashboard gives billing admins, and Care teams full visibility into how AI credits are being used — including credit balance, consumption trends, and a detailed usage table — enabling informed purchasing decisions and reducing the need to contact support for usage queries.
Now you can view:
Credit Balance at a Glance
Always know where you stand:
- Total credits allocated under your contract
- Credits consumed to date
- Remaining balance
- Last top-up amount and date
- Contract start/end dates and days remaining
- A proactive warning banners basis the consumption (for low-credit, out of credit, etc) — with a direct "Buy more credits" CTA before it becomes an outage
Consumption Trends
Spot patterns before they become problems:
- AI credit consumption across your contract period
- Unique users consuming AI credits per billing cycle
- Filterable by billing cycle — current cycle, last 2, 3, or 6 cycles, or full contract history
- "Include current cycle" toggle to include or exclude the open billing period
For more information see this article.
Feedback? Questions? Comments? Let us know below!
