AI service desk for ServiceNow & TeamsLive on Azure Marketplace

Hartley

IT support that resolves before the ticket. Hartley answers staff in Microsoft Teams from your ServiceNow knowledge base.

About Hartley

The idea

Hartley searches your ServiceNow knowledge base first, alerts your IT team channel when it can't help, and only raises a ticket when it truly has to. All inside Microsoft Teams.

Product tour

How Hartley works

  1. Knowledge base first, ticket last

    A staff member describes the problem in Teams. Hartley searches the ServiceNow knowledge base with up to three keyword variations and presents the matching article step by step. If that doesn't fix it, Hartley raises a ticket and alerts your IT team channel. Every ticket carries the whole conversation.

    Knowledge base first, ticket last
  2. Every message, routed by intent

    Each message goes to one of three flows. An issue ("broken", "error", "not working") checks open tickets, then the knowledge base. A request ("install", "I need", "access to") searches the how-to guides, then the service catalog. A ticket number or status question summarises, updates or escalates the ticket.

    Every message, routed by intent
  3. No portal: it all happens in Teams

    Staff ask for software, hardware or access in plain English, and Hartley matches the catalog item and submits it with one confirmation. Incidents go to the IT support channel and requests to a separate IT-Requests channel, so each team sees only its own work. Tickets can be checked, commented on and escalated in the chat.

    No portal: it all happens in Teams
  4. Six flows to try after deployment

    Each core flow can be tested in Teams once Hartley is deployed: a fix from the knowledge base, a new incident when there is no match, an alert to the IT channel, an open ticket found instead of a duplicate, a software request with a tracking number, and a list of your open tickets.

    Six flows to try after deployment
  5. Runs inside your environment

    The employee in Teams talks to the Hartley agent in Copilot Studio, which reaches ServiceNow through the MCP Gateway on Azure App Service. Users sign in with their existing Microsoft 365 identity, it works on Teams desktop, mobile and web, and no data leaves your Microsoft tenant or ServiceNow instance.

    Runs inside your environment
The film · 0:43

See Hartley in motion

Sample data · synthetic demo
The problem

What Hartley catches

Case 01

The fix was already written down

A staff member's Outlook stops sending email. They raise a ticket and wait, though the steps to fix it are already in the knowledge base.

Red flag: A matching knowledge article: Hartley presents its steps in the chat and no ticket is raised.

Case 02

The same problem, reported twice

Someone reports an issue again because they haven't heard back. A second ticket would only split the work.

Red flag: An open ticket for the same issue: Hartley shows its status instead of creating a duplicate.

Case 03

A ticket nobody has seen

A printer won't connect and nothing in the knowledge base helps. The ticket goes into a queue and waits for triage.

Red flag: No article matched: the incident is raised and a card goes to the IT support channel with the issue and the employee's contact.

Case 04

A software request lost in email

Someone needs Adobe Acrobat and asks around for the right form.

Red flag: A catalog item matched from plain words: the request is submitted with a tracking number after one confirmation.

Stage by stage

How work moves through Hartley

  1. Ask in Teams

    The staff member writes the problem or request in a chat with Hartley, on desktop, mobile or web. No portal and no separate login.

  2. Sort by intent

    Hartley decides whether the message is an issue, a request, or about an existing ticket, and routes it to that flow.

  3. Check, then search

    For an issue it looks for an open ticket first, then searches the knowledge base with up to three keyword variations.

  4. Walk through the fix

    It presents the article step by step and asks whether the problem is solved. Most issues end here, with no ticket.

  5. Raise and alert

    If the fix doesn't work, or the person asks, it raises a ServiceNow incident with the whole conversation and posts a card to the IT support channel.

  6. Track the ticket

    Later, the person can ask for status, add a comment or raise the priority in the same chat.

Ground rules

Promises it always keeps

  • Knowledge base first, ticket last

    A ticket is raised only when the knowledge base can't resolve the issue, or when the person asks for one.

  • No duplicate tickets

    An open ticket for the same issue is shown, not created again.

  • Context travels with the ticket

    Every ticket includes the full conversation, so nothing has to be asked twice.

  • Incidents and requests kept apart

    Incidents go to the IT support channel and software requests to the IT-Requests channel. Each team sees only what is relevant.

  • Non-standard requests go to people

    Approved catalog items are confirmed and submitted. Anything non-standard is passed to the IT-Requests channel.

  • Suggestions, reviewed by you

    Suggested fixes, catalog matches and ticket recommendations are suggestions only, for your organisation to review before acting on them.

Under the hood

What's inside Hartley

Hartley agent

The conversation itself, built in Microsoft Copilot Studio and published to Microsoft Teams.

MCP Gateway

Runs on Azure App Service in your subscription and connects the agent to ServiceNow over HTTPS.

ServiceNow

Your own instance: ITSM for incidents, the Knowledge Base for fixes, and the Service Catalog for requests.

Channel flows

Power Automate flows that post notification cards to your IT support and IT-Requests channels in Teams.

Microsoft Entra ID

Signs users in with their existing Microsoft 365 identity. No new credentials to manage or rotate.

Key Vault and Application Insights

Deployed with the gateway in your subscription: Key Vault for its secrets, Application Insights for its logs.

By design

What it deliberately won't do

  • It won't: Need a new portal or app

    If your staff have Microsoft Teams, they have Hartley. Nothing else to install.

  • It won't: Keep a copy of your data

    BISTEC Global does not access, store or process your data. Retention follows your own Azure and ServiceNow policies.

  • It won't: Raise a ticket for a solved issue

    If the knowledge base article fixes it, no ticket is created, unless the person asks for one.

  • It won't: Replace ServiceNow

    Tickets, articles and catalog items stay in your ServiceNow instance. Hartley is a way in, not a new data silo.

  • It won't: Ask staff for another password

    Sign-in uses Microsoft Entra ID, with the identity people already have.

  • It won't: Include the platform subscriptions

    Azure, ServiceNow, Microsoft 365, Copilot Studio and Power Automate are needed and are not part of the Marketplace listing.

Technical details

Four parts in a line: the employee in Microsoft Teams, the Hartley agent in Microsoft Copilot Studio, the MCP Gateway on Azure App Service, and ServiceNow (ITSM, Knowledge Base and Service Catalog). The gateway is deployed from Azure Marketplace as a managed application and provisions an App Service, Key Vault and Application Insights in your own subscription. It accepts HTTPS connections only and reports its state on a /health endpoint. Users sign in with Microsoft Entra ID through their existing Microsoft 365 identity; the agent's connector uses OAuth 2.0 with delegated permissions. Teams presence and chat use Microsoft Graph with delegated permissions. Channel notifications are Power Automate flows called by webhook, posting adaptive cards to the Teams channels you choose. Setup has three phases, about 30 minutes in all by the install guide: deploy the gateway (about 10 minutes of deployment), import the Copilot Studio agent from AppSource or as a managed solution and point it at the gateway, then give users the right Entra and Power Platform roles. It needs a Microsoft Azure subscription, a ServiceNow instance with ITSM, Knowledge Base and Service Catalog, Microsoft 365 with Teams, a Copilot Studio licence and Power Automate; these are not included in the Marketplace listing. A free ServiceNow developer instance can be used for evaluation. A VAPT certificate is available on request.

Target audience

IT service managers and service desk leads running ServiceNow and Microsoft Teams, who want staff to solve common issues themselves and want fewer tickets, each with its full context. Also the IT support team that receives the channel alerts, and the Microsoft 365 and Azure administrators who deploy it.

Questions

Does any of our data leave our tenant?

No. Everything is processed within your Azure subscription and ServiceNow instance. BISTEC Global does not access, store or process your data, and retention follows your own Azure and ServiceNow policies.

What do we need to run it?

A Microsoft Azure subscription, a ServiceNow instance with ITSM, Knowledge Base and Service Catalog, Microsoft 365 with Teams, a Microsoft Copilot Studio licence, and Power Automate for the channel notifications. These are not included in the Marketplace listing.

How long does it take to deploy?

The gateway deploys from Azure Marketplace in about 10 minutes, with no code to install. The install guide puts the whole setup, including the Copilot Studio agent and user onboarding, at about 30 minutes.

When does Hartley create a ticket?

Only when the knowledge base can't resolve the issue, or when the person asks for one. The ticket includes the whole conversation.

Will it raise duplicate tickets?

No. If the person already has an open ticket for the issue, Hartley shows its current status instead.

Do staff need a new login or app?

No. They sign in with their existing Microsoft 365 identity, and Hartley works wherever Teams does: desktop, mobile and web.

Who gets told when Hartley can't help?

Your IT support channel in Teams gets a notification card with the issue and the employee's details. Software requests go to a separate IT-Requests channel.

Can we try it before going live?

Yes. A free ServiceNow developer instance can be used for evaluation, and the terms ask you to test in a non-production environment before production.

Are Hartley's answers final?

No. Suggested fixes, catalog matches and ticket recommendations are suggestions only, and your organisation reviews them before acting on them.

Book a demo

See any of the nine running on your own use case.

A 30-minute walkthrough with the team that built it.

Email us
hello@bistecglobal.com

Offices in Sydney and Colombo.

bistecglobal.com
© 2026 BISTEC Global · Intelligent design. Engineered for adaptability.Demos on this page use sample data.