Understand your compliance responsibilities when using Bring Your Own Carrier trunks
with Salesforce. For Bring Your Own Carrier numbers, both attestation and emergency services
setup are your carrier's responsibility—coordinate with them directly to ensure
compliance.
If you're making outbound calls through your Bring Your Own Carrier trunk, here's what you
need to know: Salesforce doesn't handle STIR/SHAKEN attestation for those calls—that's your
carrier's responsibility.
Note
Calls from Salesforce-managed numbers automatically get Full Attestation (A). But if
you're using Bring Your Own Carrier numbers, your attestation level depends on what your
carrier assigns. We recommend reaching out to your carrier to make sure your outbound
calls are getting the highest attestation level they can provide.
Emergency Services
Salesforce routes emergency calls originating from Bring Your Own Carrier trunks to the
carrier. However, additional setup with your carrier is required to ensure emergency calling
works correctly. Getting the call routed correctly, providing accurate location information,
and making sure it reaches the right emergency dispatcher (PSAP) is your carrier's
responsibility.
If you're switching from Salesforce-managed numbers to Bring Your Own Carrier numbers, any
emergency services setup you had in AFCC (including RedSky integration) doesn't carry over
to your Bring Your Own Carrier carrier. You'll need to contact your carrier directly and
give them the exact physical address where each phone number is being used. This is really
important—without accurate location info, emergency responders might not be able to find you
in an emergency.
¿Resolvió este artículo su problema?
¡Háganos saber cómo podemos mejorar!
Cargando
Salesforce Help | Article
Cookie Consent Manager
Cookie Consent Manager
General Information
Required Cookies
Functional Cookies
Advertising Cookies
General Information
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.