Improving User Feedback in the PPS-GrupoB CMS

The Challenge

Communication is the backbone of any content management system. In the PPS-GrupoB project, we identified that the feedback loop for contact submissions within the CMS was inconsistent. Users were not receiving accurate confirmation that their messages had been successfully processed, leading to unnecessary support tickets and confusion.

The Approach

To resolve this, we audited the message handling lifecycle within our React-based CMS dashboard. The issue stemmed from an outdated UI response state that failed to acknowledge the server's acknowledgment properly.

Refining the Feedback State

We implemented a more robust handling pattern to ensure that the UI reflects the actual status of the asynchronous communication. By decoupling the submission intent from the response handler, we ensured that users receive immediate, clear feedback:

const handleSendMessage = async (payload) => {
  try {
    setLoading(true);
    const response = await api.post('/contact', payload);
    if (response.ok) {
      setNotification('Message sent successfully!');
    }
  } catch (err) {
    setNotification('Failed to send message.');
  } finally {
    setLoading(false);
  }
};

This snippet demonstrates the pattern: setting a clear loading state, awaiting the API resolution, and providing contextual feedback based on the result. This prevents the user from wondering if their input was ignored.

Results

By normalizing how these messages are handled, we have seen a significant reduction in duplicate submissions. The CMS now offers a predictable and reliable interface for administrative communication.

Key Insight

Simple UI feedback is often overlooked in favor of complex features. Ensuring that the user knows exactly when an action has succeeded or failed is essential to maintaining trust in any administrative interface.

Generated with Gitvlg.com