Overview
The community agent begins with a separate account on the relevant platform. The account should belong to the bot rather than impersonating the operator's personal account. Hermes receives the credentials, the role definition, example behavior, and the schedule it should follow.
A practical operating rhythm includes:
- A morning check for new posts and unanswered questions.
- A midday reply sweep.
- An evening summary of activity and unresolved issues.
- A weekly learning pass that reviews what members asked and what information should be retained or
converted into a better response process.
Hermes can answer routine questions in the configured voice, create useful prompts or dashboards, moderate activity, and report sentiment to the owner. When a question requires human judgment, it can leave the item visible for review rather than allowing it to disappear in the feed.
Email support can be added through AgentMail. The user creates an inbox and API key, gives the credentials to the correct Hermes profile, and asks Hermes to onboard itself. A test message confirms that the agent can send from its own address. Incoming requests can then be summarized, drafted, organized, followed up, or converted into Multica issues.