Overview

The Telstra WME bounty management module provides a way to automatically provision a request to claim a bounty to telstra for new and recontracted services.  It additionally allows you to manage the status of these bounty claims, whether they are later approved, rejected or clawed back.

What's in this section?


Licensing

This feature is available to subscribers of the following:  Tick the option(s) that apply. If this is available to all users, meaning "Emersion Core", other options should not be ticked. 

  • Emersion Core
  • Optional Modules (Bounty Management)
  • Upon Request (please contact your Account Manager)




Features and How To's




Prerequisites

Before attempting to use this module, users should ensure:

  • be confident in using our bulk tools.
  • they are able to configure packages and plans.

Dependencies 

Some modules and features have dependencies. For example, Commissions is dependent on having the Agents module. Processing an payment via credit card is dependent on having a subscription to the Emersion Payments module AND having a payment gateway configured and enabled. These are the things that need to be captured here.  If there are no dependencies, remove the example and leave the last line about having no dependencies. 

In order to use this module, service providers must have:

  • The Telstra WME service type is enabled for your Retail Service Provider Account


Access Control

Module permissions and powers are used to control access to modules, Powers are used to control access to features of a module, functions, and page sections.

If you are unable to access a given feature and you have checked the permissions and powers, please contact Emersion.


Module Permissions

List the module permission(s) needed to enable the module. Once that's complete, delete the sentence immediately below the table. If there are no module permissions, delete the table and leave the sentence. 

Module PermissionDescription
Finance AllGrants users access to relevant functions within the finance module, including WME Bounties.


Powers

List the module permission(s) needed to enable the base module. Powers related to its features, particularly the optional features, should not be included here as they are documented on their own feature pages. Once that's complete, delete the sentence immediately below the table. If there are no module permissions, delete the table and leave the sentence.

PowerDescription
Bounty Requests ViewGrants you the ability to view details of a bounty Request.
Bounty Request EditGrants you the ability to edit a bounty request.
Bounty Request Dispute ManagementGrants you the ability to dispute bounties, and reject and approve these disputes.


Module Events

Some modules and features include specific events. If a module includes specific events, list the event type names and IDs here. If the module includes nothing specific, remove the example, leaving the last line in tact.

The following events are included in the module.

Module Reports

Some modules and features include specific reports. If a module includes specific reports, list the report names and IDs here. If the module includes nothing specific, remove the example, leaving the last line in tact.

The following reports are included in the module.

  • Bounty Request Report (id: 1203)
  • Bounty Request Audit Log (id: 1204)



Related Articles

Click the macro and choose edit.  Add additional labels and save.  To ensure consistency with all other EKB pages, DO NOT change any other settings in the macro. Simply add more labels and save. This will populate a list of related articles based on the labels (tags) it is given.