Hey, Leadfwd world!

We are happy to announce to you our new Ringless Voicemail add-on functionality is now live! 

Ringless voicemail (RVM) is a telephony framework that can send pre-recorded voicemails, directly to voicemail inboxes—instead of dialing, ringing and waiting. You pre-record the messages and the Leadfwd platform drops those voicemails into each individual contacts voicemail box, using Sequences and Automation.

• Welcome new users who have signed up for your services.
• Remind existing customers of upcoming renewals.
• Alert customers to service upgrades or new offerings.
• Webinar or conference attendee reminders.
• Connect with your best customers with a holiday greeting.
• Reward your top clients with special offers and promotions.

RVM for Outbound Sales and Building Pipeline

• Most people don’t answer unknown numbers, but they do check voicemails.
• Stop interrupting. Prospects can listen to your message anytime.
• Shield your sales reps from rejection and repetition burnout.
• Allow sales reps to focus on talking to people that want to buy.
• Deliver a personal touch, but in a scalable way. 
• Personalize the Caller ID with your direct line for easy call backs.
• Import unlimited voicemail assets.

Learn more about RVM for Leadfwd

Hello everyone!

We are excited to announce that our 'no-code' Zapier Connector is now available. This means that you can now connect Leadfwd to over 5,000 other apps for increased productivity and efficiency.

Some of the apps that you can now connect to Leadfwd include:

• Hubspot
• Zoho
• Pipedrive
• Google Sheets
• Slack

This is a huge step forward for us and we are really excited to offer this to our customers. If you have any questions or need any help getting started, please feel free to reach out to our support team.

To get started, check out this article.

Extended the manual mailbox setting to control delays between each email sent, to include an AI algorithm to randomize the delay between every email sent. This approach helps the automation better mimic human sender activity, which in turn helps reduce some scrutiny from spam filters. 

• improvements AI Powered Delay Between Emails / Learn more

Hey! 

🎉 Leadfwd is excited to roll out new SMS features for sales and marketing teams! 

Leadfwd has extended our SMS offering with reply detection, so you can now see which leads are engaging with your SMS messages and automatically end Sequences when a prospect replies via SMS.

In addition you can now select a specific outbound phone number to use for SMS action steps on multichannel Sequences. Before the SMS number assignment was based on the single number that was assigned to each individual Leadfwd user.

🚀 Stay tuned for more to come on SMS!

Hey there,

We have some awesome news! We've made a simple, yet big improvement to testing emails in Sequences...

Ever wanted to quickly send a test preview of every email in your Sequence? Now you can! Whether it's for copy approval or testing the messaging flow, we got you covered!

You can select a specific Email Step to preview or ALL of your Email Steps. Each Email Step will be sent individually as it would be in your live Sequence. 

Simply enter the delivery email address and click 'Send now'.

Until next time!

Hey again! 

We've been super busy over the last few weeks, and we're excited to share a pretty cool update! 🎉

We've released a new Action Step ⚡️ that will allow you to seamlessly transfer prospects and leads to an entirely new Sequence or End any active sequence instantly.

We've already heard of some pretty unique ideas from our amazing customers. But our initial inspiration for this feature was to simply enable a seamless transfer at the end of a Sequence, if a prospect hasn't replied or engaged. 

This would help ensure no prospect ever slips through the cracks, even when they reach the end of a Sequence.

🚀 Stay tuned for more big news coming soon! 

Small tweaks for the week related to Prospect and B2B data searches!

• fix Prospect Search / Database update to increase performance for results on larger datasets. 

We have also fixed some defective functions as part of this hotfix release:

• fix Landing Pages: Fix defective redirect to download page when client had a CNAME was present but not registered with the Leadfwd app. 
• fix Forms: Update to form processing and identification to ignore existing cookie assignment when the 'email' input on a form has a different email address. This will ensure a new record is created instead of inaccurately attributing a form submission to a contact ID based on a cookie being present.

We have fixed some defective functions in the app within this hotfix release;

• fix Sequences: open tracking would infer opens of email steps even when the open tracking was disabled, simply based on clicking on links like unsubscribe. This would create confusing stats, since no actual open tracking was enabled. With this fix, we will no longer track or infer opens simply by visiting a static-app pages like unsubscribe. 

Hello Leadfwd Community!

We’re pleased to announce that the following features and enhancements are now available for our list import functionality for CSV files.

• new Segments are now auto-created for every unique CSV file that's imported for new lists or existing lists (updating). This makes maintaining a single master list much easier, but easily targeting individual list updates (as segments).
• improvements Changelog for lists now includes the duplicate count that were discovered during your list import or update.
• improvements Platform log now includes CSV import processes and their outcomes. Replicating the legacy email alert with your input processing report details, inside the Platform log.
• improvements Lead Source attributed to CSV files where a contact originated. Updated views include the Lead Source Analytics view, Timeline view and List view.

We have also fixed some identified bugs:

• fix Fixed and separated the List Changelog queries for Missing, Invalid and Duplicates by creating separate columns.
• fix Fixed incorrect assignment of the account owner for every list update or import. It's now accurately represented by the logged in user that executed the list update/import.