Binding a user experience workflow to a destination identifier
A user experience workflow may be configured based on input received for various object types selectively arranged within the user experience workflow and then bound to a destination identifier, such as a telephone number or web address. A user interface of software for configuring a user experience workflow is presented at a user device and input from that user device is used to selectively arrange objects within a user experience workflow and/or to configure objects thereof. After configurations are applied to the objects, the user experience workflow is bound to the destination identifier. An end user device which accesses the destination identifier (e.g., by calling the telephone number, visiting the web address, or using an application connecting to the web address) may then traverse the user experience workflow, including in some cases having configured content presented thereto.
1. A method, comprising:
binding, to a destination identifier, a user experience workflow configured to include one or more paths for traversing objects including a media playback object used to present visual content; and
serving the user experience workflow to a user device based on a request, from the user device, for the destination identifier.
2. The method of claim 1 , wherein the user device is a first user device, the method comprising:
obtaining, via a graphical user interface, input from a second user device; and
generating the user experience workflow using the input.
3. The method of claim 1 , wherein the destination identifier is a telephone number and the request for the destination identifier is a call to the telephone number, and wherein serving the user experience workflow to the user device comprises:
initiating the user experience workflow for the call to the telephone number based on a dialing of the telephone number at the user device.
4. The method of claim 1 , wherein the destination identifier is a web address and the request for the destination identifier is a browser request for the web address, and wherein serving the user experience workflow to the user device comprises:
initiating the user experience workflow for the browser request for the web address based on a transmission of the browser request for the web address from the user device.
5. The method of claim 1 , wherein the destination identifier is a telephone number, and wherein binding the user experience workflow to the destination identifier comprises:
creating a telephony routing rule that routes calls to the destination identifier through the user experience workflow.
6. The method of claim 1 , wherein the destination identifier is a web address, and wherein binding the user experience workflow to the destination identifier comprises:
embedding scripting instructions within a website associated with the web address to cause an invocation of the user experience workflow when the web address is accessed.
7. The method of claim 1 , wherein the destination identifier is a web address, and wherein binding the user experience workflow to the destination identifier comprises:
pushing the user experience workflow to a software development kit embedded within an application that accesses a website associated with the web address.
8. The method of claim 1 , wherein the user device is a first user device, the method comprising:
transmitting, to a second user device from which input is obtained and used to generate the user experience workflow, an alert based on a length of the user experience workflow.
9. A non-transitory computer readable medium storing instructions operable to cause one or more processors to perform operations comprising:
binding, to a destination identifier, a user experience workflow configured to include one or more paths for traversing objects including a media playback object used to present visual content; and
serving the user experience workflow to a user device based on a request, from the user device, for the destination identifier.
10. The non-transitory computer readable medium of claim 9 , wherein the user experience workflow is generated using a graphical user interface of workflow editor software including a canvas and a list of objects for selective arrangement within the canvas.
11. The non-transitory computer readable medium of claim 9 , wherein the user experience workflow is generated using a template.
12. The non-transitory computer readable medium of claim 9 , wherein an object of the objects is extensible using one or both scripting instructions or an application programming interface call.
13. The non-transitory computer readable medium of claim 9 , wherein the media playback object is configured based on one or more of a media content item to present, text to present in connection with the media content item, and an action to be performed after the media content item is presented.
14. A system, comprising:
one or more memories; and
one or more processors configured to execute instructions stored in the one or more memories to:
bind, to a destination identifier, a user experience workflow configured to include one or more paths for traversing objects including a media playback object used to present visual content; and
serve the user experience workflow to a user device based on a request, from the user device, for the destination identifier.
15. The system of claim 14 , wherein the objects correspond to multiple object types and configurations to apply to ones of the objects are based on respective object types of the ones of the objects.
16. The system of claim 14 , wherein the objects are selected from a list of object types including two or more of queue objects, IVR menu objects, input objects, forwarding objects, media playback objects, voicemail objects, condition objects, or messaging objects.
17. The system of claim 14 , wherein visual content presented in connection with the media playback object is configured during a generation of the user experience workflow for use with the destination identifier.
18. The system of claim 14 , wherein the destination identifier corresponds to a telephone number and the media playback object causes a presentation of audio media at the user device.
19. The system of claim 14 , wherein the destination identifier corresponds to a web address and the media playback object causes a presentation of visual media at the user device.
20. The system of claim 14 , wherein a subset of the objects associated with a first path of the one or more paths is inaccessible at a second path of the one or more paths.