Julie_McNichols | 2017-06-07 16:13:07 UTC | #1
This is an architect question. Is it possible to create dynamic menus in an architect task? For instance, if we were implementing a store locator and got back 3 stores for one zip code and four for another, could we use TTS to read the location names and menu options in a menu? Once the caller selected an option we would need to index that location option back to the address.
tim.smith | 2017-06-12 13:01:27 UTC | #2
To directly address "are there dynamic menus?", the answer is no. I've logged an enhancement request for this, however.
Julie_McNichols, post:1, topic:1380
got back 3 stores for one zip code and four for another, could we use TTS to read the location names and menu options in a menu? Once the caller selected an option we would need to index that location option back to the address.
You should be able to get pretty close to this. Here's some ideas:
got back 3 stores for one zip code and four for another, could we use TTS
You could get this information back from a bridge action. You can't get an array of data from a bridge action, so you have two options for reading this prompt:
- The bridge action can return a flattened list of information and Architect could assemble the data into a TTS string. This might be difficult since Architect doesn't support lists returned from bridge actions, so you would have to expect a series of numbered properties and check for values as you assemble the TTS prompt (e.g. looking for values in
zip1, zip2, zip3`, etc...). - The bridge action could return the full string that should be played via TTS instead of just returning the raw location data. This would prevent Architect from having to assemble the TTS string from variables.
Julie_McNichols, post:1, topic:1380
Once the caller selected an option we would need to index that location option back to the address.
Instead of using an actual menu to collect the response, you could use a Collect Input action to read the caller's option in as data. Then use another bridge action to send their selection back to the external system. Their option could also be used to determine one of a set of fixed options for routing or to set participant data on the call for an agent integration to make use of.
system | 2017-07-13 13:01:43 UTC | #3
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.
This post was migrated from the old Developer Forum.
ref: 1380