Configure close condition

---
title: Configure close condition
description: Configure the condition to exclude the chat conversation from auto importing.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/employee-service-management/employee-experience-foundation/configure-close-condition.html
release: brazil
product: Employee Experience Foundation
classification: employee-experience-foundation
topic_type: task
last_updated: "2026-09-10"
reading_time_minutes: 1
breadcrumb: [Import messages from Microsoft Teams to ServiceNow, HR Service Delivery integration, Microsoft Teams Integration for Employee Experience, Configure, ServiceNow for Microsoft Teams and Microsoft 365, EmployeeWorks, Employee Service Management]
---

# Configure close condition

Configure the condition to exclude the chat conversation from auto importing.

## Before you begin

Role required: admin

## About this task

When a ticket is set to inactive, the system does one final poll for any messages in the chat, removes the participants such that no further messages about the ticket can be exchanged in the chat, and then stops polling that chat. This is determined by the "active" field on a table being set to "false".

For any table with an active field, this behavior works automatically. If your custom application does not use an "active" field for determining whether the ticket remains active, define an alternate condition that can be used to denote the ticket as being closed or inactive.

Alternately, to adhere to platform standards, consider adding an active field to your custom application and maintaining the state of that field in accordance with the business logic of your application.

## Procedure

1.  Navigate to **All** > **ServiceNow for Microsoft 365** > **Chat Administration** > **Close Conditions**.

2.  Click **New**.

    \[Omitted image "configure-close-condition.png"\] Alt text: Configure close condition

3.  On the form, fill in the fields.

    |Field|Description|
    |:----|:----------|
    |Table|Option to select a table to which the requester mapping \(auto-import feature\) should be applicable.|
    |Inherit|Extend and apply the auto-import feature to the child tables.|
    |Active|Option to activate the requester-mapping record.|
    |Close conditions|Condition builder to define a condition that the record is closed.|

4.  Click **Submit**.

    **Note:**

    If you are creating a close condition for a new table, ensure to create business rule for close condition. For more information, refer [Configure business rule for close condition](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/employee-service-management/employee-experience-foundation/business-rule-close-condition.md).


**Parent Topic:**[Configure Request-based chats to import messages from Microsoft Teams to ServiceNow](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/employee-service-management/employee-experience-foundation/auto-import-messages.md)