WovenIQ — Release R1.68

Highlights

• Configurable customer journeys: Define journeys per store, schedule post-visit email and SMS touchpoints by days after visit, and track enrollments and send history on each Contact.
• Smarter check-in: Store associates confirm or change the customer’s journey at check-in when a store offers more than one active journey.
• Notification cleanup: Messaging Centre filters, per-associate queue notification preferences, configurable message routing to store teams, and user-level control of follow-up task reminders.
• Rolex catalog refresh: Optional daily job to refresh Rolex product metadata and MSRP from the vendor feed.
• Allocation workflow: Approvers receive an in-app notification when an allocation offer is rejected.
• Customize email content: Store associates can preview and save per-journey email copy (and preview SMS content) from the customer profile before automated sends run.

What’s new for everyone

• Journey-driven follow-up: Post-visit emails and text messages follow rules you configure per journey (for example day 1 welcome, day 21 follow-up) instead of fixed legacy schedules.
• Guest survey journeys: Customers can select a journey during check-in survey when a store has multiple active options; the choice carries through to the queue and enrollment.
• Check-in confirmation: On Store Queue and My Queue, tapping check-in prompts the associate to confirm the correct journey when more than one is active for that store.
• Messaging Centre: Filter conversations by My Customers or All Customers for quicker triage.
• Queue notifications: Store associates can turn customer-in-queue bell notifications on or off per store from the new Notification Preferences tab.
• Allocation updates: When an allocation offer is rejected, the approver sees a bell notification with context on the related product interest.
• Richer journey email preview: Customize Email Content on the customer profile lists upcoming journey emails and SMS steps, with merge-field preview using a sample customer queue record.

What’s new for administrators and data stewards

Customer journeys (new model)

• Journey — Master definition (name, display name, description, image URL) for a repeatable post-visit communication path.
• Journey Store — Links a Journey to a Store with Is Active and Sort Order; every production store needs at least one active link before check-in and survey tiles work.
• Journey Notification — Child rules on a journey: Days After Visit, Channel (Email or SMS), Email Template Developer Name (Branding package), optional Messaging Template for SMS, and Is Active.
• Customer Journey — Enrollment tying a Contact to a Journey with Last Visit Date, Last Store Visited, and Last Customer Queue (all required). Unique Id is calculated automatically from contact + journey.
• Journey Notification Log — Audit of each send attempt (status, channel, visit date, error message).
• Journey Email Customization — Optional per-enrollment override of email body text for a specific journey notification; cleared after a successful send.
• Messaging Template — Reusable SMS bodies with merge tokens; custom fields in templates must use fully qualified API names (for example woveniq__First_Name__c).

Customer Queue → Journey is required at check-in conversion. Queues created at a single-journey store can receive a journey automatically; multi-journey stores rely on survey selection and/or associate confirmation at check-in.

Preferred Communication Method on Contact and Customer Queue now uses SMS, Email, and Both (default Both). Migrate legacy Phone / Text values before enabling journey SMS in production.

Scheduling and cutover (upgrading from 1.67)

• Schedule the new daily journey notification job (onboarding default 11:00 AM). Remove legacy schedules for fixed follow-up and preference-update email jobs to avoid duplicate customer emails.
• Run the journey enrollment backfill once with your default Journey Id to create Customer Journey rows for existing contacts with visit history.
• Complete onboarding Store, Journey & Associate Configuration before testing the guest survey or journey sends.
• Redeploy the Experience Cloud site-app (manual, not in the base package) so guest survey journey tiles and APIs stay current.

After upgrading, deploy any dependent extension packages (Branding and Reports) once builds compiled against 1.68 are available.

Notification and messaging settings

• Email Notification Setting → Message Notification To SA — When unchecked (default), new message bells go to the store public group; when checked, only primary and secondary store associates for that store are notified.
• Store Associate → Receive Queue Notification — Opt out of customer-in-queue bell notifications (default on).
• User → Notify For Follow Up Tasks — Opt in to reminders for open store-visit follow-up tasks (default off).

Product catalog (Rolex)

Schedule the daily Rolex product metadata refresh job (onboarding default 1:00 AM) when your org syncs Rolex MSRP and catalog metadata from the vendor API.

Deprecated items (safe to hide on layouts)

• Customer Queue Setting → Follow Up Days After
• Contact → Update Preference Email Sent At
• Contact → Send Customer Visit Summary

Legacy follow-up and preference email automation is replaced by Journey Notification rules; converted-status check-in emails are no longer sent from the customer queue email job.

Data stewardship

• Validate journey configuration and a small backfill sample in sandbox before production cutover.
• Confirm Branding extension is upgraded with base 1.68 so journey email templates resolve queue merge context correctly.
• Re-assign WIQ Admin and WIQ User permission sets after upgrade so new journey tabs and object access apply.

Support utilities (repository scripts, not in base package)

• Journey enrollment backfill — One-time enrollment creation for existing contacts (packaged as a global batch callable from anonymous Apex).
• Adaptive sales history backfill — Org-specific utility for Zadok to refresh purchase summary fields from Adaptive when external customer identifiers are already present; run only when directed by WovenIQ support.

Support

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