In one embodiment, the method of processing telephony sessions includes: communicating with an application server using an application layer protocol; processing telephony instructions with a call router; and creating call router resources accessible through a call router Application Programming Interface (API). In another embodiment, the system for processing telephony sessions includes: a call router, a URI for an application server, a telephony instruction executed by the call router, and a call router API resource.

In a preferred embodiment, the method of caching media used in a telephony application includes: receiving a media request; sending the media request to a media layer using HTTP; the a media layer performing the steps of checking in a cache for the media resource; processing the media request within a media processing server; and storing the processed media in the cache as a telephony compatible resource specified by a persistent address. The system of the preferred embodiment includes a call router and a media layer composed of a cache and media processing server.

In one embodiment, the method of processing telephony sessions includes: communicating with an application server using an application layer protocol; processing telephony instructions with a call router; and creating call router resources accessible through a call router Application Programming Interface (API). In another embodiment, the system for processing telephony sessions includes: a call router, a URI for an application server, a telephony instruction executed by the call router, and a call router API resource.

A redirection bridge device, RBD (10, 20), comprising: —an API interface (300) comprising an API input (301), arranged capable of receiving a request (300A) from an application (APP) (30), arranged located on a user device (1100) associated with a user (1000), for the purposes of requesting metadata, said metadata being specific to at least one contact option (2100) arranged in association with at least one Enterprise (2000), a metadata store (310), for storing metadata specific to the at least one Enterprise (2000), and arranged to provide metadata to the API interface (300) in response to the request (300A), and, a Communications Manager (320), arranged in co-operation with the API interface (300) and the at least one contact option (2100), for facilitating contact between the user device (1100) and the at least one contact option (2100). A redirection bridge system, a communication system, a method of redirection bridging and use of a user interface and software product for implementation of the redirection bridging method.

A system and method to manage data associated with a merchant system to provide in response to a search query from an end user system. The system and method generate a custom entity type including one or more fields comprising first data corresponding to the merchant system. An update to the first data of the custom entity type can be received and an updated custom entity type is generated. The updated custom entity type is distributed to multiple business listing provider systems configured to provide search results associated with the merchant system in response to a search query from an end user system. The system and method can also generate a search experience interface including multiple input fields. The search experience interface is displayed to an end user to receive search terms via the first input and the second input field in response to a single search action.

In one embodiment, the method of processing telephony sessions includes: communicating with an application server using an application layer protocol; processing telephony instructions with a call router; and creating call router resources accessible through a call router Application Programming Interface (API). In another embodiment, the system for processing telephony sessions includes: a call router, a URI for an application server, a telephony instruction executed by the call router, and a call router API resource.

In a preferred embodiment, the method of caching media used in a telephony application includes: receiving a media request; sending the media request to a media layer using HTTP; the a media layer performing the steps of checking in a cache for the media resource; processing the media request within a media processing server; and storing the processed media in the cache as a telephony compatible resource specified by a persistent address. The system of the preferred embodiment includes a call router and a media layer composed of a cache and media processing server.

A system and method for customizing communication processing within a communication platform that includes configuring a service handler, which comprises of at least setting execution code of the service handler; setting an association between the service handler and a communication event of the communication platform; detecting the occurrence of the communication event of a communication facilitated through the communication platform; invoking the service handler in response to the event, which comprises: executing the execution code in a serverless execution environment and generating a service handler response; and augmenting the communication in accordance with the service handler response.

In one embodiment, the method of processing telephony sessions includes: communicating with an application server using an application layer protocol; processing telephony instructions with a call router; and creating call router resources accessible through a call router Application Programming Interface (API). In another embodiment, the system for processing telephony sessions includes: a call router, a URI for an application server, a telephony instruction executed by the call router, and a call router API resource.

A method includes receiving a first request associated with a first user account and comprising content of a first message and a first plurality of destination endpoints, and a second request associated with a second user account and comprising content of a second message and a second plurality of destination endpoints to receive the second message, generating a first list of routing options for delivering the first message to the first plurality of destination endpoints, and a second list of routing options for delivering the second message to the second plurality of destination endpoints, generating, based on the first list of routing options, one or more versions of the first message for delivery to the first plurality of endpoints, and generating, based on the second list of routing options, one or more versions of the second message for delivery to the second plurality of endpoints. The method further includes causing the one or more versions of the first message to be transmitted to the first plurality of destination endpoints, and the one or more versions of the second message to be transmitted to the second plurality of destination endpoints, and providing first access rate statistics collected by tracking access to the one or more versions of the first message by the first plurality of destination endpoints, and second access rate statistics collected by tracking access to the one or more versions of the second message by the second plurality of destination endpoints.