> For the complete documentation index, see [llms.txt](https://docs.intelligems.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intelligems.io/post-purchase-experiences/getting-started-with-post-purchase-upsells/post-purchase-experience-use-cases/the-countdown-question.md).

# The Countdown Question

The post-purchase offer already expires. Shopify holds the order for up to 60 minutes, and once the shopper accepts, declines, or the window closes, the order goes to fulfillment. The countdown timer makes that deadline visible.

It's off by default, which makes on-versus-off a clean test.

*What this test design might look like:*

|                     | **Control** | **Variant A**  |
| ------------------- | ----------- | -------------- |
| **Countdown timer** | Off         | On, 10 minutes |

{% hint style="info" %}
The timer duration has to be equal to or less than the **Offer expires after** value in General Settings. Decide what happens when it runs out too: the timer can disappear, or it can show expired text you write.
{% endhint %}

If the timer wins, the same setting is worth revisiting alongside your offer expiration. A shorter hold with a shorter timer is a different test from a visible deadline on the full 60 minutes. Both live in General Settings, covered in [How to Set Up a Post-Purchase Upsell Experience](/post-purchase-experiences/getting-started-with-post-purchase-upsells/how-to-set-up-a-post-purchase-upsell-personalization-or-test.md).


---

# 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://docs.intelligems.io/post-purchase-experiences/getting-started-with-post-purchase-upsells/post-purchase-experience-use-cases/the-countdown-question.md?ask=<question>&goal=<user_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.