> For the complete documentation index, see [llms.txt](https://docs.tracr.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tracr.com/tracr-user-guide/coming-soon.md).

# Coming Soon

## Q4 2026

### QR Codes

We understand that sometimes a Tracr ID or URL to a diamond experience can be lengthy, so are currently building the functionality to generate QR codes for a singular diamond. User will have the option to generate these with a branded Tracr logo, or without. They will also have the option to download them as an SVG or PNG.

### Unlock Reporting in Portal

We've taken your feedback and recognise that receiving an unitemised invoice can be confusing. We are not able to fully support an itemised invoice at the minute, but we are currently building a tool within the portal to allow you to see all the diamonds you unlock. You will be able to filter on this report to match it with your invoice, allowing you to perform a reconciliation.

&#x20;


---

# 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.tracr.com/tracr-user-guide/coming-soon.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.
