# manual verification system

### ✎ .verify \[user] (manual verification) command

* this command is useful for servers with "gates" to them, where some "gatekeepers" can manually verify the user after they have posted a valid introduction or some other form of verification requirement.

`/autoresponder add trigger:.verify reply:{requirearg:1|user} {requirerole:gatekeepers} {delete} {addrole:verified | [$1]}{embed} verified [$1]!`

`/autoresponder editmatchmode trigger:.verify matchmode:startswith`

* you can also have it so that once the user is verified, it sends a premade embed that greets the user in the chat channel, so that they get notified:

`/autoresponder add trigger:.verify reply:{requirearg:1|user} {requirerole:gatekeepers} {delete} {addrole:verified | [$1]} {sendto: #general} [$1] {embed:greet}` 


---

# 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.mimu.bot/autoresponder/resources/autoresponder-examples/manager-moderation-commands/manual-verification-system.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.