Error
This idea is related to another idea that has already been implemented. And we do appreciate that SMS Pipeline Actions can now chose to have an Interaction logged. But now as I'm beginning to work with interactions more and maybe starting to understand them a little better, I would like to suggest an enhancement to how these SMS Pipeline interactions are structured.
As currently designed, there is a single Interaction Channel for all SMS pipeline interactions, each individual pipeline has an Interaction Component, and the pipeline actions are the interactions. For churches that only have a single pipeline but LOTs of actions (i.e. keywords), the different pipeline action interactions are mixed in together in a single Interaction Component - making it challenging to work with for reporting and such.
A much better (more helpful) structure would be to have a separate Interaction Channel for each SMS Pipeline (maybe titled "SMS Pipeline: <name of pipeline>"). Then each action that logs interactions would have its own Interaction Component (again titled based on the title of the action). Then interactions within a component would actually represent the interactions for an individual action.
Cultivate your ideas for maximum impact with these helpful submission tips that will increase the chances of your brilliant concepts becoming reality.