Hi @jfarrell,
First, with an OOTB Choice Collector, the options dictate the node outcomes. The auth tree structure is static in nature (e.g you can’t really create outcomes for all of the possible phone numbers… and wire them to the next nodes…) - so a Configuration Provider node would probably not make it if this was possible.
So taking this blog AM Choice Collector Dynamic List as a basis, the scripted decision node task is to transform the phone map to an options array like [ “home: 5555555555”, "Mobile: 6666666666, … ] that is rendered to the user via the ChoiceCallback, and then after user selection, store the outcome (a phone number) in shared state, to be used by the next node…
Regards
Patrick