> For the complete documentation index, see [llms.txt](https://support.kea.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.kea.ai/kea-ai-customer-faqs/can-the-ai-take-an-order-over-the-phone-for-a-day-later-than-the-current-day.md).

# Can the AI take an order over the phone for a day later than the current day?

No — the AI can only process **same-day pickup orders**. This limitation is due to how orders are sent and handled by your POS system.&#x20;

[Learn about placing Same Day Scheduled Orders here.](https://support.kea.ai/kea-brand-portal-setup/placing-scheduled-orders-with-ai)

If a customer requests an order for a future date beyond today, that order would be treated as a **catering or special order**. In this case, the AI can:

* Offer to **text or email the customer your catering link**, or
* **Forward the call** to the store so a team member can take the order manually.

💡 **Tip:** If you frequently receive future-date orders, you may want to include a note in your greeting or menu prompts letting callers know about catering options — this helps set expectations and provides a smooth customer experience.


---

# 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://support.kea.ai/kea-ai-customer-faqs/can-the-ai-take-an-order-over-the-phone-for-a-day-later-than-the-current-day.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.
