Abstract: A first request to access a messaging conversation management service that permits the first user account to view and transfer text message conversations between other user accounts of multiple user accounts and multiple recipient devices is received by a communication services platform via a first application programming interface (API) call from a first client device associated with a first user account. Responsive to receiving the first request, whether the first user account is authorized to access the messaging conversation management service is determined. Responsive to determining that the first user account is authorized to access the messaging conversation management service, a first indication of the text message conversations between the other user accounts of the multiple user accounts and the multiple recipient devices is sent to the first client device for display at the first client device.

Abstract: 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.

Abstract: A first request to identify, among a plurality of user accounts, a subset of user accounts that are available to receive a transfer of a messaging conversation with a recipient device is received via a first application programming interface (API) call from a first client device associated with a first user account. A first response identifying the subset of user accounts that are available to receive the transfer of the messaging conversation is sent to the first client device responsive to receiving the first request. A second request to transfer the messaging conversation to a second user account identified among the subset of user accounts is received via a second API call from the first client device. The messaging conversation is transferred to the second user account to facilitate a continuation of the messaging conversation with the recipient device responsive to receiving the second request.

Abstract: 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.

Abstract: A first request to place a voice call is received via a first application programming interface (API) call from a first client device associated with a first user account of a communication services platform. The first request includes a messaging conversation identifier that identifies a messaging conversation. Messaging conversation data associated with the messaging conversation identifier and stored in a data store is obtained. The messaging conversation data identifies participants of the messaging conversation. A recipient of the voice call is identifying, among participants of the messaging conversation, based on filter criteria. The voice call is placed to a telephone number of an end user device associated with the recipient.

Abstract: A first request to place a voice call is received via a first application programming interface (API) call from a first client device associated with a first user account of a communication services platform. The first request includes a messaging conversation identifier that identifies a messaging conversation. Messaging conversation data associated with the messaging conversation identifier and stored in a data store is obtained. The messaging conversation data identifies participants of the messaging conversation. A recipient of the voice call is identifying, among participants of the messaging conversation, based on filter criteria. The voice call is placed to a telephone number of an end user device associated with the recipient.

Abstract: A first request to identify, among a plurality of user accounts, a subset of user accounts that are available to receive a transfer of a messaging conversation with a recipient device is received via a first application programming interface (API) call from a first client device associated with a first user account. A first response identifying the subset of user accounts that are available to receive the transfer of the messaging conversation is sent to the first client device responsive to receiving the first request. A second request to transfer the messaging conversation to a second user account identified among the subset of user accounts is received via a second API call from the first client device. The messaging conversation is transferred to the second user account to facilitate a continuation of the messaging conversation with the recipient device responsive to receiving the second request.