Skip to content

Settings and activity

3 results found

  1. 10 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Wissem Mareghni shared this idea  · 
  2. 26 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Under Review  ·  2 comments  ·  Core » Text Snip  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Wissem Mareghni supported this idea  · 
  3. 9 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Core team is working on sending this data which we'll then be able to incorporate into both AR & Dashboard. (Regardless of which licensing method the company is on)

    An error occurred while saving the comment
    Wissem Mareghni commented  · 

    It would be beneficial to incorporate the installed version into the advanced report, allowing for a comparison of usage per version for individual clients. Instead of extracting data based on a date range, we could filter by the installed version. This would be particularly useful for large structures where rollouts occur in multiple phases.

    This could also introduce an option in the dashboard to compare usage between two versions for the same client (for instance, comparing Dashboard v5 vs v6). We could then observe, percentage-wise:

    Changes in usage from one version to another: This could potentially highlight update issues. For instance, if a client uses a feature less frequently, it might indicate a hidden pain point introduced by the new version.
    Justifications for rate increases by demonstrating time savings: If the usage of manual snippets decreases from update to update while automation usage increases, it could serve as a strong argument for a rate increase.
    This approach would not only provide valuable insights into how updates affect user behavior but also help in identifying potential issues and opportunities for improvement. It would also offer tangible evidence to support rate increases, thereby enhancing the overall value proposition.

    Wissem Mareghni supported this idea  ·