Prosecution Insights
Last updated: October 01, 2026
Application No. 19/216,102

INTEGRATING AND MANAGING SOCIAL NETWORKING INFORMATION IN AN ON-DEMAND DATABASE SYSTEM

Non-Final OA §DP
Filed
May 22, 2025
Priority
Oct 30, 2009 — provisional 61/256,861 +8 more
Examiner
DALENCOURT, YVES
Art Unit
Tech Center
Assignee
Salesforce Inc.
OA Round
1 (Non-Final)
84%
Grant Probability
Favorable
1-2
OA Rounds
1y 6m
Est. Remaining
79%
With Interview

Examiner Intelligence

Grants 84% — above average
84%
Career Allowance Rate
778 granted / 924 resolved
+24.2% vs TC avg
Minimal -6% lift
Without
With
+-5.5%
Interview Lift
resolved cases with interview
Typical timeline
2y 10m
Avg Prosecution
19 currently pending
Career history
938
Total Applications
across all art units

Statute-Specific Performance

§101
9.4%
-30.6% vs TC avg
§103
39.9%
-0.1% vs TC avg
§102
29.4%
-10.6% vs TC avg
§112
13.8%
-26.2% vs TC avg
Black line = Tech Center average estimate • Based on career data from 924 resolved cases

Office Action

§DP
Notice of Pre-AIA or AIA Status The present application is being examined under the pre-AIA first to invent provisions. This office action is responsive to communication filed on 04/29/2025. Double Patenting The nonstatutory double patenting rejection is based on a judicially created doctrine grounded in public policy (a policy reflected in the statute) so as to prevent the unjustified or improper timewise extension of the “right to exclude” granted by a patent and to prevent possible harassment by multiple assignees. A nonstatutory double patenting rejection is appropriate where the conflicting claims are not identical, but at least one examined application claim is not patentably distinct from the reference claim(s) because the examined application claim is either anticipated by, or would have been obvious over, the reference claim(s). See, e.g., In re Berg, 140 F.3d 1428, 46 USPQ2d 1226 (Fed. Cir. 1998); In re Goodman, 11 F.3d 1046, 29 USPQ2d 2010 (Fed. Cir. 1993); In re Longi, 759 F.2d 887, 225 USPQ 645 (Fed. Cir. 1985); In re Van Ornum, 686 F.2d 937, 214 USPQ 761 (CCPA 1982); In re Vogel, 422 F.2d 438, 164 USPQ 619 (CCPA 1970); In re Thorington, 418 F.2d 528, 163 USPQ 644 (CCPA 1969). A timely filed terminal disclaimer in compliance with 37 CFR 1.321(c) or 1.321(d) may be used to overcome an actual or provisional rejection based on nonstatutory double patenting provided the reference application or patent either is shown to be commonly owned with the examined application, or claims an invention made as a result of activities undertaken within the scope of a joint research agreement. See MPEP § 717.02 for applications subject to examination under the first inventor to file provisions of the AIA as explained in MPEP § 2159. See MPEP § 2146 et seq. for applications not subject to examination under the first inventor to file provisions of the AIA . A terminal disclaimer must be signed in compliance with 37 CFR 1.321(b). The filing of a terminal disclaimer by itself is not a complete reply to a nonstatutory double patenting (NSDP) rejection. A complete reply requires that the terminal disclaimer be accompanied by a reply requesting reconsideration of the prior Office action. Even where the NSDP rejection is provisional the reply must be complete. See MPEP § 804, subsection I.B.1. For a reply to a non-final Office action, see 37 CFR 1.111(a). For a reply to final Office action, see 37 CFR 1.113(c). A request for reconsideration while not provided for in 37 CFR 1.113(c) may be filed after final for consideration. See MPEP §§ 706.07(e) and 714.13. The USPTO Internet website contains terminal disclaimer forms which may be used. Please visit www.uspto.gov/patent/patents-forms. The actual filing date of the application in which the form is filed determines what form (e.g., PTO/SB/25, PTO/SB/26, PTO/AIA /25, or PTO/AIA /26) should be used. A web-based eTerminal Disclaimer may be filled out completely online using web-screens. An eTerminal Disclaimer that meets all requirements is auto-processed and approved immediately upon submission. For more information about eTerminal Disclaimers, refer to www.uspto.gov/patents/apply/applying-online/eterminal-disclaimer. Claims 21 - 40 of US Application No. 19/216,102 are rejected on the ground of nonstatutory obviousness-type double patenting as being unpatentable over claims 1 - 20 of U.S. Patent No. 12,354,113. Although the conflicting claims are not identical, they are not patentably distinct from each other because claims 1 - 20 of the U.S. Patent mentioned above, contain every element of claims 21 - 40 of the instant application and thus anticipate the claim of the instant application. Claims 21 - 40 of the instant application are therefore not patently distinct from claims 1 - 20 of the U.S. Patent No. 12,354,113 and as such are unpatentable over obvious-type double patenting. "A later patent claim is not patentably distinct from an earlier patent claim if the later claim is obvious over, or anticipated by, the earlier claim. In re Longi, 759 F.2d at 896, 225 USPQ at 651 (affirming a holding of obviousness-type double patenting because the claims at issue were obvious over claims in four prior art patents); In re Berg, 140 F.3d at 1437, 46 USPQ2d at 1233 (Fed. Cir. 1998) (affirming a holding of obviousness-type double patenting where a patent application claim to a genus is anticipated by a patent claim to a species within that genus). " ELI LILLY AND COMPANY v BARR LABORATORIES, INC., United States Court of Appeals for the Federal Circuit, ON PETITION FOR REHEARING EN BANC (DECIDED: May 30, 2001). Please see the table below: US Application No. 19/216,102 US Patent Number 12,354,113 1. A system comprising: a server system comprising one or more processors, the server system configurable to cause: displaying, in a user interface (UI) on a display device, data of an account record stored in a customer relationship management (CRM) database system; identifying one or more social media posts displayable in the UI; communicating, responsive to the identifying, the one or more social media posts to the CRM database system; assigning, in the CRM database system, one or more social media users associated with the one or more social media posts, including mapping the one or more social media users to a CRM record in the CRM database system; providing an interface element in the UI for interacting with the one or more social media users; and tracking, using the CRM record in the CRM database system, interactions from the interface element. 22. (New) The system of claim 21, wherein the interactions include a response to a post in an external social media network. 23. (New) The system of claim 22, wherein the CRM record includes data from the response. 24. (New) The system of claim 21, wherein the interface element is provided at least in part by the CRM database system. 25. (New) The system of claim 21, wherein the account record is the CRM record. 26. (New) The system of claim 21, wherein the mapping of the one or more social media users to the CRM record in the CRM database system includes matching the one or more social media users to a CRM contact stored in the CRM database system. 27. (New) The system of claim 21, the server system further configurable to cause: triggering one or more follow-up actions, including creating a service request in the CRM database system, the one or more follow-up actions being trackable using the CRM database system. 28. (New) A non-transitory computer-readable medium storing computer program instructions capable of being executed by one or more processors, the instructions configurable to cause: displaying, in a user interface (UI) on a display device, data of an account record stored in a customer relationship management (CRM) database system; identifying one or more social media posts displayable in the UI; communicating, responsive to the identifying, the one or more social media posts to the CRM database system; assigning, in the CRM database system, one or more social media users associated with the one or more social media posts, including mapping the one or more social media users to a CRM record in the CRM database system; providing an interface element in the UI for interacting with the one or more social media users; and tracking, using the CRM record in the CRM database system, interactions from the interface element. 29. (New) The non-transitory computer-readable medium of claim 28, wherein the interactions include a response to a post in an external social media network. 30. (New) The non-transitory computer-readable medium of claim 29, wherein the CRM record includes data from the response. 31. (New) The non-transitory computer-readable medium of claim 28, wherein the interface element is provided at least in part by the CRM database system. 32. (New) The non-transitory computer-readable medium of claim 28, wherein the account record is the CRM record. 33. (New) The non-transitory computer-readable medium of claim 28, wherein the mapping of the one or more social media users to the CRM record in the CRM database system includes matching the one or more social media users to a CRM contact stored in the CRM database system. 34. (New) The non-transitory computer-readable medium of claim 28, the instructions further configurable to cause: triggering one or more follow-up actions, including creating a service request in the CRM database system, the one or more follow-up actions being trackable using the CRM database system. 35. (New) A computer-implemented method comprising: displaying, in a user interface (UI) on a display device, data of an account record stored in a customer relationship management (CRM) database system; identifying one or more social media posts displayable in the UI; communicating, responsive to the identifying, the one or more social media posts to the CRM database system; assigning, in the CRM database system, one or more social media users associated with the one or more social media posts, including mapping the one or more social media users to a CRM record in the CRM database system; providing an interface element in the UI for interacting with the one or more social media users; and tracking, using the CRM record in the CRM database system, interactions from the interface element. 36. (New) The computer-implemented method of claim 35, wherein the interactions include a response to a post in an external social media network. 37. (New) The computer-implemented method of claim 36, wherein the CRM record includes data from the response. 38. (New) The computer-implemented method of claim 35, wherein the interface element is provided at least in part by the CRM database system. 39. (New) The computer-implemented method of claim 35, wherein the account record is the CRM record. 40. (New) The computer-implemented method of claim 35, wherein the mapping of the one or more social media users to the CRM record in the CRM database system includes matching the one or more social media users to a CRM contact stored in the CRM database system. 1. A system comprising: a server system comprising one or more processors, the server system configurable to cause: displaying an account of a customer relationship management (CRM) database in an area of a user interface (UI) on a display device; identifying one or more social media posts displayable in the UI; assigning, responsive to input via the UI, one or more social media users associated with the one or more social media posts to the account, including mapping the one or more social media users to the account in the CRM database; displaying information indicating the assignment of the one or more social media users to the account in an account overview of the UI; and tracking the account in the CRM database in association with the one or more social media users. 2. The system of claim 1, the server system further configurable to cause: retrieving the one or more social media posts from one or more defined social media channels. 3. The system of claim 2, wherein the one or more social media posts are retrieved using social media integration provided by a web client. 4. The system of claim 1, the server system further configurable to cause: triggering one or more follow-up business actions, including creating a service request in the CRM database, the one or more follow-up business actions being trackable in association with a social media user using an interaction record. 5. The system of claim 1, the server system further configurable to cause: capturing social media user data from one or more social media posts using the assignment of the one or more social media users to the account. 6. The system of claim 1, the server system further configurable to cause: assigning the one or more social media users to one or more of a group or a contact in one or more of the CRM database or the UI. 7. The system of claim 1, the server system further configurable to cause: processing an incoming customer service communication from one of a plurality of channels including one or more of: phone, e-mail, chat, messaging, portal, or social media. 15. A computer-implemented method comprising: displaying an account of a customer relationship management (CRM) database in an area of a user interface (UI) on a display device; identifying one or more social media posts displayable in the UI; assigning, responsive to input via the UI, one or more social media users associated with the one or more social media posts to the account, including mapping the one or more social media users to the account in the CRM database; displaying information indicating the assignment of the one or more social media users to the account in an account overview of the UI; and tracking the account in the CRM database in association with the one or more social media users. 16. The computer-implemented method of claim 15, further comprising: retrieving the one or more social media posts from one or more defined social media channels. 17. The computer-implemented method of claim 16, wherein the one or more social media posts are retrieved using social media integration provided by a web client. 18. The computer-implemented method of claim 15, further comprising: triggering one or more follow-up business actions, including creating a service request in the CRM database, the one or more follow-up business actions being trackable in association with a social media user using an interaction record. 19. The computer-implemented method of claim 15, further comprising: capturing social media user data from one or more social media posts using the assignment of the one or more social media users to the account. 20. The computer-implemented method of claim 15, further comprising: assigning the one or more social media users to one or more of a group or a contact in one or more of the CRM database or the UI. Contact Information Any inquiry concerning this communication or earlier communications from the examiner should be directed to YVES DALENCOURT whose telephone number is (571)272-3998. The examiner can normally be reached M-F 8AM-5:30PM. Examiner interviews are available via telephone, in-person, and video conferencing using a USPTO supplied web-based collaboration tool. To schedule an interview, applicant is encouraged to use the USPTO Automated Interview Request (AIR) at http://www.uspto.gov/interviewpractice. If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Ario Etienne can be reached at 571-272-4001. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300. Information regarding the status of published or unpublished applications may be obtained from Patent Center. Unpublished application information in Patent Center is available to registered users. To file and manage patent submissions in Patent Center, visit: https://patentcenter.uspto.gov. Visit https://www.uspto.gov/patents/apply/patent-center for more information about Patent Center and https://www.uspto.gov/patents/docx for information about filing in DOCX format. For additional questions, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000. /YVES DALENCOURT/Primary Examiner, Art Unit 2457
Read full office action

Prosecution Timeline

May 22, 2025
Application Filed
Aug 26, 2026
Non-Final Rejection mailed — §DP (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12739149
PROGRAMMING STATIC MULTICAST ROUTES INLOAD-BALANCED NETWORKS
1y 11m to grant Granted Sep 15, 2026
Patent 12732558
INTELLIGENT PLANE NETWORK FUNCTIONS FOR GENERATING AND SHARING DATA ACROSS APPLICATIONS AND NETWORK FUNCTIONS
2y 2m to grant Granted Sep 08, 2026
Patent 12719946
CHUNKED FILE TRANSFER AMONG MOBILE PEER DEVICES
2y 0m to grant Granted Aug 25, 2026
Patent 12712808
SYSTEM AND METHOD FOR NETWORK EVENT DATA STREAMING AND PROCESSING VIA MODULAR NETWORK EVENT DATA ARCHITECTURE
2y 3m to grant Granted Aug 18, 2026
Patent 12712943
DATA PROCESSING SYSTEM AND METHOD AND DEVICE
2y 2m to grant Granted Aug 18, 2026
Study what changed to get past this examiner. Based on 5 most recent grants.

Strategy Recommendation AI-generated — please review before filing

Get a prosecution strategy drawn from examiner precedents, rejection analysis, and claim mapping.
Typically takes 5-10 seconds — AI-generated, attorney review required before filing

Prosecution Projections

1-2
Expected OA Rounds
84%
Grant Probability
79%
With Interview (-5.5%)
2y 10m (~1y 6m remaining)
Median Time to Grant
Low
PTA Risk
Based on 924 resolved cases by this examiner. Grant probability derived from career allowance rate.

Sign in with your work email

Enter your email to receive a magic link. No password needed.

Personal email addresses (Gmail, Yahoo, etc.) are not accepted.

Free tier: 3 strategy analyses per month