> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexthink.com/user-guide/spark/setting-up-and-managing-spark/rolling-out-spark-to-your-organization/planning-your-spark-launch.md). # Planning your Spark launch Before deploying Spark to employees, plan how you communicate its purpose, build awareness, and sustain engagement over time. ## Secure executive sponsorship Build alignment with leadership to ensure your operational and strategic goals support one another. Reduce their load to make it easier for them to promote Spark to their organizations. * Give leaders context on how Spark benefits the organization. * Get an announcement or endorsement from IT leadership. * Provide department leaders with talking points to promote Spark. ## Define Spark branding Decide whether to use Spark as is or rename it to an internal brand to keep messaging consistent across communication channels. * Keep the branding consistent with your organization's look and feel. Some organizations reuse existing IT service terminology for this. * Separate the Spark brand from any prior chatbots that had low trust or adoption. Refer to [Managing Spark settings and data inputs](/user-guide/spark/setting-up-and-managing-spark/managing-spark-settings.md#customizing-the-assistant-name) and [Employee channels](/configuring_nexthink/bringing-data-into-your-nexthink-instance/integrating-nexthink-with-third-party-tools/employee-channels.md#replacing-the-logo) documentation for more information. ## Configure multiple access points * Choose any of the following communication channels for Spark. Refer to [Setting up and managing Spark](/user-guide/spark/setting-up-and-managing-spark.md) for configuration steps. * Your existing enterprise chatbots. * Refer to the [Understanding employee experience with Spark](/user-guide/spark/working-with-spark/understanding-employee-experience-with-spark.md#spark-in-enterprise-ai-agents) documentation to see different integration options. * Microsoft Teams * Microsoft 365 Copilot * Bookmark Spark on the company intranet or browser homepage. * Include Spark in onboarding and employee training materials. * Add a link and description to the employee portal or handbook. * Configure automatic redirections to Spark from any existing channels (see [#redirect-employees-from-existing-channels-gradually](#redirect-employees-from-existing-channels-gradually "mention") on this page). * Add Spark to the IT knowledge base. ## Prepare for rollout * Select a small group of early adopters from different departments and roles to serve as Spark ambassadors. This creates peer advocates in each area and across different IT challenges before broader rollout. Refer to [#build-a-spark-ambassador-program](#build-a-spark-ambassador-program "mention") on this page. * Get leaders or specific business units on board before a wider release. * Train IT team members to use Spark when supporting employees. Make sure they understand Spark's support workflow, including data inputs, employee recognition, remediation execution, and escalations, and their role in making this process effective. * Establish a communication plan for general access to all employees. * Redirect employees away from existing support channels gradually, rather than all at once. Refer to [Driving Spark adoption](/user-guide/spark/setting-up-and-managing-spark/rolling-out-spark-to-your-organization/driving-spark-adoption.md#redirect-employees-from-existing-channels-gradually)documentaion for more details. * Prioritize changes that increase positive experiences over changes that add friction. For example, a banner encouraging employees to try Spark before creating a ticket adds low friction. * Add friction only to the entry points you want to redirect away from. {% hint style="info" %} Complete the technical setup in [Setting up and managing Spark](/user-guide/spark/setting-up-and-managing-spark.md) before starting the rollout. {% endhint %} *** RELATED TOPICS * [Rolling out Spark to your organization](/user-guide/spark/setting-up-and-managing-spark/rolling-out-spark-to-your-organization.md) * [Driving Spark adoption](/user-guide/spark/setting-up-and-managing-spark/rolling-out-spark-to-your-organization/driving-spark-adoption.md) * [Setting up and managing Spark](/user-guide/spark/setting-up-and-managing-spark.md) * [Understanding employee experience with Spark](/user-guide/spark/working-with-spark/understanding-employee-experience-with-spark.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.nexthink.com/user-guide/spark/setting-up-and-managing-spark/rolling-out-spark-to-your-organization/planning-your-spark-launch.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.