Chatbot session timeout· Conversation state
Chatbot Session Timeout — How Long Silence Lasts Before a Chat Resets
Quick answer: A session timeout is a clock that restarts every time the customer writes. If the clock runs out, the platform considers the session over. The customer may still see the old messages on screen, but the bot may have forgotten what it was in the middle of: the order number it just asked for, the step of the form, the topic. That is separate from how long you store the transcript.
Session timeout versus history retention versus context window
These three are often confused because all of them involve "how long the bot remembers."
| Session timeout | Conversation history retention | Context window | |
|---|---|---|---|
| What it limits | Silence before the session ends | How long records are stored | How much text the model reads per reply |
| Measured in | Minutes to days | Days to years | Tokens |
| Who sets it | Platform setting or your code | Your policy and legal advice | The model |
| Typical failure | Bot forgets mid-task | Records kept longer than allowed, or deleted too soon | Early messages dropped from a long chat |
| Where to read more | This entry | Data retention policy | Chatbot context window |
A bot can time out after 30 minutes and still keep the transcript for a year. It can also keep a session open for a day and delete the transcript the same night. The two are independent settings, so decide each on purpose.
What three vendors document
These pages show how different the same idea looks in practice. Each is vendor documentation and may change.
Google Dialogflow CX. Its session page says a session stays active and its data is stored for 30 minutes after the last request. You can extend this with a session time-to-live setting, which the page says has a maximum of 24 hours. It also describes saving the current page and parameters yourself and sending them back later to restore state under a new session ID, without restoring the handler call stack. The page does not say what happens to a session at the moment it expires, or whether a request resets the extended timer.
Microsoft Copilot Studio. Its inactivity trigger page describes a trigger that runs a topic you build when a user sends no message for a set time. The duration can be set in seconds up to 604,800 (seven days), the timer resets on every user message, and the dropdown offers 15, 30, 45 minutes or one hour as presets. The page says the conversation ends only if your topic calls the End conversation action; it does not state a platform default timeout, and it notes that behavior differs by channel (for example it is not supported for telephony and has caveats in Microsoft Teams).
Intercom. Its article on auto-closing inactive conversations describes a workflow template: after a wait period (3 days by default, adjustable) a check-in message is sent, the conversation is snoozed (1 day by default), and if there is still no reply a closing notice is sent and the conversation is closed. The article discusses conversations where a teammate was waiting for the customer; it does not say whether bot-only or Fin conversations are affected, or what plan is required.
The pattern: one platform ends sessions on a fixed clock, one lets you build the behavior, one works on the scale of days in a ticketing inbox. "The timeout" is not one number you can look up.
What happens to the customer
- Nothing visible. The chat window still shows the old messages. The next reply behaves as a new conversation, which feels like the bot "forgot."
- A reminder, then a close. The bot nudges after a short gap, then closes with a note on how to restart. See reprompt.
- A resume. The bot detects the returning customer and offers to continue or start again.
- A handoff. If a person was involved, the timeout rules differ; see human handoff.
What to check in any platform
- Default. Is there one, and where is it stated?
- What resets the timer. Customer messages only, or also bot messages?
- What expiry clears. Collected answers, the current step, the transcript, or all of them?
- Per-channel behavior. Web chat, messaging apps and voice can differ.
- Reminder and close messages. Are they built in or yours to write?
- Relation to retention. Does expiry delete anything, or only end the session?
Why it matters for metrics
A conversation closed by a timeout is not the same as one resolved. If timeouts are counted as "resolved" or as "abandoned" without a rule, your numbers shift when you change the clock. See chatbot abandonment rate.
FAQ
What is a chatbot session timeout? The period of customer silence after which a chatbot platform ends the session and may clear its working memory.
How long should a chatbot session last? There is no standard. Dialogflow CX documents a 30-minute default; Copilot Studio documents no default for its inactivity trigger; Intercom's template works in days. Choose from how long your customers really pause, then test.
Is session timeout the same as conversation history retention? No. Timeout is about silence and the live session. Retention is about how long records are stored. They are set separately.
Why does my chatbot forget what we were talking about? Often the session expired and the bot started a new one, or the conversation outgrew the model's context window. Those are different causes with different fixes.
Can a customer resume after a timeout? Only if you build it, for example by saving the state and restoring it, as Dialogflow CX's page describes. Not all platforms offer this by default.
Does a timeout delete the chat? Not necessarily. Check what your platform clears at expiry, and keep that separate from your retention rules.
Related terms
- Session context — what the bot remembers inside one session.
- Chatbot context window — the model's per-reply input limit.
- Data retention policy — how long records are kept.
- Chatbot abandonment rate — the metric a timeout can distort.
- Human handoff — when a person joins, timeout rules change.
- Reprompt — the nudge before a session closes.
- Chatbot greeting message — what a returning customer sees first.
Sources
- Google Cloud, Dialogflow CX: Session — docs.cloud.google.com/dialogflow/cx/docs/concept/session, read 6 November 2026. Source of the 30-minute default, the 24-hour maximum for the extended lifetime, and the restore-state option. Does not describe expiry behavior.
- Microsoft, Inactivity trigger guidance (Copilot Studio) — learn.microsoft.com/en-gb/microsoft-copilot-studio/guidance/inactivity-trigger-guidance, read 6 November 2026. Source of the configurable duration, seven-day maximum, timer reset and End conversation behavior. States no default timeout.
- Intercom, Auto-close inactive conversations — intercom.com/help/en/articles/9636573-auto-close-inactive-conversations, read 6 November 2026. Source of the check-in, snooze and close workflow and its default timings. Silent on bot-only conversations and plan requirements.
- Chatbotscape evaluation methodology. /methodology (continuously updated).