WovenIQ — Release R1.83

Highlights

• SMS matches the other profile actions: With message integration on and Customer Messaging Style set to Button, the SMS button is the same size as Call, Mail, and the rest of the row. The unread badge still sits on that button.
• Closing a conversation marks it read: Clicking the envelope to close a Podium conversation also marks every unread Salesforce message read and clears Unread Message Count. Opening the conversation leaves unread messages unread.
• The badge is current when you return: Back from Messaging Centre to the customer reloads Unread Message Count, so the SMS bubble shows the count that was just saved.

What’s new for everyone

• Customer profile — SMS button: When Enable Message Integration is on and Customer Messaging Style is Button, SMS lines up with the other gold action buttons. Previously that button could look a little shorter.
• Messaging Centre — close: The closed envelope still closes the Podium conversation. It now also marks the thread read in Salesforce. The unread separator in the thread, the inbox badge, and the profile SMS bubble all clear. The open envelope still only reopens the conversation; it does not mark messages unread.
• Back to the customer: From a thread opened off the customer (Contact), Back waits until an in-progress read, unread, or close has saved, then returns to the profile and reloads the unread count. The SMS bubble shows that count instead of the number from before you opened Messaging Centre.
• Same day-to-day clienteling otherwise: Profile fields, queues, journeys, attachments, and the activity timeline behave as in Release 1.82 except where noted above.

What’s new for administrators and data stewards

Messaging — close marks the thread read

Messaging Conversation Action is unchanged. It still decides whether opening a thread or marking unread updates the Podium conversation.

Closing from the envelope is separate: the associate asked to close, so Salesforce marks the thread read even when Messaging Conversation Action is No or Open Only. That close does not send a second Podium update. Opening from the envelope does not move the unread watermark.

Last Message Sent At advances to the close time when there were unread messages. Unread Message Count becomes the number of received messages on or after that time, which is 0 for messages already in the thread.

Customer profile — unread badge after Messaging Centre

On the phone, opening SMS from the customer goes to Messaging Centre. Returning with Back forces a fresh read of Unread Message Count on Contact, including after the thread was marked read, marked unread, or closed. The profile no longer keeps a stale bubble from before that visit.

Custom objects and fields referenced

No new custom objects or fields are introduced.

Existing fields used by this release

• Contact → Unread Message Count
• Contact → Last Message Sent At (unread watermark; advances when a close marks the thread read)
• Customer Profile Setting → Enable Message Integration
• Customer Profile Setting → Customer Messaging Style
• Customer Profile Setting → Messaging Conversation Action

Upgrading from 1.82 to 1.83

• Standard managed-package upgrade; no data migration or scheduler changes.
• Re-assign WIQ User and WIQ Admin after install.
• No new middleware release is required beyond the 1.82 middleware that already supports the conversation icon.
• In sandbox, with Customer Messaging Style set to Button, confirm the SMS button matches the other profile actions.
• Open a thread that has unread messages, close it with the envelope, and confirm Unread Message Count is 0. Open a closed conversation and confirm unread messages stay unread.
• From the customer, open Messaging Centre, then tap Back and confirm the SMS bubble matches the saved count.

Upgrading from earlier releases

Orgs not yet on 1.82 should install 1.83 (cumulative) and also follow Release 1.82, then earlier notes as needed.

Branding and Reports extensions

WovenIQ - Branding and WovenIQ - Reports builds pinned to 1.80 remain compatible; no extension change is required for this release unless your team publishes a new build against 1.83.

Support

If you have questions about this release or need help with configuration, contact your WovenIQ administrator or your WovenIQ support channel.