# February 3, 2023 - AI generated diagnostics!

This call is for people who are:

* Interested in building their own workflows
* Wanting to stay on top of new developments
* Want to learn more about Rewst and participate in the community
* We will talk about the platform, news, some training, and any Q\&A.
* As always, feel free to unmute and interrupt us, this is an interactive call!

{% embed url="<https://www.youtube.com/embed/vVdkRcrBHnY>" %}

## Contents of the recording

<details>

<summary><strong>Contents of the Call</strong></summary>

On this ROC call, Nick starts us off as ever talking about the latest developments from the Development Team.

Then Matt from the ROC shows off his new workflow to manage calendar permissions from a form, discussing potential improvements around putting it in the hands of your clients themselves with a process approval!

We then move on to a discussion around the new AI generated diagnostics for your techs using ticket information!

We finish off with a few discussions the product roadmap, common issues and more!

</details>

<details>

<summary><strong>How to get help from the ROC</strong></summary>

How to get help - Engage the ROC in Slack - Email support coming soon! - \[FUTURE] Live chat in the app - Would this be helpful to people? - Documentation - <https://rewst.help> - Feature Requests - <https://rewst.canny.io/>

</details>


---

# Agent Instructions: 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:

```
GET https://docs.rewst.help/updates/roc-open-mics/roc-open-mics-north-america/2023-roc-open-mics/february-3rd-2023-ai-generated-diagnostics.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.