Chatting With Your Developer

Every active fix request includes a direct chat thread with the developer assigned to your site. Use it to share updates, answer questions, and confirm when something is fixed.

This article explains chat best practices, including replying quickly when updates are needed, keeping passwords in the Vault, and keeping each chat focused on one issue.

Best practices

• Reply promptly when status is Awaiting Response. Delays can pause work.
• Do not share passwords in chat. Use the Vault instead.
• Keep messages focused on the current issue. Open a new fix request for unrelated problems.

Chat history is saved when the fix is closed so you have a record of what was done.