Promotions

Types, configuration inputs, and governance rules for BAU promotions.

Promotions are used to drive acquisition, reward loyalty, and support bundle pricing.

This section covers what the platform supports in BAU, plus the rules you must follow when launching and operating promos.

circle-exclamation

What you can do (BAU)

  • Create coupon-code and systematic promotions.

  • Limit promotions by plan, customer type, user type, and number choice.

  • Control stacking and priority when stacking is allowed.

  • Support bundle-triggered discounts via API (HSI only).

Promotion types

Type
How it works
Operational behavior

Coupon code

Customer or agent enters a promo code at checkout.

Once applied to an account, it cannot be removed. Validate configuration before publishing the code.

Systematic

Discount auto-applies when eligibility rules match.

Removed only when eligibility is no longer met. Manual removal is not supported.

API — HSI only

Discount triggers when the customer meets brand-defined HSI eligibility.

Requires an active Product Bundle API integration. Treated as the base promo with the highest priority (P0).

Standard configuration inputs

The platform expects the fields below for every promo.

Field
Required
Allowed values
Notes

Promo Name

Mandatory

Free text, max 15 chars

Customer-facing label used across Web/App/RC and billing views.

Promo Code

Mandatory

Free text, max 15 chars

Coupon: must be unique. Systematic: can match Promo Name. Shows in reporting.

Promo Reason Code

Mandatory

Free text, max 15 chars

Used for reporting and reconciliation.

Application Duration

Mandatory

Purchase / Activation

Purchase applies at checkout. Activation applies when the line activates.

Promo Start Date

Mandatory

MM-DD-YYYY

First day the promo can apply.

Promo End Date

Optional

MM-DD-YYYY

Leave blank for open-ended promos.

Promo Type

Mandatory

Systematic / Coupon / API (HSI only)

Defines how the promo is triggered.

User Type

Mandatory

New User / Existing (Add line) / Both

Promo applies to new purchases only (even for add-a-line).

Customer Type

Mandatory

Residential / Business / Employee / combinations

Allowed combinations: Res+Bus, Res+Emp, Bus+Emp, Res+Bus+Emp.

Plans

Mandatory

All / specific plan names

Use exact plan names when scoping.

Number Preference

Mandatory

New Number / Port-In / Both

Controls eligibility by number choice.

Frequency

Mandatory

# bill/renewal cycles or Recurring-infinite

Examples: One-time, Recurring (6 cycles), Recurring-infinite.

Value

Mandatory

$ amount or % (≤ 100%)

Example: $10 off, 100% off.

Line Criteria

Mandatory

Primary / Secondary / Both / specific lines

Controls which lines the promo targets on a multi-line account.

Usage Limit

Mandatory

Numeric value or # lines on account

Max number of applications.

Account / Plan Level

Conditional

Account / Plan

Required for multi-line discounting logic.

Promo Stacking Allowed

Mandatory

Allowed / Not Allowed

Whether other promos can coexist.

Promo Stacking Priority

Conditional

Priority order + promo list

Required only when stacking is allowed.

Promo Description

Mandatory

Free text, max 20–25 chars

Short customer-facing description on the plan card.

Invoice Display Name

Optional

Free text, max 15 chars

If blank, invoice uses Promo Name.

Stacking and priority

When stacking is enabled, promos are applied in a fixed priority order.

  • P0 — HSI bundle discount (API; always highest priority)

  • P1 — 1st line free / employee discount

  • P2 — BOGO

  • P3 — coupon codes and other stackable promos

Governance rules (non-negotiables)

Rule
Policy

When promos can be applied

Only during a new purchase flow. You cannot add a promo to an already-active plan after purchase.

Coupon removal

Not supported once applied to an account.

Systematic removal

Happens only when the account no longer matches eligibility. Manual removal is not supported.

Effective date of removal

Any removal takes effect starting the next billing cycle. No retroactive adjustments.

Non-BAU configurations

Anything outside these rules is treated as custom work.

BAU use cases (templates)

Use the examples below as copy/paste templates when completing the Promo BAU Configuration Sheet.

Use case 1 — 1st line discount via coupon

Field
Value

Promo Name

First line discount

Promo Code

FIRST10OFF

Promo Type

Coupon

Application Duration

Purchase

User Type

New User

Customer Type

Residential

Plans

All Plans

Value

$10 off

Frequency

Recurring – 6 months

Line Criteria

Primary

Usage Limit

1 (Account level)

Promo Stacking

Allowed — P1

Number Preference

New Number

Invoice Display Name

First line discount

Use case 2 — BOGO (buy one, get one)

Field
Value

Promo Name

BOGO Feb 2026

Promo Code

BOGO Feb 2026

Promo Type

Systematic

Application Duration

Activation

User Type

Existing (Add line)

Customer Type

Residential + Employee

Plans

All Plans

Value

100% off

Frequency

Recurring – 3 months

Line Criteria

Every 2nd line (2, 4, …)

Usage Limit

2 (Plan level)

Promo Stacking

Not Allowed

Number Preference

Both

Invoice Display Name

1 Unlimited Line Free

Use case 3 — 1st line free (systematic)

Field
Value

Promo Name

1st Line free

Promo Code

1st Line free

Promo Type

Systematic

Application Duration

Activation

User Type

New User

Customer Type

All

Plans

Unlimited Plans Only

Value

100% off

Frequency

Recurring – 12 months

Line Criteria

Primary

Usage Limit

1 (Plan level)

Promo Stacking

Allowed — P2

Number Preference

Both

Invoice Display Name

1st Line free

Use case 4 — employee discount

Field
Value

Promo Name

Employee discount

Promo Code

Employee discount

Promo Type

Systematic

Application Duration

Purchase

User Type

Both

Customer Type

Employee

Plans

All Plans

Value

100% off Line 1 / $X off other lines

Frequency

Recurring – Infinite

Line Criteria

Both

Usage Limit

# lines on account (Account level)

Promo Stacking

Not Allowed

Number Preference

Both

Invoice Display Name

Employee discount

circle-info

Questions or clarification? Reach out to your respective account manager or email at [email protected]

Last updated