Getting started with Spark
Nexthink Spark is the personal IT agent for every employee, using live DEX telemetry to diagnose and remediate issues autonomously and eliminate tickets.
Before you begin
Before deploying and using Nexthink Spark, ensure you have:
Configured Spark prerequisites which require administrator permissions. Refer to the Granting permissions for Spark section.
Configured Collector to gather the UPN for each user in clear text. Refer to the Configuring Collector level anonymization documentation.
Configured the Microsoft Entra ID inbound connector for your Microsoft tenant.
A Self-service portal URL.
The updated version 1.2.0 of the Nexthink Teams application package that was shared with you by email.
Nexthink recommends configuring ServiceNow connector credentials to enable incident creation directly from Spark. This integration enhances the ability of Spark to escalate unresolved issues with full context.
Setting up Nexthink Spark
Set up a communication channel for Spark interactions
Ensure that you meet the prerequisites before setting up a MS 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.
Use the welcome message to inform employees about the Spark scope and remind them to exercise judgment when reading AI-generated replies.
After setting up the communication channel, install the Spark version-specific application package (.zip) provided directly by Nexthink.
If you have previously deployed the Nexthink Teams app (either the original version or the new Spark version) using the Microsoft Teams Admin console, you will not be able to upload the Spark Teams application into your Teams client directly.
Microsoft Teams blocks the use of the application for users who are not authorized in the Teams Admin console. If you have never deployed the Nexthink Teams app through your Teams Admin console, you can upload the Spark Teams application into your Teams client directly.
Grant permissions
To configure and monitor Spark, update your roles to include the required permissions:
Set the Agent conversations NQL table visibility to Visible for the relevant roles.
Enable Spark permissions for the relevant roles.
For detailed information about available permissions, View domain options, Data model visibility and Data privacy granularity settings, see:
Import knowledge base articles from ServiceNow
Manually upload knowledge base articles from the ITSM tool, ServiceNow, as CSV files into Nexthink to feed the Spark knowledge base.
Refer to the Managing knowledge sources documentation.
Enable diagnosis and remediation actions for Spark
Validate and enable actions for Spark in Nexthink.
Enable built-in agent actions
From the main navigation menu:
Go to Spark > Manage actions and review the Agent actions designed to work with Spark.
Enable the desired Agent actions for Spark use.
Refer to the Managing Agents actions documentation for more information.
Activate custom remote actions
From the main navigation menu:
Go to Remote Actions > Manage remote actions.
Create or edit a remote action, ensure you enable the Spark trigger.
Refer to the Spark actions documentation for more information
Nexthink advises against setting up remote actions for Spark that involve Nexthink campaigns.
Configure connector credentials for ServiceNow integration
You can set up connector credentials for ServiceNow in Nexthink to allow Spark to raise tickets when it cannot solve an incident. Nexthink is planning other ITSM tool integrations for future releases.
Ensure that the credential used has the required permission in ServiceNow to read and create incidents, e.g., has the
itilrole.Provide Nexthink with the credential configuration URL, the list of required ticket fields and your self-service portal URL.
Nexthink completes the initial setup, enabling Spark for ticket/incident creation— there is a plan for customer-facing UI for future releases.
Refer to the Connector credentials documentation for more information.
Communicate Spark deployment
Select the employee group for Spark deployment and prepare communications.
Use the controls in the 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 employee requests across configured channels, runs a diagnosis and attempts issue resolution.
At the moment, Microsoft Teams is the only available channel. Third-party tool integrations are planned for future releases.
The diagram above visually maps the Spark workflow sequence:
The employee submits a request through a configured communication channel 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 links to related knowledge base 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 Spark from providing an effective solution
Spark may suggest and initiate resolution measures, but all device remediation actions require user approval.
What data does Spark use?
Spark relies on a combination of static and dynamic data sources:
Knowledge base articles: Manually imported knowledge base articles.
Contextual Nexthink data: Device health, diagnostics, remediations and user metadata from Nexthink Infinity.
Consequently, Spark relies on specific NQL data model tables to query Spark-user interaction data.
Personal data handling is covered under the Nexthink Data Processing Agreement (DPA). Spark processing is user-specific and restricted to the customer region.
Spark never provides data from other organizations.
What languages does Spark support?
Spark detects the employee’s language from message content and delivers responses in that language, allowing employees to interact with Spark in their native language.
If the language cannot be detected or is not supported, Spark falls back to the tenant language, currently English or Japanese, and informs the employee accordingly.
Escalated tickets are generated in the tenant language, English or Japanese. They include a short description, actions taken, and the conversation transcript. Additional fields may contain the same content in the original employee language.
Last updated
Was this helpful?