Feature Requests

Join other users in helping making Sinosend better
New Filter Options for Transfers Panel ("Downloaded" and "Not Downloaded")
Hi Rishi, I would like to submit a feature request to expand the filtering capabilities within the Transfers dashboard to help users track client engagement more efficiently. A. Proposed Feature Currently, the existing Filter dropdown menu has All, Shared, Active, and Expired. Please add two new filter statuses: Downloaded Not Downloaded B. How it Should Work "Downloaded" Filter: Selecting this will display only the transfers where the recipient has clicked the link and successfully downloaded the files at least once. "Not Downloaded" Filter: Selecting this will isolate transfers that remain unread or un-downloaded by the recipient. C. Use Case & Pain Points Current Behavior: The existing dashboard filters by time or sharing status (All, Shared, Active, Expired), but it does not let users sort files based on recipient interaction. The Problem: For users handling dozens of daily transfers, manually checking the individual status logs of each transfer to see who has or hasn't grabbed their files is incredibly time-consuming. The Goal: A "Not Downloaded" filter creates a seamless way for users to instantly identify stalled projects. It allows them to quickly pull a list of outstanding transfers and send a gentle follow-up reminder ("nudge") to those specific clients, drastically improving workflow efficiency and follow-up management. Hope you will favorably review this suggestion to bring deeper tracking insights directly to the Transfers dashboard!
2
·
planned
Bulk Selection and Deletion for the Transfers Panel
Hi Rishi, I have a feature request aimed at improving file management and account cleanup efficiency for users. A. Proposed Feature Please introduce checkboxes for multi-selection and a "Bulk Delete" button within the Transfers dashboard. B. How it Should Work Multi-Selection Checkboxes: Add a checkbox next to each individual transfer row, along with a "Select All" checkbox at the top of the list (similar to the standard user interface in Gmail). Integration with Filters: Users should be able to apply existing filters (e.g., viewing only Expired or Active transfers etc.), click "Select All" to highlight that filtered group, and delete them simultaneously. Confirmation Prompt: To prevent accidental data loss, a quick confirmation pop-up (e.g., "Are you sure you want to delete X selected transfers?") should appear before final execution. C. Use Case & Pain Points Current Behavior: Users must manually delete old or expired transfers one by one. The Problem: For users who send dozens of files daily, the Transfers panel fills up rapidly over weeks and months. Deleting these entries individually is highly tedious, consumes significant time, and creates an inefficient administrative bottleneck. The Goal: A bulk deletion feature will allow high-volume users to clean up their dashboards in seconds, leading to a much cleaner workspace, better file tracking, and a more professional user experience. Thank you for reviewing this suggestion to help make Sinosend even more efficient!
0
🔗🔁 MCP Server Integration (Lightweight Alternative to API)
A Model Context Protocol (MCP) server for Sinosend would unlock automation, CLI, and AI‑agent workflows without the complexity of a full public API. Today, more and more prospective users and teams work directly from the terminal/CLI and AI tools and they expect their file‑transfer tools to plug into those workflows instead of only the browser. A first‑party MCP server would give users a simple way to use Sinosend with any MCP-aware client while ensuring cross‑border delivery and security. Why this matters and why now Immediate and adjacent competitors like MASV and dlvr . sh already expose MCP servers for their platforms, so it’s becoming a differentiating feature in the file‑transfer space rather than a niche experiment. MCP is specifically designed to let users connect AI agents and CLIs to an existing product in a safe, constrained way, where Sinosend decides which actions and data are exposed (e.g., “create transfer,” “list transfers,” “get share link,” “revoke link”, etc). This significantly increases productivity for power users: they can upload files, generate branded links, and notify clients from their existing scripts and AI workflows, instead of manually repeating the same steps in the Web UI. How it fits Sinosend’s roadmap and focus MCP can be a lighter‑weight bridge that respects constraints related to current infrastructure and maintenance overhead: MCP servers can initially be scoped and opinionated (covering just the most valuable operations like upload, share link creation, and transfer status), rather than a full open API surface. Full control over auth, rate limits, and plan eligibility (e.g. Pro/Business tiers), which keeps infrastructure load predictable. Early adopters will be the same users already asking for automation and API‑style workflows, so Sinosend would directly address an existing, documented demand. Simple usage example: From Claude Desktop or a terminal UI, a user could type: “Upload client_deck.pdf to Sinosend with brand X, generate a link, and draft an email to the client.” The MCP server would handle the upload, apply the correct branding/sales room options, return a secure link, and expose basic metadata (recipient, expiry, etc.) back to the agent.
2
Load More