Leveraging multiple SMS short codes in AJO | Community
Skip to main content
R
RyanMo20
Level 2
January 23, 2026
Question

Leveraging multiple SMS short codes in AJO

  • January 23, 2026
  • 2 replies
  • 43 views

Im curious if others have implemented the use of multiple short codes for SMS journeys in AJO. As an enterprise business, having a short code per brand to allow for customers to opt in and out of specific brands seems like a no-brainer, but it seems AJO may not be equipped to handle that without a custom solution. Anyone have a similar experience with SMS in AJO?

2 replies

M
MontexHo
Level 2
January 23, 2026

I’ve had this question previously. I don’t believe the issue is so much configuration in AJO, but you would need to purchase multiple Short Codes and have them configured with the SMS aggregator.

Doing so should give you the ability to configure an SMS Channel and create a surface for each brand Short Code. You should be able to configure the surface based on brand when send SMS out of AJO. 

Please note - I’m a user of AJO, but this question has come up several times, but my clients never went the multiple short code route once pricing started coming into the mix.  

 

    R
    RyanMo20Author
    Level 2
    January 23, 2026

    Thank you for the context! My real question is based around SMS consent and how to track that at the short code level.

    DavidKangni
    Community Advisor
    DavidKangniCommunity Advisor
    Community Advisor
    January 27, 2026

    ​@RyanMo20 

    you will have two level of consent, the channel level consent which is consent.marketing.sms.val and the consent.idSpecific which will handle the consent at short codes level.

     

     AJO will always look into the consent profile attributes before sending any communication.

    • It will start with channel-level consent (consents.marketing). If the profile is opted out, it will not send the communication.
    • If the channel-level consent is not present or the profile is opted in, it will then check the identity-level consent (consents.idSpecific).

    In other words, channel-level consent takes precedence over identity-level consent.

    https://experienceleague.adobe.com/en/docs/experience-platform/xdm/field-groups/profile/consents#idspecific

    Thanks

    David Kangni
      R
      RyanMo20Author
      Level 2
      January 27, 2026

      Thanks ​@DavidKangni this is really helpful! Is this something you have worked with personally? Any gotchas or pitfalls to be on the lookout for? Thanks!

      DavidKangni
      Community Advisor
      DavidKangniCommunity Advisor
      Community Advisor
      January 27, 2026

      ​@RyanMo20 

      Yes, I did it for couple of AJO projects.
      Thanks,

      David Kangni
        Terms & ConditionsAccessibility statement

        Loading footer...