Long codes and short codes in MobileConnect are provisioned per-country and are constrained by local telecom regulations governing two-way SMS traffic — specifically, the ability to receive inbound messages (replies, keyword opt-ins/opt-outs) from subscribers within that country ' s mobile network. A single long code typically cannot reliably receive inbound SMS traffic from multiple distinct countries due to carrier routing and regulatory requirements, meaning that if NTO needs subscribers in Brazil, Mexico, and Chile to be able to text back to the number (rather than only receive outbound messages), a separate, locally-provisioned long code per country becomes a hard technical and regulatory requirement rather than a preference. This is the deciding functional question that drives whether additional long codes are needed. UTF-8 character support (A) is a message-encoding setting independent of how many long codes are provisioned. Different From Names by country (C) can typically be managed through message configuration and sender profiles without requiring separate long codes. Independent reporting by country (D) can be achieved through data segmentation and filtering in reporting regardless of whether one or multiple long codes are used. Reference: MobileConnect Long Codes, International SMS Regulations.