> For the complete documentation index, see [llms.txt](https://doc.batch.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.batch.com/release-notes/release-notes/january-20-new-dashboard-improvement.md).

# January 20, New dashboard improvement

Various experience improvements have been released:

* It is now possible to filter Campaign and Automation listings by Push Platform (Android, IOS, Web). Previously, it was only possible to filter by the entire push channel.
* It's now easier to identify the health of a Campaign or Automation directly from the listing with new metrics.
* Push channels activated on a push message are now displayed on each push step of the Automation Builder.
* The status (Draft, Running, Completed...) of the Orchestration is now displayed inside Orchestration forms.
* The targeting modal has been fully redesigned to offer a greater 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://doc.batch.com/release-notes/release-notes/january-20-new-dashboard-improvement.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.