Page cover

1.89.6 (15.08.2023)

A deployment of a new version of SodaStream and Client Portal inside the regular release window.

Improvements

PF - Report phone issue

Where found: Client Portal > Prospects > All prospects > Side menu

We are adding the option for the users to be able to report an issue with the phone numbers associated with a prospect.

When the side modal or prospects details page is opened, we have added a 'Report phone issue' next to the phone number. This will allow our clients to provide their feedback for the sourced numbers and for us to be able to analyze the patterns and optimize the phone finding process and accuracy of the data.

The user will be able to select between three options:

  • Phone number doesn't exist

  • Incorrect caller

  • Other

When a user reports an issue for a specific number, next time the button will be changed to 'You reported an issue' so that all redundant steps are excluded.

PF - Add SDR notification

Where found: Client Portal > Prospects > All prospects

We want to encourage our clients to add in SDR logs when they use a phone number i.e. call a prospects. This will allow us to have a visibility of the success of the campaign, but also exclude the prospects from the email outreach activity.

For these reasons, when a user copies a phone number an in-app notification will appear advising the user to add an SDR log.

Campaigns with more than 4 stages in email templates tab on portal

Where found: Client portal > Email templates

As the teams started to test different approaches that contain multiple emails per chain, a change of logic was implemented in terms of how we're presenting the email templates in the Portal.

So far the Portal supported visibility of the regular 4 stages, and this is now upgraded and on the Portal we'll have visible all stages that are defined as part of a campaign an set as 'In use' in SodaStream.

Postal - Remove domain check for psrp.domain responder accounts

Where found: SodaStream > Ops&Delivery > Responder Account

We are introducing post MVP improvement for Postal that will allow the users to create a responder account for the accounts set on Postal.

So far, we were creating these accounts directly from DB, and moving forward the teams can do the same via SodaStream.

Delay between sends default values

Where found: SodaStream > Campaigns & Setup > Campaign send schedules

As part of the deliverability process it is advised that every send schedule should have delay between the sends. So far these fields were 0, and we added default values so that we save some time and ensure that all send schedules will have the advised delay.

Email notification on LinkedIn credentials inserted

Where found: Client Portal > Onboarding

This improvement will provide better visibility to the Ops team during the onboarding phase of a campaign. When a client adds their LinkedIn credentials a system notification will be triggered to advise the ops owner that the client has added their LinkedIn credentials to the Portal.

Referral page- Add LinkedIn Profile field

Where found: Client Portal > Reward Scheme

For the clients that want to refer us to another business but doesn’t have an email address, we added an option to do that by providing a LinkedIn profile.

When LinkedIn profile is added to the Reward scheme page, the sales team will be advised and they can proceed with the defined process for these scenarios.

Bug fixes

Where found: SodaStream> Email templates

When a user wanted to test an email template, and that email template had a variable for a GB template with a number in the name, the preview link didn't work i.e. when the giftlink was accessed via inbox the landing page didn't load.

The issue was identified and fixed, moving forward the test of email templates will have functioning giftlinks.

E-mail address creation date is not written for addresses in a cloned e-mail profile

Where found: SodaStream > Campaigns & Setup > Campaign email profiles

It was detected that whenever an email profile is cloned the CreationDate field in the DB wasn't populated, and this disabled the teams to create WarmUp schedule 2.0.

The issue was identified and fixed, moving forward the teams can WarmUp schedule 2.0 with cloned email profiles.

Last updated