Have something to say?

Tell us how we could make the product more useful to you.

Instagram Video Thumbnail Not Displayed When Sending Links

Feature Category Media Preview and Link Rendering Description When sending an Instagram video link through Periskope, the preview thumbnail is not correctly displayed. Instead of showing the actual video thumbnail, the system displays the default Instagram logo. Example URL for validation: https://www.instagram.com/reel/DTtY2l4ErWx/⁠ This link can be used to confirm that Instagram video thumbnails are not being properly retrieved and rendered, as the preview consistently falls back to the default Instagram logo. This behavior reduces the visual quality and clarity of the message, especially when sharing video content where the thumbnail is important to understand the context. Proposed Solution Ensure that Instagram video links generate and display the correct preview thumbnail instead of the default Instagram logo. Proposed behavior: When an Instagram video link is sent, Periskope fetches and displays the actual video thumbnail. The preview should match the behavior typically seen in native messaging environments where thumbnails reflect the content of the video. If thumbnail retrieval fails, fallback behavior can be applied, but the system should prioritize displaying the correct media preview whenever possible. Problem Being Solved Users cannot visually identify the content of an Instagram video from the preview, which reduces engagement and clarity in conversations. Why This Matters Video thumbnails provide immediate visual context and significantly improve message comprehension. Showing only the Instagram logo removes this context and makes messages less informative. This is particularly problematic for businesses that rely on visual content to communicate with customers or promote products. Expected Benefits Improved visual clarity of shared content Better user engagement with video links More professional presentation of messages Enhanced user experience when sharing media. Consistency with expected behavior from modern messaging platforms. Increased click through rates on shared video links Additional Context Accurate media previews are a standard expectation in messaging tools. Ensuring correct thumbnail rendering for Instagram links would align Periskope with common user expectations and improve overall communication quality.

Marco Rinaudo 11 days ago

WhatsApp Contact Name Bi Directional Sync

Feature Category Contacts Management and Data Synchronization Description Periskope currently imports contact names from WhatsApp and correctly displays them within the platform. However, when a contact name is created or updated inside Periskope, the change is not synchronized back to the WhatsApp App, including both the standard WhatsApp and WhatsApp Business versions. This results in a one way synchronization model where WhatsApp acts as the source, but Periskope cannot act as a source of truth for contact updates. Proposed Solution Implement bi directional synchronization of contact names between Periskope and WhatsApp. Proposed behavior: Periskope continues to import contact names from WhatsApp as it currently does. When a contact name is created or updated in Periskope, the change is pushed back to WhatsApp across all app variants. Contact updates remain consistent across all linked devices. Synchronization should handle conflicts intelligently, prioritizing the most recent update or allowing defined rules. Problem Being Solved Users frequently operate across both Periskope and the WhatsApp App. When contact names are not synchronized back, WhatsApp displays only phone numbers instead of identifiable names, making it difficult to manage conversations efficiently. Why This Matters Users often rely on multiple linked devices in WhatsApp. Without synchronization, contacts updated in Periskope are not recognizable in WhatsApp, leading to confusion and operational inefficiencies. Additionally, WhatsApp status visibility depends on saved contacts. If contacts cannot be properly created or updated from Periskope, those contacts may not be able to view published statuses. Lack of synchronization also increases the risk of human error, such as messaging the wrong contact due to unidentified numbers. Expected Benefits Consistent contact identification across all platforms Improved usability for teams switching between Periskope and WhatsApp Reduced confusion when handling conversations directly in WhatsApp Better alignment with WhatsApp features such as status visibility Reduced risk of human error when identifying contacts Improved operational speed for high volume messaging environments Centralized contact management with Periskope as a reliable source of truth Better team collaboration by ensuring all agents see the same contact names Enhanced CRM like capabilities by maintaining accurate and synchronized contact data Additional Context Many users continue to rely on the native WhatsApp applications alongside Periskope, especially when using multiple linked devices. Maintaining synchronized contact data is critical for operational clarity and efficiency.

Marco Rinaudo 14 days ago

Completed

Mobile App Media Library Local Cache

Feature Category Performance and User Experience Description Periskope allows users to select stored media files when sending WhatsApp messages. However, the current behavior appears to retrieve media from the server every time a user sends a file, even if the same media has already been used previously. This results in unnecessary delays and inefficient bandwidth usage, especially for teams that frequently reply with the same images, videos, documents, or other media files. Proposed Solution Implement a local caching system for media files in the mobile application. Proposed behavior: When a media file is used for the first time, it is retrieved from the server as it is today. The file is then cached locally within the mobile app. On subsequent uses, the file is loaded directly from the local cache instead of downloading it again. The application may optionally verify whether the remote file has been updated and refresh the cache only when necessary. Problem Being Solved Repeated downloads of the same media create unnecessary delays and reduce efficiency for users who frequently send identical media files in conversations. Expected Benefits Faster media selection and sending Improved responsiveness in the mobile app Reduced server requests Lower bandwidth consumption Better experience for high volume customer support environments Additional Context In many operational scenarios, a large percentage of WhatsApp replies reuse the same media assets repeatedly. Local caching would significantly improve efficiency and usability of the media library.

Marco Rinaudo 22 days ago

2

Native WhatsApp Business Labels Import and Bi Directional Sync

Currently Periskope offers a label system that is separate from the native label system available in the WhatsApp Business App. While the feature is useful, the labels exist only inside Periskope and are not synchronized with the labels that already exist in WhatsApp Business. This creates two parallel label systems, which leads to duplication and the loss of the original organizational structure already used inside WhatsApp Business. Proposed improvement: Implement native label import and bi directional synchronization with the WhatsApp Business label system. Suggested behavior: Periskope imports the existing native labels already attached to chats in WhatsApp Business. Synchronization occurs in both directions so that changes made in Periskope are reflected in WhatsApp Business and vice versa. Since WhatsApp Business currently limits native labels to 20, Periskope could synchronize the first 20 labels with WhatsApp. Periskope could still allow additional internal labels beyond the 20 limit. These additional labels would remain Periskope only and would not sync back to WhatsApp. Why this matters: Many users already rely heavily on WhatsApp Business native labels to organize conversations. Losing these labels during migration to Periskope would remove important historical categorization that has already been applied to many chats. Technical note: There is strong evidence that native labels are exportable and synchronized by WhatsApp itself. When linking additional devices to the WhatsApp Business App, the existing labels and their assignments are automatically replicated across devices. This suggests that label data is accessible and can be synchronized. Expected benefit: This feature would allow Periskope to integrate seamlessly with existing WhatsApp Business workflows while preserving the user’s existing chat organization.

Marco Rinaudo 22 days ago