ACC: Inbound Replies on the Extended SMPP Connector | Community
Skip to main content
A
Anonymous
May 13, 2019
Solved

ACC: Inbound Replies on the Extended SMPP Connector

  • May 13, 2019
  • 1 reply
  • 1510 views

I am looking for a way to setup conditional replies on the "Automated Reply" feature available on the extended connector to no avail so far.

My Scenario.

KeywordShortcodeAnswerAdditional Action
Lorem1234Hello LoremBlacklist
Ipsum1234Hello IpsumBlacklist

I want to setup a reply and action for any keywords not matched, ie. "Sorry we didn't understand your request, please send a valid keyword"

I don't see anyway to do it with the OOTB feature in the extended SMPP connector, I have a related question on here ACC: Inbound SMS Activity

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by Jonathon_wodnicki

    Hi,

    I think that activity requires all actions to be scripted out, which defeats the purpose of using a workflow and really its existence as a workflow activity. Instead here just instead poll nms:inSMS for new messages, either with scheduler + query + split or an advanced js activity with sleep and transitions, using an xtk:option to track position in the table. Transitions would go to update activities and continuous deliveries, etc, depending on desired actions.

    Thanks,

    -Jon

    1 reply

    Jonathon_wodnicki
    Community Advisor
    Jonathon_wodnickiCommunity AdvisorAccepted solution
    Community Advisor
    May 13, 2019

    Hi,

    I think that activity requires all actions to be scripted out, which defeats the purpose of using a workflow and really its existence as a workflow activity. Instead here just instead poll nms:inSMS for new messages, either with scheduler + query + split or an advanced js activity with sleep and transitions, using an xtk:option to track position in the table. Transitions would go to update activities and continuous deliveries, etc, depending on desired actions.

    Thanks,

    -Jon

      Terms & ConditionsAccessibility statement

      Loading footer...