> For the complete documentation index, see [llms.txt](https://help.uchat.com.au/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.uchat.com.au/viber-chatbot/viber-limitations.md). # Viber Limitations **1- Location** Share location option is only available on mobile phones and not on desktop **2- File** The file uploaded by the user will be sent to Viber and UChat will get a URL link for the file. You are unable to put this URL link in a "Send Message - File" because the link from Viber is not a direct file link. Alternatively, to send the file back to your user, you can use "Send Message - Text" to print the link, the user can tap the link to download the file. **3- Send Message** * For Each: JSON should be under 2000 characters. * Ecommerce: The JSON should be under 2000 characters so you might be unable to list 10 products per page according to your products information length (try 5 or 6 per page). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.uchat.com.au/viber-chatbot/viber-limitations.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.