US 12,483,864 B2
Systems and methods for personalizing messages based on a recipient relationship
Kuppappa Dandappa Harijan, Bangalore (IN); and Madhusudhan Srinivasan, Bangalore (IN)
Assigned to Adeia Guides Inc., San Jose, CA (US)
Filed by Adeia Guides Inc., San Jose, CA (US)
Filed on May 31, 2024, as Appl. No. 18/680,205.
Application 18/680,205 is a continuation of application No. 18/223,650, filed on Jul. 19, 2023, granted, now 12,028,783.
Application 18/223,650 is a continuation of application No. 17/833,134, filed on Jun. 6, 2022, granted, now 11,758,371, issued on Sep. 12, 2023.
Application 17/833,134 is a continuation of application No. 17/002,178, filed on Aug. 25, 2020, granted, now 11,395,109, issued on Jul. 19, 2022.
Application 17/002,178 is a continuation of application No. 16/370,318, filed on Mar. 29, 2019, granted, now 10,791,433, issued on Sep. 29, 2020.
Prior Publication US 2024/0414506 A1, Dec. 12, 2024
This patent is subject to a terminal disclaimer.
Int. Cl. H04W 4/12 (2009.01)
CPC H04W 4/12 (2013.01) 20 Claims
OG exemplary drawing
 
1. A method for personalizing messages based on recipient relationships, the method comprising:
storing, in a database for a sender account, relationship information for each of a plurality of potential recipients, wherein the database stores for each respective potential recipient at least one contact category of a plurality of contact categories that the respective potential recipient belongs to, and wherein the storing the relationship information comprises storing the at least one contact category of the respective potential recipient that is obtained from information communicated via a social network associated with at least one of the respective potential recipient or the sender account;
receiving at least one request from a device associated with the sender account to send a first message to a first recipient of the plurality of potential recipients and a second message to a second recipient of the plurality of potential recipients;
processing a first request of the at least one request to send the first message to the first recipient by:
retrieving, by a message constructor, relationship information for the first recipient from the database which identifies that the first recipient belongs to a first contact category of the plurality of contact categories;
accessing, by the message constructor, a first message template based on the first contact category;
generating, by the message constructor, the first message by applying a first modification based on the first message template; and
transmitting over a network the first message to the first recipient; and
processing a second request of the at least one request to send the second message to the second recipient by:
retrieving, by the message constructor, relationship information for the second recipient from the database which identifies that the second recipient belongs to a second contact category of the plurality of contact categories;
accessing, by the message constructor, a second message template based on the second contact category;
generating, by the message constructor, the second message by applying a second modification based on the second message template; and
transmitting over the network the second message to the second recipient.