Home > Configuring and Using File Exchange
Categories: Chat Agent Docs
(Last Updated On: March 7, 2019)
SnapEngage makes is easy to exchange files during a visitor chat. With just a click of a button your agents and website visitors will be able to upload and download files directly with one another without having to resort to using email or another service.
To activate the File Exchange feature sign into to your SnapEngage account and click on Options tab underneath in the Settings section. The File Exchange section is found near the bottom:
Simply click on the checkbox to the right of “Enable visitors and agents to exchange files during a chat” label and click on the “Save” button. Conversely, if you wish to disable the feature uncheck the option and click on the “Save” button.
If during the course of a chat the agent wants to send a file to the visitor they simply need to click on the “Actions” button to the right of the message input field to yield a menu and pick “Send a File” :
After doing so the agent then needs to find (1) and select (2) the file they wish to upload :
and then click on the “Send” button (3):
Once that’s done the file will appear in the transcript on both the agent side:
and visitor side:
If during the course of a chat the agent wants to receive a file from the visitor they need to initiate the exchange by clicking on the “Actions” button which will yield a menu and then they need to pick “Request a File” :
After doing so the visitor will then see a file upload form and can click on “Upload” :
Once the visitor selects the file then both the visitor and agent will see it in the chat transcript:
As a bonus: If the uploaded file is either a png, gif or jpg a preview of the image will be shown.
Any files exchanged during the chat will be linked in the chat transcript within whichever integration is configured. For Email and Zendesk integrations copies of the files will be included as well.
- File Exchange is only available via Conversations Hub.
- The maximum file upload size is capped at 32 MB.
- This feature is HIPAA compliant.
Published June 3, 2015