> This page is for version Scripted.
> For other versions, use one of these documentation indexes:
> - Generative (default): https://developers.ada.cx/generative/llms.txt
> - Scripted: https://developers.ada.cx/scripted/llms.txt

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://developers.ada.cx/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://developers.ada.cx/_mcp/server.

# Manage when your bot forgets customers

## Overview\[#UUID-bfcf145f-00d5-cf0b-fb4c-49726eb73dd2_id_360018115813_id_h_443fe9b3-5c82-48f8-b79e-3882a1d133cf]

Ada chatbots can remember a customer from one conversation to the next.
Bots store a record of the customer, their associated data, and their
chat history. This is called Customer Persistence.

But what if you don't want your bot to always remember the customers it
speaks with? No problem! You can use the Customer Persistence settings
to determine when your bot should *forget* a customer.

## Configure Customer Persistence\[#UUID-bfcf145f-00d5-cf0b-fb4c-49726eb73dd2_id_360018115813_id_h_01FK1MJM7GSK6XXNPQ3ESPSJ7Z]

Here’s how to access the Customer Persistence settings for your bot:

1. On the Ada dashboard, go to **Settings** > **Integrations**.

2. Under **Channels Integrations**, beside **Ada Web Chat**, click
   **Configure**. The Configure Web Chat window opens.

3. Click the **Persistence** tab.

4. From the drop-down menu, select your preferred Customer Persistence
   setting (see below).

5. Click **Save**.

## Customer Persistence settings\[#UUID-bfcf145f-00d5-cf0b-fb4c-49726eb73dd2_id_360018115813_id_h_01FK1MKRPMWRX4QQ278FD4VSV7]

There are four Customer Persistence settings to select from. Each is
outlined below.

<table>
  <tbody>
    <tr>
      <td>
        **Never Forget**
      </td>

      <td>
        The bot never forgets the chat history and saved variables,
        regardless of how the customer ends the conversation.

        > **Note**
        >
        > If the customer clears their browser history, the chat history is
        > cleared as well.
      </td>
    </tr>

    <tr>
      <td>
        **Forget After Tab Close**
      </td>

      <td>
        The bot forgets the chat history and saved variables if the
        customer closes the chat tab or window; however, the bot maintains the
        chat history and saved variables if the customer refreshes the page or
        links to a new page.

        > **Note**
        >
        > Each new tab behaves as a unique chat conversation. The customer's
        > conversation and data does not carry across tabs.
      </td>
    </tr>

    <tr>
      <td>
        **Forget After Reload**
      </td>

      <td>
        The bot forgets the chat history and saved variables if the
        customer leaves the webpage, or refreshes or closes their browser
        tab.
      </td>
    </tr>

    <tr>
      <td>
        **Forget After...**
      </td>

      <td>
        The bot forgets the chat history and saved variables after a
        predetermined time period that you define. This can be any number of
        minutes, hours, days, or weeks.
      </td>
    </tr>
  </tbody>
</table>

## Additional considerations\[#UUID-bfcf145f-00d5-cf0b-fb4c-49726eb73dd2_id_360018115813_id_h_01FPWRFMZRVCVNMJ46DW84FDA2]

* If your bot hands customers off to a live agent it is best practice to
  select either Never Forget or Forget After… Selecting Forget After Tab
  Close will result in each new tab behaving as a unique chat session.
  This can become problematic when the bot hands the customer off to a
  live agent. Multiple tabs with separate bot conversations may confuse
  the customer. They may even start another handoff request flow.

* When you select Never Forget, returning customers are not provided
  with the Greeting Answer. Thus, this setting is not recommended if you
  use the Greeting Answer to provide customers with important
  announcements such as realtime bug and outage updates.

* The Customer Info within the Conversations view contains a combination
  of customer and session data. This means that the bot may have
  collected variable data in a previous conversation.

---

Have any questions? Contact your Ada team, or email us at [](<mailto:help@ada.support%20%E2%80%9CHelp Docs inquiry%E2%80%9D>).