Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Overview

This guide will help you know where and how to request new features to the CTG team. Proposed features will be evaluated by the team and with the brands. New feature prioritization will be based on cross-platform ROI and the feature’s effect on any critical marketing campaigns.

Where to Request Features

Please submit them through service desk here:https://rbictg.atlassian.net/servicedesk/customer/portal/2. All requests sent through the service desk portal are managed in a centralized ticket queue.

How to Request Features

  1. Navigate to the link in the where section

  2. Select ‘Feature Requests/Changes’

3. Complete the form inputs

Brand

Select the brand. If the feature is specific to one region, select the brand + region.

Feature Name

Proposed name for the feature.

Feature Category

Select the primary category that the feature is intended to improve. This category should correspond with the development team who would build the feature.

  • Conversion

  • Data

  • Reliability

  • Support

Tied to National Marketing Campaign

If yes, please provide a description, timeline, and expected impact of the marketing campaign in the feature details comments.

ROI/Customer Value

Define the expected improvement (ie funnel conversion, frequency, app stability, UI/UX, user satisfaction) and the evaluation metric for the feature ( ie dollar sales, number of purchases, number of new users, app ratings). If the expected improvement is quantifiable, please list all base value assumptions. If the feature is expected to improve an existing funnel, please provide a link to that funnel.

Feature Description

Describe the issue that you’re trying to solve with as much detail as possible. Focus on the problem, not the solution.

Our product and engineering teams are better suited to provide specific solutions give they have wider knowledge of our platform.

  • No labels