Number, Service and Feature Status Lists
This page is a reference for the status and type lists behind numbers, services and features. Status lists control lifecycle state and billing; type lists set categories, validation and defaults.
Number Statuses
Section titled “Number Statuses”A number status tracks the lifecycle state of a phone number, such as active, suspended or ceased. The status controls what the number can do and how it is billed. A suspended number might still incur line rental but block outgoing calls, while a ceased number stops all charges.
Number Status Name
Section titled “Number Status Name”This section defines the name and display properties of the number status, including how it appears in lists and reports.
| Field | Description |
|---|---|
| Number Status | The name of the number status as displayed throughout the system |
| Number Status (Short) | Abbreviated version of the number status name for compact displays |
| Number Status Availability | Availability of this number status (Headline, Standard, or Historical) |
| Number Status Display Class | CSS class name used for styling this number status in the interface |
| Number Status Display Position | Sort order for displaying this number status in lists and dropdowns |
Status
Section titled “Status”Configure the basic status properties determining whether numbers with this status are active and visible in frontend and backend interfaces.
| Field | Description |
|---|---|
| Is Active | Whether numbers with this status are considered active in the system |
| Is Suspended | Whether numbers with this status are treated as suspended |
| CRM Only | Whether numbers with this status are CRM-only records |
| Visible in Frontend | Whether this number status is visible to customers in the frontend portal |
| Related Feature Status | Feature status that should be applied to features when number has this status |
| Visible in Backend | Whether this number status is visible to users in the backend system |
Billing
Section titled “Billing”Control billing behaviour for numbers with this status, including whether they can be billed, have calls, or fixed charges applied.
| Field | Description |
|---|---|
| Is Billable | Whether numbers with this status can be included on customer invoices |
| Can Have Calls | Whether numbers with this status can generate call charges |
| Can Have Fixed Charges | Whether numbers with this status can have fixed monthly or periodic charges applied |
Final Bill
Section titled “Final Bill”Special billing rules for final invoices, allowing override of normal cutoff dates and billable status checking.
| Field | Description |
|---|---|
| Ignore Cutoff Date | Whether to ignore billing cutoff dates for final invoices when numbers have this status |
| Ignore Billable Status | Whether to ignore the billable status check for final invoices when numbers have this status |
| Ignore Cutoff Date (Calls) | Whether to ignore billing cutoff dates specifically for call charges on final invoices |
| Ignore Billable Status (Calls) | Whether to ignore the billable status check specifically for call charges on final invoices |
Update Requirements
Section titled “Update Requirements”Specify validation requirements when updating numbers to this status.
| Field | Description |
|---|---|
| Require Status Reason | Whether changing a number to this status requires providing a reason |
System Information
Section titled “System Information”| Field | Description |
|---|---|
| Last Modified | Timestamp of the most recent modification to this number status |
| Created | Timestamp when this number status was created |
Number Types
Section titled “Number Types”A number type categorises numbers, such as landline, mobile or premium rate. Each type carries its own validation rules, pricing and available features, so the platform handles each kind of number correctly.
Number Type
Section titled “Number Type”This section defines the basic properties of the number type including names used in different contexts, display settings, customer product associations, and visibility options. These settings control how the number type appears throughout the system.
| Field | Description |
|---|---|
| Number Type | The primary name for this number type used throughout the system |
| Number Type (Display) | Alternative display name for this number type shown in user interfaces |
| Number Type (Short) | Abbreviated name for this number type used in compact displays |
| Number Type Display Class | CSS class name used for styling this number type in web interfaces |
| Number Type Display Position | Sort order position for displaying this number type in lists |
| Number Type (Itemisation) | Name used for this number type on detailed invoice itemisations |
| Number Type (CDR) | Name used for this number type in generated (outbound) Call Detail Records |
| Alternate Number Type (CDR) | Alternative name used for this number type in generated (outbound) Call Detail Records |
| Customer Products | Customer products that can be associated with numbers of this type |
| Standard Number Type Groups | Standard groups this number type belongs to |
| Number Type Availability | Availability of this number type (Headline, Standard, or Historic) |
| Hidden | Whether this number type is hidden from standard user interfaces |
| Use Inbound Call Types From | Different number type to use for inbound call type determination |
Number Validity
Section titled “Number Validity”This section specifies the validation rules for numbers of this type, including valid prefixes, regular expressions for format checking, and which call types are permitted. These rules ensure numbers are correctly formatted and can be used with appropriate call routing.
| Field | Description |
|---|---|
| Valid Prefixes | Comma-separated list of valid number prefixes for this number type |
| Active Numbers | Regular expression pattern that valid numbers of this type must match |
| Valid Call Types | Call types that are permitted for numbers of this type |
Term Details
Section titled “Term Details”This section defines notice period requirements for numbers of this type, covering both call charges and service charges. These settings determine how much advance notice is required before making changes to features associated with numbers of this type.
| Field | Description |
|---|---|
| Notice Period Length (Calls) | Default length of notice period required before changing call-related features |
| Notice Period Length Type (Calls) | Unit type for the calls notice period length |
| Notice Period Length (Service Charges) | Default length of notice period required before changing service charge features |
| Notice Period Length Type (Service Charges) | Unit type for the service charges notice period length |
Transaction Codes
Section titled “Transaction Codes”This section specifies default transaction codes used for different types of billing activities on numbers of this type, including general transactions, connections, recurring charges, and call charges.
| Field | Description |
|---|---|
| Default Transaction Code | Default transaction code used for general billing activities on numbers of this type |
| Default Connection Transaction Code | Default transaction code used for connection charges on numbers of this type |
| Default Recurring Transaction Code | Default transaction code used for recurring service charges on numbers of this type |
| Default Calls Transaction Code | Default transaction code used for call charges on numbers of this type |
Service Statuses
Section titled “Service Statuses”A service status is a lifecycle state for a service, controlling whether it is active, billable and visible. Statuses are used when enabling, suspending or ceasing services, and decide how attached features are handled.
Service Status Name
Section titled “Service Status Name”Defines the name and display properties of the service status.
| Field | Description |
|---|---|
| Service Status | The name of the service status as displayed throughout the system |
| Service Status (Short) | Abbreviated version of the service status name for compact displays |
| Service Status Display Class | CSS class name used for styling this service status in the interface |
| Service Status Display Position | Sort order for displaying this service status in lists and dropdowns |
Status
Section titled “Status”Controls whether services with this status are active and visible.
| Field | Description |
|---|---|
| Is Active | Whether services with this status are considered active in the system |
| Is Suspended | Whether services with this status are treated as suspended |
| CRM Only | Whether services with this status are CRM-only records |
| Visible in Frontend | Whether this service status is visible to customers in the frontend portal |
| Visible in Backend | Whether this service status is visible to users in the backend system |
Billing
Section titled “Billing”Controls billing behaviour for services with this status.
| Field | Description |
|---|---|
| Is Billable | Whether services with this status can be included on customer invoices |
| Can Have Fixed Charges | Whether services with this status can have fixed or recurring charges applied |
| Related Feature Status | Feature status that should be applied to features when a service has this status |
Update Requirements
Section titled “Update Requirements”Specifies validation requirements when updating services to this status.
| Field | Description |
|---|---|
| Status Reason Required | Whether a status reason is required when setting a service to this status |
System Information
Section titled “System Information”| Field | Description |
|---|---|
| Last Modified | Timestamp of the most recent modification to this service status |
| Created | Timestamp of when this service status was created |
Service Types
Section titled “Service Types”A service type categorises services, defining common properties such as default notice periods and associated customer products. Service types group similar services for configuration and reporting.
Service Type
Section titled “Service Type”Defines the basic properties of the service type, including names and display settings.
| Field | Description |
|---|---|
| Service Type | The primary name for this service type used throughout the system |
| Service Type (Display) | Alternative display name for this service type shown in user interfaces |
| Service Type (Short) | Abbreviated name for this service type used in compact displays |
| Service Type Display Class | CSS class name used for styling this service type in web interfaces |
| Service Type Display Position | Sort order position for displaying this service type in lists |
| Hidden | Whether this service type is hidden from standard user interfaces |
| Customer Products | Customer products that can be associated with services of this type |
| Service Type Groups | Standard groups this service type belongs to |
Term Details
Section titled “Term Details”Defines notice period requirements for services of this type.
| Field | Description |
|---|---|
| Notice Period Length (Service Charges) | Default length of notice period required before changing service charge features |
| Notice Period Length Type (Service Charges) | Unit type for the service charges notice period length |
Transaction Codes
Section titled “Transaction Codes”Default transaction codes used for billing services of this type.
| Field | Description |
|---|---|
| Default Transaction Code | Default transaction code used for general billing activities on services of this type |
| Default Connection Transaction Code | Default transaction code used for connection charges on services of this type |
| Default Recurring Transaction Code | Default transaction code used for recurring service charges on services of this type |
System Information
Section titled “System Information”System-generated information about the service type.
No fields defined for this section.
Feature Statuses
Section titled “Feature Statuses”A feature status tracks the lifecycle state of a feature, such as active, suspended or ceased. Like number statuses, it controls whether the feature provides service and how it is billed. A suspended feature might stop working but still appear on the bill, while a ceased feature stops both service and charges.
Feature Status Name
Section titled “Feature Status Name”This section defines the basic identification and display properties for the feature status, including the name, short name, display class, and position used throughout the system.
| Field | Description |
|---|---|
| Feature Status | The name of this feature status as displayed throughout the system |
| Feature Status (Short) | Abbreviated name for this feature status used in compact displays |
| Feature Status Availability | Availability of this feature status (Headline, Standard, or Historical) |
| Feature Status Display Class | CSS class name used for styling this feature status in the interface |
| Feature Status Display Position | Numeric position for ordering this feature status in lists and dropdowns |
Status
Section titled “Status”This section controls the core status properties, determining whether features with this status are considered active and where they are visible within the system interfaces.
| Field | Description |
|---|---|
| Is Active | Whether features with this status are considered active in the system |
| Is Suspended | Whether features with this status are treated as suspended |
| CRM Only | Whether features with this status are CRM-only records |
| Visible in Frontend | Whether features with this status are visible to customers in the frontend |
| Visible in Backend | Whether features with this status are visible to staff in the backend system |
Billing
Section titled “Billing”This section defines the billing behaviour for features with this status, including whether they can be billed, have call charges, or fixed service charges applied.
| Field | Description |
|---|---|
| Is Billable | Whether features with this status can generate charges on customer invoices |
| Can Have Calls | Whether features with this status can have call usage charges applied |
| Can Have Fixed Charges | Whether features with this status can have fixed service charges applied |
Final Bill
Section titled “Final Bill”This section controls special billing rules that apply when generating final bills for customers, allowing certain features to bypass normal cutoff dates and billable status requirements.
| Field | Description |
|---|---|
| Ignore Cutoff Date | Whether to ignore billing cutoff dates when generating final bills for features with this status |
| Ignore Billable Status | Whether to ignore the billable status when generating final bills for features with this status |
| Ignore Cutoff Date (Calls) | Whether to ignore billing cutoff dates for call charges when generating final bills for features with this status |
| Ignore Billable Status (Calls) | Whether to ignore the billable status for call charges when generating final bills for features with this status |
Update Requirements
Section titled “Update Requirements”This section defines validation requirements that must be met when updating features to this status, such as requiring status change reasons.
| Field | Description |
|---|---|
| Require Status Reason | Whether a reason must be provided when changing features to this status |
System Information
Section titled “System Information”| Field | Description |
|---|---|
| Last Modified | Timestamp of the most recent modification to this feature status |
| Created | Timestamp when this feature status was created |
Related
Section titled “Related”- Numbers, Services and Features: the records these lists apply to.
- Suspend and Unsuspend: how status changes flow through an account.
Want lifecycle states that bill exactly the way your business works? see how SAFE Billing Platform handles service lifecycles