Getting started with Spark
This Technical Preview is made available to customers free of charge for their evaluation and feedback; in general availability the functionalities of the preview may be subject to additional cost and/or licensing. As such, the Technical Preview, the documentation, and any updates are provided for limited evaluation only and on an ‘as-is’ and ‘as-available’ basis without warranty of any kind.
Nexthink Spark is an AI agent that interprets and resolves level-1 IT requests and questions across real-time communication channels—currently, only available for MS Teams.
By accelerating issue resolution, Spark reduces IT support workload and enhances the employee experience.

Before you begin
Before deploying and using Nexthink Spark:
Set up a communication channel for Spark-Teams interactions
Ensure that you meet the pre-requisites to setup a Teams communication channel:
Use the Collector Option to gather the UPN for each user in clear text. Refer to the Configuring Collector level anonymization documentation for more information.
Configure a Microsoft Entra ID inbound connector for your Microsoft tenant
Set up a communication channel in Nexthink to enable Spark interaction with MS Teams.
After setting up the communication channel, install the version-specific application package (.zip) for Spark, which Nexthink provides directly for this technical preview.
Use the welcome message to inform employees about the chatbot's scope and remind them to exercise judgment when reading AI-generated replies.
Configure connector credentials for ServiceNow integration
Set up connector credentials for ServiceNow in Nexthink—other ITSM tool integrations are planned for future releases.
Provide Nexthink with the list of required ticket fields and your self-service portal URL.
Nexthink completes the initial setup for enabling Spark for ticket/incident creation—a customer-facing UI is planned for future releases.
Configure permissions
Edit your roles to add permissions related to Spark functionalities for admins:
Data model visibility:
Agent conversations enables users to view conversation information from Spark using Nexthink Query Language (NQL)
Spark:
View agent overview dashboards enables users to see overview dashboards to monitor the adoption and value of Spark
Manage all agent actions enables users to manage the agent actions that are available to Spark
View all agent conversations enables users to see the list of Spark conversations and their details including the conversation content
Review agent conversations enables users to give feedback about Spark conversations that are used to improve Spark (not currently used)
Manage agent knowledge sources enables users to upload knowledge articles that Spark can have access to (not currently used)
Communicate Spark deployment
Select the employee group for Spark deployment and prepare communications.
Use the controls in MS Teams admin console to select the employees with Spark access.
Inform employees about the scope of the Spark agent and remind them to exercise judgment when reading AI-generated replies.
How does Spark work?
Spark connects with employees' requests across configured channels, runs a diagnosis and attempts issue resolution.

(*) Conversation logs for reinforced learning are planned for future releases and are currently unavailable.
At the moment, Microsoft Teams is the only available channel. Third-party tool integrations are planned for future releases.
The diagram above visually maps Spark workflow sequence:
The employee reports in real time an issue via enterprise chats or other supported front-end channel integrations—currently only available for MS Teams.
Spark interprets the employee request in natural language—using LLMs hosted in the AWS Bedrock service within the Infinity platform. Depending on the employee request, Spark gathers and evaluates:
Nexthink datasets for the specific user/device diagnosis—limited to the user's own device.
Available actions—built-in agent actions and custom remote actions—for diagnostics or remediation.
Spark responds to the employee by sharing answers to employee questions or potential solutions to resolve their issues. Spark can either:
Provide self-help guidance or detailed information, including related links to related knowledge-based articles.
Request employee authorization for automated resolutions of device issues.
If unresolved, Spark escalates the support request to the service desk with full context. Spark only escalates requests in the following cases:
After exhausting relevant automatic actions and user troubleshooting.
Receiving an explicit escalation request from the employee.
Running into issues that require administrative access that the employee does not have.
Encountering technical limitations that prevent providing an effective solution.
What data does Spark use?
Spark relies on a combination of static and dynamic data sources:
Knowledge-based articles: Manually imported knowledge-based articles.
Contextual Nexthink data: Device health, diagnostics, remediations, and user metadata from Nexthink Infinity.
Planned data enhancements for future releases:
Conversation feedback: In the Cockpit, supervisors provide conversation feedback to help improve response quality in similar future interactions.
Consequently, Spark relies on specific NQL data model tables to query Spark-user interaction data.
Last updated
Was this helpful?