Server health polling

On a schedule, an agent reads the metrics ReisHost exposes in its dashboard, such as uptime, load, and resource use per server. It compares each reading against your threshold rules and, when a server crosses a limit, opens a ticket, updates the affected account record, and notifies the owner. Readings inside normal range are recorded and left alone. When metrics spike in a pattern the rules do not cover, several servers degrade at once, or a reading looks implausible, the agent escalates to an infrastructure engineer with the collected data rather than acting on its own.

Support ticket triage

Incoming ReisHost tickets get read as they arrive, including the message, the account, and the server involved. The agent classifies each against your support rules, sets priority, tags the topic, and either posts a known answer or assigns the ticket to the right queue. Routine questions about the dashboard or account get resolved directly. Tickets that mention data loss, billing disputes, or hardware faults, or that carry an angry tone the rules cannot judge safely, are raised to a human support lead with a short summary and the account history attached.

Billing and renewal updates

Ahead of a renewal date, the agent reads the account record, plan, and payment status held in ReisHost. It applies your billing rules, updates the record, and notifies the customer about upcoming charges or an expiring plan. Straightforward renewals with a valid payment method proceed and get logged. Failed payments, mismatched plan details, or a request to drop below a supported tier are held back and routed to a billing owner. The agent never changes a price or cancels a server on its own; it prepares the change and waits for a person to approve.