{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/practice-gets-calls-before-congestion/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/practice-gets-calls-before-congestion/",
        "slug": "practice-gets-calls-before-congestion",
        "url": "https://update.dsesecurity.com/updates/practice-gets-calls-before-congestion/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/practice-gets-calls-before-congestion.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/practice-gets-calls-before-congestion/"
        },
        "title": "Practice GETS calls before normal telephone service is congested",
        "summary": "Train enrolled personnel to use the Government Emergency Telecommunications Service and maintain their access information before a crisis.",
        "format": {
            "slug": "checklist",
            "name": "Checklist"
        },
        "priority": {
            "slug": "important",
            "name": "Important"
        },
        "featured": false,
        "image": {
            "theme": "network-infrastructure",
            "label": "Networks & infrastructure",
            "alt": "Resilient network core with engineered blue and gold data paths.",
            "card_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-card.webp?v=1.8.20",
            "hero_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-hero.webp?v=1.8.20",
            "social_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20",
            "width": 2400,
            "height": 1350
        },
        "topics": [
            {
                "slug": "business-continuity",
                "name": "Business Continuity",
                "url": "https://update.dsesecurity.com/topic/business-continuity/"
            },
            {
                "slug": "networks-infrastructure",
                "name": "Networks & Infrastructure",
                "url": "https://update.dsesecurity.com/topic/networks-infrastructure/"
            }
        ],
        "author": {
            "name": "DSE Security Editorial Team",
            "url": "https://update.dsesecurity.com/#editorial-team",
            "type": "Organization"
        },
        "publisher": {
            "name": "Detection Systems & Engineering",
            "url": "https://dsesecurity.com/"
        },
        "published_at": "2026-08-25T21:34:32+00:00",
        "modified_at": "2026-08-26T13:27:46+00:00",
        "reviewed_on": "2026-08-25",
        "reading_minutes": 3,
        "word_count": 528,
        "potentially_affected": "Organizations and personnel eligible for or enrolled in CISA's Government Emergency Telecommunications Service",
        "dse_recommendation": "Enroll only through the official program, protect user credentials, and conduct approved practice calls from realistic devices and locations.",
        "primary_source": {
            "name": "CISA Priority Telecommunications Services presentation",
            "url": "https://405d.hhs.gov/Documents/405d-webinar-2024-0327-cisa-telcom-svc.pdf",
            "published_on": null,
            "authority": "405d.hhs.gov"
        },
        "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/",
        "usage_info": "https://update.dsesecurity.com/usage/",
        "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.",
        "content_html": "<p>GETS can support priority calling for enrolled subscribers when ordinary calls are difficult to complete, but users still need their access information, a current dialing workflow, and a working connection from the devices available during the incident.</p>\n<h2>Source fact:</h2>\n<p>A <a href=\"https://405d.hhs.gov/Documents/405d-webinar-2024-0327-cisa-telcom-svc.pdf\" target=\"_blank\" rel=\"noopener noreferrer\">CISA Priority Telecommunications Services presentation hosted by HHS 405(d)</a> says events including cyberattacks, extreme weather, human error, and high call volume can degrade, destroy, or overload network infrastructure. It explains that GETS enhances voice-call completion when commercial networks are overloaded or impaired and provides end-to-end priority over landline commercial networks.</p>\n<p>The presentation instructs a user to dial the universal GETS access number, enter the user&#8217;s PIN after the tone, and then enter the destination number when prompted. Its best-practices slide recommends practicing with GETS and WPS, making test calls frequently, and incorporating those calls into training exercises. It also directs users to report call problems and lists the Priority Telecommunications Service Center&#8217;s 24-hour assistance number. The presentation reports a generally greater-than-95-percent GETS completion rate; it does not promise that every call will complete or that destroyed infrastructure will remain available.</p>\n<h2>Boundary</h2>\n<p>Use current CISA resources and the CISA Priority Telecommunications Service Center for enrollment and dialing details. This article does not enroll a person or organization or replace CISA instructions. The presentation distinguishes GETS priority over wireline commercial networks from WPS priority over wireless networks. The following continuity steps are DSE recommendations; they do not assert that a specific call path will work.</p>\n<h2>Applicability questions</h2>\n<ul>\n<li>Which incident roles need to place essential calls during congestion, and are those people eligible and currently enrolled?</li>\n<li>Can they retrieve their GETS access information if corporate identity, email, or mobile-data service is unavailable?</li>\n<li>Which originating phones, PBXs, calling plans, and locations are likely during activation?</li>\n<li>Are destination numbers maintained offline and expressed in a dialable format?</li>\n<li>Who reports lost credentials, role changes, departures, and failed test calls?</li>\n</ul>\n<h2>DSE recommendation:</h2>\n<p>Use CISA&#8217;s current process to determine eligibility and enroll the minimum operational roles that require priority calling. Assign program administration, user training, roster review, and credential-loss response. Protect PINs from shared documents and tickets while ensuring each user has an approved, resilient way to retrieve their own information during an outage.</p>\n<p>Conduct practice calls only as permitted by current program guidance. Include the actual devices and calling paths users expect at a primary site, alternate site, home, and field location. Have the user follow the complete sequence, reach a designated test recipient, and record only nonsecret results. Pair the test with scenarios in which corporate contact lists, single sign-on, mobile data, or normal PBX dialing are unavailable. Maintain satellite, radio, alternate-carrier, or other communications where the continuity assessment requires them.</p>\n<h2>Verification and evidence</h2>\n<p>Keep an access-controlled roster of active enrolled roles, training dates, approved practice-call records, failure tickets, CISA support contacts, and quarterly or other defined review evidence. Do not store PINs in the evidence package. A useful exercise verifies both the user&#8217;s procedure and the destination&#8217;s readiness to recognize the call and exchange the necessary information. Remove or update access promptly after role and employment changes through the official process.</p>\n<h2>Official references</h2>\n<ul>\n<li><a href=\"https://405d.hhs.gov/Documents/405d-webinar-2024-0327-cisa-telcom-svc.pdf\" target=\"_blank\" rel=\"noopener noreferrer\">CISA Priority Telecommunications Services presentation, hosted by HHS 405(d)</a></li>\n</ul>",
        "content_text": "GETS can support priority calling for enrolled subscribers when ordinary calls are difficult to complete, but users still need their access information, a current dialing workflow, and a working connection from the devices available during the incident.\nSource fact:\nA CISA Priority Telecommunications Services presentation hosted by HHS 405(d) says events including cyberattacks, extreme weather, human error, and high call volume can degrade, destroy, or overload network infrastructure. It explains that GETS enhances voice-call completion when commercial networks are overloaded or impaired and provides end-to-end priority over landline commercial networks.\nThe presentation instructs a user to dial the universal GETS access number, enter the user’s PIN after the tone, and then enter the destination number when prompted. Its best-practices slide recommends practicing with GETS and WPS, making test calls frequently, and incorporating those calls into training exercises. It also directs users to report call problems and lists the Priority Telecommunications Service Center’s 24-hour assistance number. The presentation reports a generally greater-than-95-percent GETS completion rate; it does not promise that every call will complete or that destroyed infrastructure will remain available.\nBoundary\nUse current CISA resources and the CISA Priority Telecommunications Service Center for enrollment and dialing details. This article does not enroll a person or organization or replace CISA instructions. The presentation distinguishes GETS priority over wireline commercial networks from WPS priority over wireless networks. The following continuity steps are DSE recommendations; they do not assert that a specific call path will work.\nApplicability questions\n\nWhich incident roles need to place essential calls during congestion, and are those people eligible and currently enrolled?\nCan they retrieve their GETS access information if corporate identity, email, or mobile-data service is unavailable?\nWhich originating phones, PBXs, calling plans, and locations are likely during activation?\nAre destination numbers maintained offline and expressed in a dialable format?\nWho reports lost credentials, role changes, departures, and failed test calls?\n\nDSE recommendation:\nUse CISA’s current process to determine eligibility and enroll the minimum operational roles that require priority calling. Assign program administration, user training, roster review, and credential-loss response. Protect PINs from shared documents and tickets while ensuring each user has an approved, resilient way to retrieve their own information during an outage.\nConduct practice calls only as permitted by current program guidance. Include the actual devices and calling paths users expect at a primary site, alternate site, home, and field location. Have the user follow the complete sequence, reach a designated test recipient, and record only nonsecret results. Pair the test with scenarios in which corporate contact lists, single sign-on, mobile data, or normal PBX dialing are unavailable. Maintain satellite, radio, alternate-carrier, or other communications where the continuity assessment requires them.\nVerification and evidence\nKeep an access-controlled roster of active enrolled roles, training dates, approved practice-call records, failure tickets, CISA support contacts, and quarterly or other defined review evidence. Do not store PINs in the evidence package. A useful exercise verifies both the user’s procedure and the destination’s readiness to recognize the call and exchange the necessary information. Remove or update access promptly after role and employment changes through the official process.\nOfficial references\n\nCISA Priority Telecommunications Services presentation, hosted by HHS 405(d)",
        "content_markdown": "GETS can support priority calling for enrolled subscribers when ordinary calls are difficult to complete, but users still need their access information, a current dialing workflow, and a working connection from the devices available during the incident.\n\n## Source fact:\n\nA [CISA Priority Telecommunications Services presentation hosted by HHS 405(d)](https://405d.hhs.gov/Documents/405d-webinar-2024-0327-cisa-telcom-svc.pdf) says events including cyberattacks, extreme weather, human error, and high call volume can degrade, destroy, or overload network infrastructure. It explains that GETS enhances voice-call completion when commercial networks are overloaded or impaired and provides end-to-end priority over landline commercial networks.\n\nThe presentation instructs a user to dial the universal GETS access number, enter the user’s PIN after the tone, and then enter the destination number when prompted. Its best-practices slide recommends practicing with GETS and WPS, making test calls frequently, and incorporating those calls into training exercises. It also directs users to report call problems and lists the Priority Telecommunications Service Center’s 24-hour assistance number. The presentation reports a generally greater-than-95-percent GETS completion rate; it does not promise that every call will complete or that destroyed infrastructure will remain available.\n\n## Boundary\n\nUse current CISA resources and the CISA Priority Telecommunications Service Center for enrollment and dialing details. This article does not enroll a person or organization or replace CISA instructions. The presentation distinguishes GETS priority over wireline commercial networks from WPS priority over wireless networks. The following continuity steps are DSE recommendations; they do not assert that a specific call path will work.\n\n## Applicability questions\n\n- Which incident roles need to place essential calls during congestion, and are those people eligible and currently enrolled?\n\n- Can they retrieve their GETS access information if corporate identity, email, or mobile-data service is unavailable?\n\n- Which originating phones, PBXs, calling plans, and locations are likely during activation?\n\n- Are destination numbers maintained offline and expressed in a dialable format?\n\n- Who reports lost credentials, role changes, departures, and failed test calls?\n\n## DSE recommendation:\n\nUse CISA’s current process to determine eligibility and enroll the minimum operational roles that require priority calling. Assign program administration, user training, roster review, and credential-loss response. Protect PINs from shared documents and tickets while ensuring each user has an approved, resilient way to retrieve their own information during an outage.\n\nConduct practice calls only as permitted by current program guidance. Include the actual devices and calling paths users expect at a primary site, alternate site, home, and field location. Have the user follow the complete sequence, reach a designated test recipient, and record only nonsecret results. Pair the test with scenarios in which corporate contact lists, single sign-on, mobile data, or normal PBX dialing are unavailable. Maintain satellite, radio, alternate-carrier, or other communications where the continuity assessment requires them.\n\n## Verification and evidence\n\nKeep an access-controlled roster of active enrolled roles, training dates, approved practice-call records, failure tickets, CISA support contacts, and quarterly or other defined review evidence. Do not store PINs in the evidence package. A useful exercise verifies both the user’s procedure and the destination’s readiness to recognize the call and exchange the necessary information. Remove or update access promptly after role and employment changes through the official process.\n\n## Official references\n\n- [CISA Priority Telecommunications Services presentation, hosted by HHS 405(d)](https://405d.hhs.gov/Documents/405d-webinar-2024-0327-cisa-telcom-svc.pdf)"
    },
    "json_ld": {
        "@context": "https://schema.org",
        "@graph": [
            {
                "@type": "Organization",
                "@id": "https://dsesecurity.com/#organization",
                "name": "Detection Systems & Engineering",
                "alternateName": "DSE Security",
                "url": "https://dsesecurity.com/",
                "logo": {
                    "@type": "ImageObject",
                    "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20"
                }
            },
            {
                "@type": "Organization",
                "@id": "https://update.dsesecurity.com/#editorial-team",
                "name": "DSE Security Editorial Team",
                "url": "https://update.dsesecurity.com/",
                "parentOrganization": {
                    "@id": "https://dsesecurity.com/#organization"
                }
            },
            {
                "@type": "WebSite",
                "@id": "https://update.dsesecurity.com/#website",
                "name": "DSE Updates",
                "alternateName": "DSE Security Knowledge Hub",
                "url": "https://update.dsesecurity.com/",
                "inLanguage": "en-US",
                "publisher": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "potentialAction": {
                    "@type": "SearchAction",
                    "target": {
                        "@type": "EntryPoint",
                        "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}"
                    },
                    "query-input": "required name=search_term_string"
                }
            },
            {
                "@type": "WebPage",
                "@id": "https://update.dsesecurity.com/updates/practice-gets-calls-before-congestion/",
                "url": "https://update.dsesecurity.com/updates/practice-gets-calls-before-congestion/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-08-25"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/practice-gets-calls-before-congestion/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Practice GETS calls before normal telephone service is congested",
                        "item": "https://update.dsesecurity.com/updates/practice-gets-calls-before-congestion/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/practice-gets-calls-before-congestion/#article",
                "identifier": "https://update.dsesecurity.com/updates/practice-gets-calls-before-congestion/",
                "url": "https://update.dsesecurity.com/updates/practice-gets-calls-before-congestion/",
                "headline": "Practice GETS calls before normal telephone service is congested",
                "description": "Train enrolled personnel to use the Government Emergency Telecommunications Service and maintain their access information before a crisis.",
                "abstract": "Train enrolled personnel to use the Government Emergency Telecommunications Service and maintain their access information before a crisis.",
                "articleBody": "GETS can support priority calling for enrolled subscribers when ordinary calls are difficult to complete, but users still need their access information, a current dialing workflow, and a working connection from the devices available during the incident.\nSource fact:\nA CISA Priority Telecommunications Services presentation hosted by HHS 405(d) says events including cyberattacks, extreme weather, human error, and high call volume can degrade, destroy, or overload network infrastructure. It explains that GETS enhances voice-call completion when commercial networks are overloaded or impaired and provides end-to-end priority over landline commercial networks.\nThe presentation instructs a user to dial the universal GETS access number, enter the user’s PIN after the tone, and then enter the destination number when prompted. Its best-practices slide recommends practicing with GETS and WPS, making test calls frequently, and incorporating those calls into training exercises. It also directs users to report call problems and lists the Priority Telecommunications Service Center’s 24-hour assistance number. The presentation reports a generally greater-than-95-percent GETS completion rate; it does not promise that every call will complete or that destroyed infrastructure will remain available.\nBoundary\nUse current CISA resources and the CISA Priority Telecommunications Service Center for enrollment and dialing details. This article does not enroll a person or organization or replace CISA instructions. The presentation distinguishes GETS priority over wireline commercial networks from WPS priority over wireless networks. The following continuity steps are DSE recommendations; they do not assert that a specific call path will work.\nApplicability questions\n\nWhich incident roles need to place essential calls during congestion, and are those people eligible and currently enrolled?\nCan they retrieve their GETS access information if corporate identity, email, or mobile-data service is unavailable?\nWhich originating phones, PBXs, calling plans, and locations are likely during activation?\nAre destination numbers maintained offline and expressed in a dialable format?\nWho reports lost credentials, role changes, departures, and failed test calls?\n\nDSE recommendation:\nUse CISA’s current process to determine eligibility and enroll the minimum operational roles that require priority calling. Assign program administration, user training, roster review, and credential-loss response. Protect PINs from shared documents and tickets while ensuring each user has an approved, resilient way to retrieve their own information during an outage.\nConduct practice calls only as permitted by current program guidance. Include the actual devices and calling paths users expect at a primary site, alternate site, home, and field location. Have the user follow the complete sequence, reach a designated test recipient, and record only nonsecret results. Pair the test with scenarios in which corporate contact lists, single sign-on, mobile data, or normal PBX dialing are unavailable. Maintain satellite, radio, alternate-carrier, or other communications where the continuity assessment requires them.\nVerification and evidence\nKeep an access-controlled roster of active enrolled roles, training dates, approved practice-call records, failure tickets, CISA support contacts, and quarterly or other defined review evidence. Do not store PINs in the evidence package. A useful exercise verifies both the user’s procedure and the destination’s readiness to recognize the call and exchange the necessary information. Remove or update access promptly after role and employment changes through the official process.\nOfficial references\n\nCISA Priority Telecommunications Services presentation, hosted by HHS 405(d)",
                "datePublished": "2026-08-25T21:34:32+00:00",
                "dateModified": "2026-08-26T13:27:46+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/practice-gets-calls-before-congestion/"
                },
                "inLanguage": "en-US",
                "isAccessibleForFree": true,
                "author": {
                    "@type": "Organization",
                    "name": "DSE Security Editorial Team",
                    "url": "https://update.dsesecurity.com/#editorial-team"
                },
                "publisher": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "image": {
                    "@type": "ImageObject",
                    "@id": "https://update.dsesecurity.com/updates/practice-gets-calls-before-congestion/#primaryimage",
                    "url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20",
                    "contentUrl": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20",
                    "width": 1200,
                    "height": 630,
                    "caption": "Practice GETS calls before normal telephone service is congested"
                },
                "articleSection": [
                    "Business Continuity",
                    "Networks & Infrastructure"
                ],
                "keywords": [
                    "Business Continuity",
                    "Networks & Infrastructure",
                    "Checklist",
                    "Important priority"
                ],
                "genre": "Checklist",
                "about": [
                    {
                        "@type": "Thing",
                        "name": "Business Continuity",
                        "url": "https://update.dsesecurity.com/topic/business-continuity/"
                    },
                    {
                        "@type": "Thing",
                        "name": "Networks & Infrastructure",
                        "url": "https://update.dsesecurity.com/topic/networks-infrastructure/"
                    }
                ],
                "wordCount": 528,
                "timeRequired": "PT3M",
                "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/",
                "usageInfo": "https://update.dsesecurity.com/usage/",
                "copyrightHolder": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.",
                "citation": {
                    "@type": "CreativeWork",
                    "name": "CISA Priority Telecommunications Services presentation",
                    "url": "https://405d.hhs.gov/Documents/405d-webinar-2024-0327-cisa-telcom-svc.pdf"
                }
            }
        ]
    }
}