Patrick Vu (WICLOUD CORPORATION) CE

Please continue addressing the known issue 4449491. This is a trending issue that affects many customers.

When the estimated members in the draft segment did not match the member count immediately after the segment was set live—considering it was still in the draft state—I would like to suggest implementing indexing to improve segmentation member update performance.

When modifying member record fields in a draft segment, the estimated members view updates immediately. However, after setting the segment live, the member count does not update right away. While delays may be expected when modifying a live segment, it is not reasonable for this behavior to occur in a draft segment. To resolve this, I recommend implementing indexing to improve segmentation member update performance.

Based on the document Exclude bot interactions - Dynamics 365 Customer Insights from Microsoft, inflated open rates are a known occurrence due to the fact that bot protection does not apply to email opens. As a result, nonhuman traffic can artificially increase open rates, leading to misleading analytics.

I would like assistance in identifying a solution to prevent this issue from occurring in the future

Currently, when using the SMS system that retrieves phone numbers from ACS, incoming messages trigger a notification. However, users must manually click on the notification to view the message, creating unnecessary delays in communication.

To optimize efficiency and streamline workflows, we propose implementing real-time message visibility—allowing messages to be displayed instantly without requiring user interaction. This enhancement would eliminate the need to repeatedly click on notifications, ensuring smoother, uninterrupted communication, especially in fast-paced environments where real-time responsiveness is crucial.

By introducing this functionality, users can engage with incoming messages more seamlessly, improving productivity and overall user satisfaction. We believe this feature would be a valuable addition to the system and greatly enhance its usability.

This setting allows organizations to enable or disable Copilot access for specific users or security roles within Customer Journey Insights.

• Controlled Rollout: Admins may want to test and evaluate Copilot internally before making it available to the broader team. This ensures the feature aligns with organizational goals and expectations.
• Training & Adoption: By limiting access initially, admins can train selected users, gather feedback, and refine usage strategies—leading to smoother and more effective adoption.
• User Preference: Not all users may wish to use Copilot. Some prefer manual analysis or may have concerns about AI-generated insights. Providing opt-in or role-based access respects individual workflows

This feature would provide more flexibility and control, helping organizations adopt Copilot in a way that aligns with their internal processes and readiness.

Currently, for example, I have a warehouse with a single product that has approximately 5 units in stock. When I create a work order and add that product, the system behaves as expected: if I update the estimated quantity to exceed the available inventory and set the item to "Used," a warning pops up indicating that the quantity is insufficient and asks whether I’d like to proceed.

However, I’ve observed that when editing two work order items simultaneously, the system allows me to save without displaying any warning—even when the combined quantity exceeds the available inventory.

I believe a warning should still appear in this scenario to prevent unintentional overconsumption of inventory. Without it, users may unknowingly allocate more units than are available, which could lead to inaccurate stock levels, fulfillment issues, and downstream integration errors—especially in systems like Business Central where inventory accuracy is critical.

Currently, when using a form published with the "Form capture" option, the system tracks only the number of submissions. It does not record visit metrics, which consistently display as zero in the Analytics tab. This creates a confusing user experience, as the visit metric is visible but non-functional—leading users to question whether their setup is incomplete or incorrect.

Incorporating visit metrics into form capture functionality is critical for optimizing user engagement, improving conversion rates, and enabling data-driven decision-making.

• By understanding the ratio of visits to submissions helps identify friction points in the form experience, allowing teams to make targeted improvements that enhance completion rates.
• Visit metrics provide valuable insights into form performance across campaigns, channels, and audience segments, supporting more accurate ROI analysis and strategic adjustments.

Currently, when using a form published with the "Form capture" option, the system tracks only the number of submissions. It does not record visit metrics, which consistently display as zero in the Analytics tab. This creates a confusing user experience, as the visit metric is visible but non-functional—leading users to question whether their setup is incomplete or incorrect.

Incorporating visit metrics into form capture functionality is critical for optimizing user engagement, improving conversion rates, and enabling data-driven decision-making.

• By understanding the ratio of visits to submissions helps identify friction points in the form experience, allowing teams to make targeted improvements that enhance completion rates.
• Visit metrics provide valuable insights into form performance across campaigns, channels, and audience segments, supporting more accurate ROI analysis and strategic adjustments.

Currently, when using the Convert to Lead dialog, certain fields such as Last Name are marked as required. Even after changing the Lead entity field requirement from Business Required to Optional, the dialog continues to enforce the requirement.

This behavior is confusing and limits flexibility, as organizations may have different data collection needs and may not always require the Last Name field during lead conversion.