Product Updates & Releases
On websites that randomize form field names as spam protection (like Real Estate Webmasters sites), the pixel either missed submissions entirely or created contacts with just an email address. It now reads the field's id, type, placeholder, and label to capture the full contact — first name, last name, email, and phone.
Read more →A PDF or other file attached to an email a contact sent you was silently dropped during sync — only embedded images were kept. Regular attachments on newly synced emails are now stored and show up on the email.
Read more →On Android the phone would never sleep or lock while the Sure Send app was open. It now behaves normally, staying awake only during a call.
Read more →Automation and lead-flow conditions using "Was Less Than" or "Was More Than" on a date field now evaluate correctly, instead of silently stopping the automation.
Read more →Number, date, and multi-select conditions in Lead Flow and Automation now compare by actual value instead of as text, fixing rules that misrouted leads.
Read more →The "Note Preview" section of an @mention email was showing the note's underlying HTML code rather than what the note actually says. It now shows the readable text, with mentions appearing as the person's name.
Read more →Events now include a normalized canonicalEventType field and a matching filter, so integrations no longer have to guess between "Viewed Property", "page_view", and "property_save" formats.
Read more →On a lead sitting in a pond and not yet claimed, agents with pond access could only see the calls, texts and emails they had logged themselves. They now see all of it, so nobody re-calls a lead a colleague already worked.
Read more →A soft border or tinted background written with a shortened opacity value — like rgba(0,0,0,.15) — was being dropped from your emails before they sent, so recipients saw no border at all. Those colours now survive to the inbox.
Read more →A date custom field now rejects a value it cannot read instead of silently storing it, so a bad entry can no longer break contact search.
Read more →
