How configuration profiles and rules work#

Configuration profiles and rules work together to automate DID number setup after purchase. A profile stores the settings to apply to a number — such as voice routing, SMS routing, and Capacity — while a rule determines when and whether that profile is applied automatically.

Understanding how these two components relate to each other is the foundation for building a consistent, repeatable provisioning workflow.

For the field-level details, see Configuration profiles reference and Rules reference. For the procedures that use these settings, see Configuration profiles how-to guides.

Configuration profiles overview#

A configuration profile is a reusable set of DID number settings. A profile can include voice routing, SMS routing, Capacity settings, and a description.

Profiles are useful when multiple DID numbers need the same setup. Instead of configuring each DID number separately, you can apply one profile to selected numbers or use rules to apply a profile automatically after purchase.

For profile fields, actions, and constraints, see Configuration profiles reference. For creating, applying, editing, or deleting profiles, see Configuration profiles how-to guides.

Rules overview#

Rules apply configuration profiles to newly purchased DID numbers based on conditions such as country, number type, region, or city.

Important

Rules apply only to newly purchased DID numbers. They do not update DID numbers that already exist in your account.

For rule fields, filters, actions, and priority values, see Rules reference. For creating or managing rules, see Configuration profiles how-to guides.

Rule matching order#

Rules are evaluated when a new DID number is added to your account. DIDWW checks the rule conditions and applies the configuration profile that best matches the number.

Rule conditions can be broad or specific. A broad rule can apply to all selected countries. A more specific rule can be narrowed by number type, region, or city.

        flowchart LR
    %% Start of the process
    start((Purchase New DID<br>Start Rule Matching)):::customer --> city(("DID Matches a<br>City?")):::staff

    %% Unified Apply / Do Not Apply outputs
    city --> yes
    region --> yes
    number --> yes
    country --> yes
    yes --> apply((Apply Profile)):::completed
    no --> dontapply((Do not Apply<br>Profile)):::canceled

    %% Sequential rule matching path with shared Yes and common No Match chain
    city --> nomatch1[No Match Found]:::status
    nomatch1 --> region(("DID matches a<br>Region?")):::staff
    region --> nomatch2[No Match Found]:::status
    nomatch2 --> number(("DID matches a<br>Number Type?")):::staff
    number --> nomatch3[No Match Found]:::status
    nomatch3 --> country(("DID matches a<br>Country?")):::staff
    country --> nomatch4[No Match Found]:::status
    nomatch4 --> allcountries(("Is there a<br>rule set for<br>All Countries?")):::staff
    allcountries --> yes[Yes]:::completed
    allcountries --> no[No]:::status

    %% Color and style definitions (matching the provided image)
    classDef status fill:#f9e6dc,stroke:#ff5c1a,stroke-width:2px,color:#1f2d3d;
    classDef staff fill:#fff4cf,stroke:#ffb000,stroke-width:2px,color:#1f2d3d;
    classDef customer fill:#d7ecfb,stroke:#008ce3,stroke-width:2px,color:#1f2d3d;
    classDef completed fill:#d0f0ec,stroke:#00a99d,stroke-width:2px,color:#1f2d3d;
    classDef canceled fill:#f6d6df,stroke:#e83f6f,stroke-width:2px,color:#1f2d3d;

When multiple rules can match the same DID number, DIDWW checks rules from the most specific match to the broadest match. City-level rules take priority over regional rules, regional rules take priority over number-type rules, and number-type rules take priority over country-level rules.

For priority details, see Rule priority.

Profile and rule relationship#

A rule does not contain routing or Capacity settings directly. Instead, the rule points to a configuration profile. When a newly purchased DID number matches the rule conditions, DIDWW applies the selected profile to that number.

For example, you could create a rule that matches any new Local number purchased in the United States and applies a profile that assigns a specific voice trunk, SMS trunk, Capacity group, and description — without any manual steps after the purchase.

For the profile fields that the rule can apply, see Configuration profiles reference. For the rule fields and matching order, see Rules reference.

Profile application methods#

Configuration profiles can be applied in two ways:

  • Manually, from My Numbers, using the Apply Configuration Profile batch action. Use this for existing numbers that were purchased before a rule was in place, or for numbers that need a one-off configuration. For the procedure, see Apply configuration profile manually.

  • Automatically, from Configuration Profiles > Rules, when a newly purchased number matches a rule’s conditions. Use this to ensure every new number receives a standard setup immediately after purchase. For rule creation, see Create rules for profiles.

Registration and service requirements#

Configuration profiles can help standardize setup after a DID number is purchased or ported in, but they do not replace country, number type, or service requirements. If a DID number requires end-user verification, identity details, or address details, those requirements still apply.

For registration-related number management, see My Numbers and End-user verification.