CPC Class H04M

A token-based billing model for delivering server-side rendered applications to remote users. A token represents a right to access a server-side rendered application. Each remote user is associated with one or more tokens. When a given token expires, the set of tokens associated with a user is decremented. The rate at which tokens expire are modulated based on aggregate load across the resources of the server-side rendered application provider, as well as the individual loads attributable to each of the users.

A software as a service (SaaS) platform sends, to an end user device, a message of a messaging conversation between the end user device and a first client device associated with a first user account of the SaaS platform. The message is associated with a first telephone number provisioned by the SaaS platform. The messaging conversation is associated with a messaging conversation identifier. The end user device is associated with a second telephone number. The first client device is associated with a third telephone number. a first request to place a voice call is received, via a first application programming interface (API) call from the first client device, based on the messaging conversation identifier. Responsive to receiving the first request, the voice call to the second telephone number is placed. The voice call is associated with the first telephone number provisioned by the SaaS platform.

A method includes receiving a first request associated with a first user account and comprising content of a first message, and a second request associated with a second user account and comprising content of a second message, generating a first list of routing options for delivering the first message to a first plurality of destination endpoints, and a second list of routing options for delivering the second message to a second plurality of destination endpoints, determining a first optimal routing option for delivering the first message, determining, a second optimal routing option for delivering the second message, causing one or more versions of the first message to be transmitted to the first plurality of destination endpoints using the first optimal routing option, and causing one or more versions of the second message to be transmitted to the second plurality of destination endpoints using the second optimal routing option.