Skip to main content
Abid Md
Contributor ⭐️
March 5, 2026
New Idea

Exact drafts count

Related products:CS Timeline & Activity Tracking
  • March 5, 2026
  • 1 reply
  • 18 views

Hi Team,

Our users are in the early stages of adoption. One feature that has been particularly well-received is the ability to log interactions to the timeline, making it much easier to track account activity compared to managing interactions via email.

To fully leverage this feature, users are logging a significant number of emails to the timeline. However, due to our current data structure, multiple emails are being logged as drafts. As instructed, users are navigating to the drafts section, making necessary edits, and then logging these drafts to the timeline. While this process works, there is some confusion regarding the draft count display.

Currently, the draft count always shows as "99+," regardless of the actual number of drafts. For example, if there are 110 drafts, the draft page only displays a count of 100, as it loads 100 records at a time. When a draft is moved to the timeline and the page is refreshed, the count still shows 100, reflecting only the latest 100 drafts. This makes it difficult for users to determine whether a record has been successfully logged to the timeline.

Request:
Could we update the system to display the total number of drafts, rather than just "99+," to provide users with greater clarity and confidence in the process?

    1 reply

    pranaykundarapu
    Gainsight Employee ⭐️
    pranaykundarapu
    Gainsight Employee ⭐️
    March 5, 2026

     

    Thanks for raising this—our team fully supports this request, and we're aligned on the importance of improving visibility for users. We're hearing similar feedback from our side as well, especially as adoption increases and more emails are being logged to the timeline.

    While our teams have implemented internal guidance to help users navigate drafts effectively, having the system display the actual total number of drafts (instead of "99+") would provide far greater clarity and significantly reduce confusion around whether records have been successfully logged.

    Terms & ConditionsAccessibility statement