> For the complete documentation index, see [llms.txt](https://docs.rewst.help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rewst.help/updates/roc-open-mics/roc-open-mics-north-america/2025-roc-open-mics/may-16-2025-secure-your-help-desk-with-face-match-automation.md).

# May 16, 2025: Secure Your Help Desk with Face Match Automation

### **Join Live!**

Join us live every Friday at 3 pm EST!

[Download the Calendar Invite here](https://engine.rewst.io/webhooks/custom/trigger/02eb02e2-1177-43d9-9e13-8547414979fc/c47fdd7f-4075-47a8-ba92-94e790e67c06?request_type=open_mic_link&)!

## Open Mic Video Recording

{% embed url="<https://youtu.be/0VAaMvC0n-g>" %}

### Contents of the Recording:

* 🎙️ "Aharon" opens with reminders about the call, Flow registration urgency, and the importance of asking questions to succeed with automation.
* 📹 George encourages community content contributions for Workflow Wednesday and shares a success story.
* 🛠️ Danial presents updates like “no validate” in Halo PSA, new ServiceNow triggers, and UI improvements.
* 📦 JP shares marketplace progress on bug fixes, transforms, and upcoming refactors.
* 🏫 Clea gives shoutouts to new certification earners and highlights updates to Cluck University’s layout and calendar.
* 🔐 Stephen demos a face-checking workflow using Entra Verified ID to securely verify identities across tenants.
* 📦 Jen shares a QR-based label and inventory tracking workflow using Halo and Roost to manage tech items.
* 🤖 Emmitt shows a workflow using Teams bots to track ticket status changes and escalate after delays.
* ⚙️ Owen demos a GitHub-shared workflow for monitoring admin password alerts via Microsoft Graph.
* 🧪 Ben shares form tips like markdown tricks, prefilled fields, and hidden metadata use cases.
* 💬 Q\&A covers crate improvement requests, folder features, filtering execution history, error handling in workflows, and onboarding edge cases.

<details>

<summary><strong>How to Get Help</strong></summary>

* 💬 Chat (Discord): [https://discord.gg/rewst​​](https://discord.gg/rewst%E2%80%8B%E2%80%8B)
  * Private #{{ msp }} channel
  * \#the-kewp
* 🎫 Submit Tickets to: <the_roc@rewst.io>
* 📝 Feature Request + Integration Requests: <https://rewst.canny.io/>

**CLUCK UNIVERSITY – REWST TRAINING:**

* 👨‍🏫 Live Instructor-Led Training: <https://calendly.com/cluck-u/>
* 🏁 Rewst Foundations Training: <https://docs.rewst.help/cluck-university/rewst-foundations-10x>
* ▶️ On-demand Videos: <https://docs.rewst.help/cluck-university/rewst-foundations-10x>

**DOCS:**

* 🥚 Rewst Docs: <https://docs.rewst.help>
* ⛩️ Jinja Docs: <https://jinja.palletsprojects.com/>

**KEY LINKS:**

* 📝 Feature Request + Integration Requests: <https://rewst.canny.io/>

</details>


---

# 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.rewst.help/updates/roc-open-mics/roc-open-mics-north-america/2025-roc-open-mics/may-16-2025-secure-your-help-desk-with-face-match-automation.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.