When image upload in the widget helps
Letting visitors send images turns vague reports into actionable context—when you have designed for it. Use it where a screenshot removes five minutes of back-and-forth, not where it invites sensitive data you do not want in chat.
High-value scenarios
- Support— UI bugs, unexpected errors, misaligned layouts (“send a screenshot of what you see”).
- Implementation — wiring diagrams, console errors, config screens (with secrets blurred by the visitor).
- Sales / solutions — rough sketches of workflows or org charts prospects already share in calls.
Policy and instructions
State in custom instructions what you want the agent to do with images: confirm receipt, describe what it sees at a high level, never OCR credit cards or government IDs, and route ID verification to your official flow if applicable.
Tell visitors what not to upload (passwords, API keys, personal health records) in the welcome or in replies when you invite a screenshot.
Workflow handoff
Images should accelerate human follow-up, not replace it when policy requires a ticket. Pair upload with a clear next step: “I will flag this for support with your screenshot attached”—if that matches how you actually operate.