Product Ideas & Feedback

It would be nice if SourceWhale could record when someone accepts your connection request. Like it records InMails and replies, It records when you send a connection request, why not record when it is accepted. Thanks!

Ensures that all messages are of a certain standard before being sent out - determined by the client

This would ensure that high-priority initial outreach is sent in a timely manner, rather than being delayed due to SourceWhale prioritizing follow-up touchpoints in active campaigns.

When working through LinkedIn connection requests and InMails, it would be helpful to see how many you have left to do without going back into SW. Adding the small yellow notification (as I've shown in the screenshot) to the plugin would be a nice-to-have.

There ar a number of tools that are offering the ability to personalize VM drops with an AI tool that allows you to clone your voice and use the contact name in the VM drop and video recordings in an email - some also offer the ability to include this in a connection request in LinkedIn

We need a way to identify contacts who haven't opened any past emails in order to remove them from future ones. Whilst we can get a list from an individual campaign, there is currently no way of finding a master list of contacts with poor engagement. Our contacts are often spread across campaigns, and so there is no practical way to identify the ones we should be removing. In an ideal world, uploading a spreadsheet would identify contacts with poor engagment, so that these can be removed. Alternatively, a way to blacklisting contacts with poor engagement would be good (similar effect to unsubsribing, but distinguishable and reversable). This is partly to ensure we don't waste outbox space on poor targets, and partly to ensure good email practice and improve our rating with Outlook.

Please allow the ability to change the contact's stage in a campaign when you open the contact popup. If you're calling through the contacts in a campaign, the call outcome will not change the contact's stage, even if you are currently in their active campaign.

Platforms like DRIPify offer deeper insight into your LinkedIn engagement journey — showing stats like: • Connection request sent / accepted • Invite withdrawn • Liked/commented on a post • Followed vs connected In Sourcewhale, there’s currently no visibility on these micro-engagements. This makes it hard to track: • Whether someone is a first, second, or third-degree connection • Whether they’ve been followed but not connected • If a connection request was sent, accepted, or withdrawn • What light-touch engagement (e.g. post like) has already occurred Why this matters: • These steps shape campaign sequencing. For example: • You might follow someone first, then engage with a post, before sending a connection request. • You don’t want to resend a connection request or message if one is already pending. • It helps you avoid duplicate or awkward touches and better personalise follow-ups. Suggested Improvements: • Display connection degree + follow status in the contact pop-up and project list. • Show LinkedIn action history (e.g. followed on June 10, connection request sent June 12). • Add filters or icons to help sort contacts by engagement status. This would bring Sourcewhale closer to what tools like DRIPify provide — but within a project-based, search-led workflow that better suits executive search.

SourceWhale does data refresh of our database (RecruitCRM) and each time it updates it shows on Recruit CRM as updated by and then a random person from our organisation. Because of that we cannot tell who really updated a record. Would it be possible to have "updated by SourceWhale" on our database? RecruitCRM team says it would have to be changed on your end.