System, method, and apparatus for initiating outbound communications from a user device
View Patent ↗Provided are systems, methods, and apparatuses initiating outbound communications. The system may include at least one processor of a telecommunications device comprising a display and a communication application, the at least one processor programmed or configured to: receive, with the communication application, a communication request comprising a number, the communication request initiated by a user of the telecommunications device, determine whether to automatically initiate a communication to the number based on recipient data associated with the number, in response to determining to not automatically initiate the communication to the number, prompt the user, on the display of the telecommunications device, with a selectable option configured to initiate the communication to the number upon selection, and in response to determining to automatically initiate the communication to the number, automatically initiate the communication to the number upon selection.
1 . A system comprising at least one processor of a user device comprising a display and a dialer application, the at least one processor configured to:
receive recipient data from rich call data from inbound communications to the user device, the recipient data comprising a verified entity;
store the recipient data by the dialer application;
receive a request through the dialer application identifying a recipient party;
retrieve, based on the recipient party, at least a portion of the recipient data stored by the dialer application;
display the retrieved recipient data on the display of the user device;
manage communication consent with the verified entity based on input received through the user device, the communication consent comprising at least one of the following: permission to receive communications from the recipient party via specified communication channels, revoke permission for the recipient party to contact the user via specified communication channels, or any combination thereof; and
transmit, by the dialer application, the communication consent to the verified entity.
2 . The system of claim 1 , wherein the communication consent is transmitted by the dialer application to the entity through at least a channel specified in a registry to at least one of: the verified entity, an entity that attested to the an identity of the registered entity and/or signed the rich call data, a voice carrier associated with a user, a voice carrier associated with the registered entity, a messaging carrier associated with the user, a messaging connectivity partner associated with the registered entity, an attorney, or any combination thereof.
3 . The system of claim 1 , wherein the recipient data is stored in a call history of the dialer application.
4 . The system of claim 1 , wherein the recipient data is stored in a registered contacts database or contact history on the user device by the dialer application.
5 . The system of claim 1 , wherein the recipient data comprises an image, and wherein displaying the retrieved recipient data on the display of the user device comprises displaying the image during an outbound communication to the verified entity.
6 . The system of claim 1 , wherein the recipient data comprises at least one of an image or a name, and wherein displaying the retrieved recipient data on the display of the user device comprises displaying the image and/or the name such that selecting at least one of the image or the name causes display of an interface configured to receive the input used to manage the communication consent.
7 . The system of claim 1 , wherein the recipient data is stored in response to affirming an authenticity of the inbound communications by an information identity source.
8 . The system of claim 1 , wherein the recipient data comprises at least one of the following: an entity name, a website URL, an electronic card, an email address, a location, a title, a role, a department, a category, a note, a reason for a communication, a source of identity verification/attestation, or any combination thereof.
9 . The system of claim 1 , wherein the at least one processor is further configured to display at least one of the following to a user on the user device based on the recipient data: an authenticated identity verification, and unknown identity icon, a warning icon, a source of the authenticated identity verification or any combination thereof.
10 . The system of claim 1 , wherein the at least one processor is further configured to receive additional recipient data about the recipient party, the additional recipient data comprised of at least one of a reputation score, a fraud score, a SPAM score, a call and/or text message history of a caller, a call and/or text message history of a callee, carrier analytics, or crowd-sourced data.
11 . The system of claim 1 , wherein the at least one processor is further confirmed to manage communication options based on input received through the user device, the communication options comprising at least one of the following: opt in and/or out of all communications or communications via a specific channel, file a complaint, revoke previously granted communications permissions, review a history of expressed permissions and preferences, request a call now with the verified entity, schedule a call with the entity, access a registered chatbot, access a registered messaging communications number, access a registered messaging moniker, access a registered social media handle, or any combination thereof.
12 . The system of claim 11 , wherein a complaint is transmitted by the dialer application through a complaint channel specified in a registry to at least one of: a registered entity, the entity that attested to the verified identity of the registered entity and/or signed the rich call data, a voice carrier associated with the user, a messaging carrier associated with the user, a messaging connectivity partner associated with the registered entity, an attorney, or any combination thereof.
13 . A method comprising:
receiving, with at least one processor of a user device comprising a display and a dialer application, recipient data from rich call data from inbound communications to the user device, the recipient data comprising a verified entity;
storing, by the dialer application, the recipient data;
receiving, by the dialer application, a request identifying a recipient party;
retrieving, based on the recipient data, at least a portion of the recipient data stored by the dialer application of the user device;
displaying the retrieved recipient data on the display of the user device;
managing communication consent with the verified entity based on input received through the user device, the communication consent comprising at least one of the following: permission to receive communications from the recipient party via specified communication channels, revoke permission for the recipient party to contact the user via specified communication channels, or any combination thereof; and
transmitting, by the dialer application, the communication consent to the verified entity.
14 . The method of claim 13 , wherein the communication consent is transmitted by the dialer application to the verified entity through at least a channel specified in a registry to at least one of: the verified entity, an entity that attested to an identity of the registered entity and/or signed the rich call data, a voice carrier associated with a user, a voice carrier associated with the registered entity, a messaging carrier associated with the user, a messaging connectivity partner associated with the registered entity, an attorney, or any combination thereof.
15 . The method of claim 13 , wherein the recipient data is stored in a call history of the dialer application.
16 . The method of claim 13 , wherein the recipient data is stored in a registered contacts database or contact history on the user device by the dialer application.
17 . The method of claim 13 , wherein the recipient data comprises an image, and wherein displaying the retrieved recipient data on the display of the user device comprises displaying the image during an outbound communication to the verified entity.
18 . The method of claim 13 , wherein the recipient data comprises at least one of an image or a name, and wherein displaying the retrieved recipient data on the display of the user device comprises displaying the image and/or the name such that selecting at least one of the image or the name causes display of an interface configured to receive the input used to manage the communication consent.
19 . The method of claim 13 , wherein the recipient data is stored in response to affirming an authenticity of the inbound communication by an information identity source.
20 . The method of claim 13 , wherein the recipient data comprises at least one of the following: an entity name, a website URL, an electronic card, an email address, a location, a title, a role, a department, a category, a note, a reason for a communication, a source of identity verification/attestation, or any combination thereof.
21 . The method of claim 13 , further comprising: displaying at least one of the following to a user on the user device based on the recipient data: an authenticated identity verification, and unknown identity icon, a warning icon, a source of the authenticated identity verification or any combination thereof.
22 . The method of claim 13 , further comprising: receiving additional recipient data about the recipient party, the additional recipient data comprised of at least one of a reputation score, a fraud score, a SPAM score, a call and/or text message history of a caller, a call and/or text message history of a callee, carrier analytics, or crowd-sourced data.
23 . The method of claim 13 , wherein the at least one processor is further confirmed to manage communication options based on input received through the user device, the communication options comprising at least one of the following: opt in and/or out of all communications or communications via a specific channel, file a complaint, revoke previously granted communications permissions, review a history of expressed permissions and preferences, request a call now with the verified entity, schedule a call with the entity, access a registered chatbot, access a registered messaging communications number, access a registered messaging moniker, access a registered social media handle, or any combination thereof.
24 . The method of claim 22 , wherein a complaint is transmitted by the dialer application through a complaint channel specified in a registry to at least one of: a registered entity, the verified entity that attested to the identity of the registered entity and/or signed the rich call data, a voice carrier associated with the user, a messaging carrier associated with a user, a messaging connectivity partner associated with the registered entity, an attorney, or any combination thereof.
25 . A computer program product comprising at least one non-transitory computer-readable medium including program instructions that, when executed by at least one processor of a user device comprising a display and a dialer application, cause the at least one processor to:
receive recipient data from rich call data from inbound communications to the user device, the recipient data comprising a verified entity;
store the recipient data by the dialer application;
receive a request through the dialer application identifying a recipient party;
retrieve, based on the recipient party, at least a portion of the recipient data stored by the dialer application of the user device;
manage communication consent with the verified entity based on input received through the user device, the communication consent comprising at least one of the following: permission to receive communications from the recipient party via specified communication channels, revoke permission for the recipient party to contact the user via specified communication channels, or any combination thereof; and
transmit, by the dialer application, the communication consent to the verified entity.