> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/pro/operations/service-instances.md). # Service instances Service instances of all customers in Equipme Pro: list of provided services, search by customer, employee or attribute value (e.g. serial number), and product instances with budget. **Path:** "Operations" → "Service instances" A **service instance** is a specific service at a customer, e.g. an employee's notebook, a software license or a mobile phone contract. Here you see all service instances you have provided for your customers and quickly find individual devices again. The page has three tabs. ## "Services provided" tab A list of all service instances across all customers. The data is loaded page by page. Columns: | Column | Content | | ----------------------------------- | ----------------------------------------------------------------- | | "Id" | Number of the service instance | | "Service name" | The provided service | | "Customer" | Which customer it belongs to | | "Supplier" | Who supplies the service (you or a partner) | | "Location", "Employee", "Email" | Assignment at the customer | | "Activation date", "Remaining term" | Contract start and remaining term | | "Inventory number" | The customer's inventory number | | "Active" | Whether the contract is active | | "One-time cost", "Recurring cost" | Prices of the service | | "Additional information" | Further stored details | | "Status" | Current status, e.g. "Active", "Ready for delivery", "In removal" | You can sort, search and export to Excel using the table functions. Clicking a row opens the service instance's detail view. {% hint style="info" %} Not every instance can be opened. If the customer provides the service themselves, Pro reports: "This service instance is provided internally by the customer. To access the details, please use the customer portal." If the service comes from a partner supplier, you also cannot open the details. {% endhint %} ## "Search for service" tab Here you specifically find an employee's services or a particular device. There are two mutually exclusive ways to search: **By customer and employee** 1. Select the customer under "Customer". 2. Select the employee in the employee field. The "Without assignment" option shows all of the customer's services without an employee assignment, e.g. warehouse devices or location devices. **OR by attribute value** 1. In the "Attribute value" field, enter e.g. a serial number, IMEI or inventory number. 2. Search with Enter or the magnifying glass. The search runs across all customers. With "Hide canceled and removed instances" (active by default), you hide terminated services. Use the search field above the results to filter the hits further. The results show name, employee, customer, location, status and attributes. Clicking a result opens the service instance. ## "Search for product instances" tab "Select a product to display related services and their resulting budgets." This answers questions like "Which customers use model X, and what do these services cost?". 1. Optionally select a category to narrow down the product selection. 2. Select one or more products. For each hit, the table shows "Customer", "Assignment", "Service", "Product", "Version", "Attributes" and "Cost/unit". "Total number" and "Total budget" are shown at the top right. Clicking a row opens the service instance. ## The detail view The detail view of a service instance is the same as in fulfillment. There you find the tabs "Service instance", "Order", "Changes", "Cancellations", "Add-ons" and "Software" (see [Open positions](/pro/fulfillment/open-positions.md#the-detail-view-of-a-service-instance)). Typical day-to-day tasks: * **Maintain components**: Under "Service components", change attributes ("Change attribute values"), add a component with "New" or swap a component with "Replace" (see [Service changes](/pro/fulfillment/service-changes.md#replace-a-component-replacement)). * **Edit the inventory number**: in the "Overview" via the pencil icon (Fulfillment Operator, Fulfillment Manager or Administrator). * Add **additional information and attachments**, e.g. warranty documents. * Save an **internal note** that only your team sees. * **Open the instance in the portal** if you are allowed to switch to this customer's customer portal. ## Permission Users with read access to fulfillment, e.g. "Fulfillment Controller", can see the service instances. Changes to service instances (inventory number, components, status) require "Fulfillment Operator", "Fulfillment Manager" or "Administrator". How customers see their own services is described in the customer guide ("Inventory"). You can also view and manage customers' inventory in the [customer details](/pro/customers/customer-details.md). ## Frequently asked questions **I only know a device's serial number. How do I find it?** Go to the "Search for service" tab, enter the serial number in the "Attribute value" field and search. The search runs across all customers. **Why are customer and employee grayed out?** You have already entered an attribute value. Clear the field to search by customer and employee again, and vice versa. **Why can't I find a canceled service?** "Hide canceled and removed instances" is active. Uncheck it. --- # 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://hub.equipme.io/pro/operations/service-instances.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.