Chatting With Your Developer

Every fix request has its own conversation with the BugShield team. Keeping messages inside the request gives both sides the context, files and decisions needed to complete the work.

What to use the conversation for

• Answer questions from the developer working on your request.
• Share any new information you discover after submitting the request.
• Let the developer know when requested access has been added to the Vault.
• Confirm any choices or approvals needed to continue the work.
• Add a screenshot or file when the developer requests one or it helps explain a new detail.

Keep credentials in the Vault

Do not paste passwords, secret keys or hosting credentials into chat. Add or update the appropriate Vault item. If the developer requests a credential type, fulfil that request from the site Vault so access remains controlled and logged.

Reply to the current issue

Use replies or quoted messages when a conversation contains several points. Keep unrelated faults in separate fix requests so scope, status and payment remain clear.

Attachments and privacy

Before uploading an image or document, remove customer data, card information, API secrets and anything not needed for diagnosis. The request workspace shows shared attachments alongside the conversation.

After completion

Read the final developer message and test the original workflow. You can return to the completed request at any time to review the conversation. If you would like a copy for your records, open the completed request and select Email chat transcript in the Request complete panel at the top of the page. BugShield will send the transcript to you by email.