We released a behind-the-scenes improvement to calling, which makes your inbound and outbound calls made with the Dialer more stable.
To learn more about how our built-in Dialer works, you can check out the help guide here.
Apple recently released iOS 14.5, which fixes over 50 security issues, many of them critical. They followed this quickly with release 14.5.1, which fixes a web browser security issue that Apple says "may have been actively exploited."
If you have an iPhone or iPad, we recommend updating your iOS to version 14.5.1, as we prioritize security to keep our customers as safe as we can.
More details on this update from Apple are here.
And now for the iPhone app bug fixes:
We released version 2.16.1 of our iPhone app, which is now available in the iOS App Store. You can opt to manually update the app here if you want, or the auto-update will happen in the coming days.
This is mainly a bug-fix release, addressing the following issues:
Bad password: If a user entered the wrong password, they would end up in a state where they needed to kill the app to try again. This was a regression introduced in version 2.15.3, and also occurred in 2.16.0, and is now fixed.
Robust email signatures: Some complex email signatures would not be accurately added to emails, due to data processing issues. That processing is now stripped-out before sending, and the accurate signature will now be properly inserted.
Add first Relationship: If a lead had no Relationships, you couldn't add one in version 2.16.0, but now you can.
Appointment invitees for Relationships: If any email for a person was already invited to an appointment, other emails including those for Relationships could not be added.
We've introduced a change to make it easier for you to introduce agents and/or referral action plan emails.
Previously, when sending emails via Action Plans we would always use the Sender's profile information instead of the assigned agent. This made it difficult for teams wishing to send emails for agent introduction or lender referrals. With this new change, Action Plan emails will always use the assigned agent information just like when sending 1<>1 template emails.
Additionally, we introduced a new merge field for %sender_ to make it as clear as possible for you to specify what information to use when sending an email template.
1) Action plan will always use Assigned agent information
2) Action plan will use the Sender's profile information for introduction emails
There are more details within the help document below and If you have any questions, please email us at email@example.com
We've released a fix to improve the reliability of our Google Calendar sync, as part of this release customer accounts will be re-syncing over the next few days.
If you continue to see any issues with your Calendar sync after this week please let us know at firstname.lastname@example.org and we'll investigate/fix right away.
Our engineering team has fixed an issue where tags would be deleted from the Tags page, but then mysteriously reappear at a later date. Now, when you delete a tag from the Tags page, it will be permanently deleted as expected.
Our Engineering team resolved an issue where mirrored calendar events would show up when multiple team members were scheduling a new event on the calendar at the same time causing Agent A’s calendar and Agent B calendar to mirror the same event until the page was refreshed. We certainly apologize for any confusion this issue caused you and your team.
Thanks for subscribing!
Check your inbox to verify your email