Client Control Via Third Party Application

A system, comprising:

• a private branch exchange (PBX) server comprising a non-transitory computer-readable medium comprising stored instructions;
• and
• a server comprising a non-transitory computer-readable medium comprising stored instructions configured to:
• receive a control command from a first client associated with a third party application configured to run on a software platform, the control command indicating a function for a second client to perform;
• generate an event socket command based on the control command;
• and
• transmit the event socket command to the PBX server;
• the PBX server configured to:
• determine a binding status from a database that indicates an existence of a wireless binding between the first client and the second client, wherein the first client and the second client share a user account;
• and
• transmit the event socket command to the second client to execute the function based on the binding status that indicates the existence of the wireless binding between the first client and the second client, wherein the wireless binding between the first client and the second client is based on a multi-step confirmation received from the first client and the second client.

A non-transitory computer-readable medium comprising instructions stored on a memory, that when executed by a processor, cause the processor to perform operations comprising:

• receiving a control command from a first client associated with a third party application configured to run on a software platform, the control command indicating a function for a second client to perform;
• generating an event socket command based on the control command;
• transmitting the event socket command to a private branch exchange (PBX) server of the software platform;
• determining a binding status from a database indicating an existence of a wireless binding between the first client and the second client, wherein the first client and the second client share a user account;
• and
• transmitting the event socket command to the second client to execute the function based on the binding status indicating the existence of the wireless binding between the first client and the second client, wherein the wireless binding between the first client and the second client is based on a multi-step confirmation received from the first client and the second client.