Start with the game, language, available time, service scope, and price. If details become account-specific, keep them inside the signed-in account area when that flow is available.

Keep service descriptions clear, avoid employment wording, publish availability honestly, and accept orders only after the service profile is approved.

Use signed-in account areas for delivery notes, screenshots, timing changes, and dispute evidence when that flow is available. Public forum posts should stay general.

Describe the game, language, lobby length, communication boundary, and availability window before a buyer sends a service request.

Keep notes factual: service status, agreed scope, timestamps, user-visible messages, and the requested platform action.

Service information can be published after account setup, but service request acceptance remains locked until the service profile passes review.