> For the complete documentation index, see [llms.txt](https://help.supplyd.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.supplyd.co/mcp/getting-started/ask-your-first-questions.md).

# Ask your first questions

Example prompts for checking your Supply'd connection and getting useful answers.

You do not need to know MCP tool names. Ask about Supply'd in ordinary language and include enough context to identify the records you mean.

## A quick connection check

Try these in order:

1. **“What Supply'd information can you access for me?”**
2. **“Show my five most recent sales orders.”**
3. **“Open the newest order and summarise its items and status.”**

This checks discovery, search and a follow-up using the returned record.

## Useful first questions

### Products and production

* “Find the product with SKU ABC-123.”
* “Show its ingredients, recipe stages, method, labour time and processing time.”
* “When was it last produced?”
* “Show the last five production runs and their quantities.”

### Sales and customers

* “Compare sales this week with last week.”
* “Show this customer's latest orders.”
* “Which products has this customer bought most often?”

### Purchases and inventory

* “Which purchase-order items are still outstanding?”
* “How much of this product is available by warehouse?”
* “Show batches of this product that expire in the next 30 days.”

### Deliveries and work

* “Which deliveries are scheduled for today?”
* “Show the progress of this fulfilment.”
* “What open tasks are assigned to my department?”

## Tips for better answers

* Include a date range, warehouse, customer, supplier or status when it matters.
* Use an exact SKU, order number or returned record ID when names are similar.
* If the result is large, ask for a narrower period or the first few records.
* For follow-ups, say “this product” or repeat its name or SKU if the client loses context.
* Verify important operational or financial decisions in Supply'd before acting on an AI summary.

## Try the expanded capabilities

* “Show our company locations and departments.”
* “Find related recipes and substitutes for SKU ABC-123.”
* “Which suppliers and sales channels are linked to this product?”
* “Show this product's sales and purchase history for last month.”
* “Show inventory activity for this batch.”
* “Compare this expense's purchase-order lines, scanned invoice and saved values. Which differences explain the mismatch?”

Use records you can already view in Supply'd. In ChatGPT, mention **@Supply'd** again when a follow-up needs another data retrieval. In other clients, ensure the connector remains enabled.


---

# 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://help.supplyd.co/mcp/getting-started/ask-your-first-questions.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.