Northern Trail Outfitters (NTO) wants email subscribers to adopt their app. They are investigating using MobileConnect features since over 90% of…

MobileConnect depends on country-specific telecommunications regulations.

• Short and long codes are provisioned per country; some markets have neither, so availability varies (A).

• Inbound (MO) traffic is delivered only when the handset sends to a code registered in its local country; cross-border inbound is unsupported (C).

• MobileConnect SMS is not offered in every country that Salesforce services; marketers must verify the supported-country list before launch (D).

Carrier billing is handled through Salesforce, not by direct operator invoicing, and opt-in can occur via API, import, or keyword, so B and E are incorrect.

B – Customers are billed by Salesforce per message; operators do not invoice NTO directly.

E – Subscribers can be opted in via API, contact import with consent, or Smart Capture— not only via inbound SMS.

1. Salesforce Help: “MobileConnect Country and Code Availability”, Marketing Cloud Mobile Messaging Guide, table ‘Supported Countries’, notes 1-3.

2. Salesforce Help: “SMS Code Types and Restrictions”, same guide, section ‘Short and Long Codes Are Country Specific’.

3. Salesforce Help: “Create and Manage Subscriber Opt-Ins”, MobileConnect Admin, paragraph ‘Importing Existing Consents’.