IP Library Granted Patent US 12,273,305
Granted Patent B2
US 12,273,305 · App. 18/244,665 · Granted Apr 8, 2025

System and method of managing channel agnostic messages in a multi-client customer platform

Inventors: Vijay Vadlamani (Cambridge, MA); Antoinette Hocbo (Cambridge, MA); Harminder Singh (Reading, MA); Nathaniel Dempkowski (Cambridge, MA)
Assignee: HubSpot, Inc.
H04L51/046H04L51/02H04L51/21
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,273,305
App. No.
18/244,665
Filed
Sep 11, 2023
Granted
Apr 8, 2025
Kind
B2
Art Unit
2457
USPC
709/206
Abstract

Techniques are provided for implementing omnichannel messaging. A set of application programming interfaces are utilized to create a set of channels connected to services of a customer platform. A channel is defined to specify how the channel is to interact with a service of the customer platform. Flows are formatted and defined for sending and receiving messages across the set of channels based upon native messaging experiences provided by the services of the customer platform. Flows are formatted and defined for viewing and interacting with the messages based upon a set of contexts for viewing and interacting with the messages through the services. The flows are executed for processing messages.

Claims (54)

1. A method comprising:

utilizing an application programming interface to create a channel connected to a service of a customer platform, wherein the channel is defined to specify how the channel is to interact with the service;

integrating a channel framework with the customer platform, wherein the channel framework is defined with levels including a first level for building and connecting to channels, a second level for constructing functions of channels in a workspace, and a third level for enabling workspace features within the channel framework;

defining the channel framework to include at least one of a fourth level for integrating the channel framework into a customer relationship management (CRM) system or a fifth level for enabling platform tools within the channel framework;

defining first flows for sending and receiving messages across the channel according to messaging functionality supported by the service;

defining second flows for viewing and interacting with the messages based upon context for viewing and interacting with the messages through the service; and

executing, utilizing the levels of the channel framework, the first flows and the second flows for processing the messages.

2. The method of claim 1 , wherein the utilizing comprises:

utilizing a channel integration application programming interface to define and set a channel configuration for the channel.

3. The method of claim 1 , comprising:

utilizing a user experience framework to discover and connect the channel to the service.

4. The method of claim 1 , comprising:

utilizing a data framework to capture and store user accounts for the channel, wherein a user account defines a channel type, user account specific rules, and user account specific settings.

5. The method of claim 1 , comprising:

in response to receiving a selection of a user account for the channel, syncing and sending messages through a team workspace of a team workspace service during channel connection of the channel.

6. The method of claim 1 , comprising:

integrating the channel with workflows associated with a ticket automation service.

7. The method of claim 1 , comprising:

utilizing a data framework to facilitate message composition and channel and recipient searching.

8. The method of claim 1 , comprising:

enabling user to move from utilizing the channel in a context to utilizing a different channel in the context.

9. The method of claim 1 , comprising:

utilizing a customer relationship management service of the customer platform for conversational automation and reporting associated with messages using the channel.

10. The method of claim 1 , comprising:

capturing data points from the channel for storage into a customer relationship management (CRM) system, wherein the data points are evaluated to identify information about the message and recipient of the message.

11. A non-transitory machine-readable storage medium comprising instructions that when executed by a machine, causes the machine to perform operations comprising:

utilizing an application programming interface to create a channel connected to a service of a customer platform, wherein the channel is defined to specify how the channel is to interact with the service;

integrating a channel framework with the customer platform, wherein the channel framework is defined with levels including a first level for building and connecting to channels, a second level for constructing functions of channels in a workspace, and a third level for enabling workspace features within the channel framework;

defining the channel framework to include at least one of a fourth level for integrating the channel framework into a customer relationship management (CRM) system or a fifth level for enabling platform tools within the channel framework;

defining first flows for sending and receiving messages across the channel according to messaging functionality supported by the service;

defining second flows for viewing and interacting with the messages based upon context for viewing and interacting with the messages through the service; and

executing, utilizing the levels of the channel framework, the first flows and the second flows for processing the messages.

12. The non-transitory machine-readable storage medium of claim 11 , wherein the customer platform supports a team workspace service, a customer relationship management service, a workflow service, and a reporting service.

13. The non-transitory machine-readable storage medium of claim 11 , wherein the utilizing comprises:

utilizing a channel integration application programming interface to define and set a channel configuration for the channel.

14. The non-transitory machine-readable storage medium of claim 11 , comprising:

utilizing a data framework to capture and store user accounts for the channel, wherein a user account defines a channel type, user account specific rules, and user account specific settings.

15. The non-transitory machine-readable storage medium of claim 11 , comprising:

in response to receiving a selection of a user account for the channel, syncing and sending messages through a team workspace of a team workspace service during channel connection of the channel.

16. A computing device comprising:

a memory comprising machine executable code; and

a processor coupled to the memory, the processor configured to execute the machine executable code to cause the processor to perform operation comprising:

utilizing an application programming interface to create a channel connected to a service of a customer platform, wherein the channel is defined to specify how the channel is to interact with the service;

integrating a channel framework with the customer platform, wherein the channel framework is defined with levels including a first level for building and connecting to channels, a second level for constructing functions of channels in a workspace, and a third level for enabling workspace features within the channel framework;

defining the channel framework to include at least one of a fourth level for integrating the channel framework into a customer relationship management (CRM) system or a fifth level for enabling platform tools within the channel framework;

defining first flows for sending and receiving messages across the channel according to messaging functionality supported by the service;

defining second flows for viewing and interacting with the messages based upon context for viewing and interacting with the messages through the service; and

executing, utilizing the of levels of the channel framework, the first flows and the second flows for processing the messages.

17. The computing device of claim 16 , wherein the operations comprise:

integrating the channel with workflows associated with notifications, routing automation, and ticket automation.

18. The computing device of claim 16 , wherein the operations comprise:

utilizing a data framework to facilitate message composition comprising text formatting, media handling, attachment handling, recipient search, and channel searching.

19. The computing device of claim 16 , wherein the operations comprise:

enabling a user to move from utilizing the channel in a context to utilizing a different channel in the context.

Assignments (2)
SECURITY INTEREST Recorded Feb 12, 2026
From: HUBSPOT, INC.
To: BANK OF AMERICA, N.A.
Reel/Frame 074818/0036 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 25, 2023
From: VADLAMANI, VIJAY; HOCBO, ANTOINETTE; SINGH, HARMINDER; DEMPKOWSKI, NATHANIEL
To: HUBSPOT, INC.
Reel/Frame 065009/0866 →
Continuity (2)
Provisional Application 63405103 · Sep 9, 2022
Related Publication 20240089224A1 · Mar 14, 2024
References Cited (139)
US 7136941B2 · Nguyen et al. · 2006 [cited by applicant]
US 7580982B2 · Owen et al. · 2009 [cited by applicant]
US 7584114B2 · Estrada et al. · 2009 [cited by applicant]
US 7792835B2 · Bohannon et al. · 2010 [cited by applicant]
US 7831676B1 · Nagar · 2010 [cited by applicant]
US 7984297B2 · Bohannon et al. · 2011 [cited by applicant]
US 7992145B2 · Emerson et al. · 2011 [cited by applicant]
US 8006261B1 · Haberman et al. · 2011 [cited by applicant]
US 8224902B1 · Glasser et al. · 2012 [cited by applicant]
US 8442969B2 · Gross · 2013 [cited by applicant]
US 8594618B2 · Meyer et al. · 2013 [cited by applicant]
US 8706800B1 · Ahmed et al. · 2014 [cited by applicant]
US 8719356B2 · Dillingham et al. · 2014 [cited by applicant]
US 9304862B2 · Simon et al. · 2016 [cited by applicant]
US 9305104B2 · Wu et al. · 2016 [cited by applicant]
US 9317816B2 · Zeng et al. · 2016 [cited by applicant]
US 9356947B2 · Shraim et al. · 2016 [cited by applicant]
US 10115060B2 · Chestnut et al. · 2018 [cited by applicant]
US 10217058B2 · Gamon et al. · 2019 [cited by applicant]
US 10387559B1 · Wendt et al. · 2019 [cited by applicant]
US 10853082B1 · Aleti et al. · 2020 [cited by applicant]
US 10992780B1 · Rudrappa Goniwada et al. · 2021 [cited by applicant]
US 20020099697A1 · Jensen-Grey · 2002 [cited by applicant]
US 20020152254A1 · Teng · 2002 [cited by applicant]
US 20020199194A1 · Ali · 2002 [cited by applicant]
US 20030097617A1 · Goeller et al. · 2003 [cited by applicant]
US 20030208472A1 · Pham · 2003 [cited by applicant]
US 20040034652A1 · Hofmann · 2004 [cited by applicant]
US 20040111327A1 · Kidd · 2004 [cited by applicant]
US 20040122803A1 · Dom et al. · 2004 [cited by applicant]
US 20040260621A1 · Foster · 2004 [cited by applicant]
US 20050160166A1 · Kraenzel · 2005 [cited by applicant]
US 20050188028A1 · Brown, Jr. et al. · 2005 [cited by applicant]
US 20050210111A1 · Fukudome · 2005 [cited by applicant]
US 20050265319A1 · Clegg et al. · 2005 [cited by applicant]
US 20060059253A1 · Goodman · 2006 [cited by examiner]
US 20060095556A1 · Arnold et al. · 2006 [cited by applicant]
US 20060212931A1 · Shull et al. · 2006 [cited by applicant]
US 20060224673A1 · Stern et al. · 2006 [cited by applicant]
US 20060242140A1 · Wnek · 2006 [cited by applicant]
US 20070011073A1 · Gardner et al. · 2007 [cited by applicant]
US 20070136430A1 · Qureshi et al. · 2007 [cited by applicant]
US 20070203996A1 · Davitz et al. · 2007 [cited by applicant]
US 20070299777A1 · Shraim et al. · 2007 [cited by applicant]
US 20080034432A1 · Bohannon et al. · 2008 [cited by applicant]
US 20080168269A1 · Wilson · 2008 [cited by applicant]
US 20080172606A1 · White · 2008 [cited by applicant]
US 20090013041A1 · Farmer et al. · 2009 [cited by applicant]
US 20090019003A1 · Bohannon et al. · 2009 [cited by applicant]
US 20090119268A1 · Bandaru et al. · 2009 [cited by applicant]
US 20090138711A1 · Heimbigner · 2009 [cited by applicant]
US 20090248813A1 · Sawhney · 2009 [cited by applicant]
US 20100100778A1 · Sullivan · 2010 [cited by examiner]
US 20100161506A1 · Bosenick et al. · 2010 [cited by applicant]
US 20100161735A1 · Sharma · 2010 [cited by applicant]
US 20100186088A1 · Banerjee et al. · 2010 [cited by applicant]
US 20100228777A1 · Imig et al. · 2010 [cited by applicant]
US 20100235915A1 · Memon et al. · 2010 [cited by applicant]
US 20100312837A1 · Bodapati et al. · 2010 [cited by applicant]
US 20110029504A1 · King et al. · 2011 [cited by applicant]
US 20110149725A1 · Zhao et al. · 2011 [cited by applicant]
US 20110179067A1 · Dalvi et al. · 2011 [cited by applicant]
US 20110258218A1 · Hayes et al. · 2011 [cited by applicant]
US 20120053887A1 · Nurmi · 2012 [cited by applicant]
US 20120191546A1 · Phelan et al. · 2012 [cited by applicant]
US 20120197862A1 · Woytowitz et al. · 2012 [cited by applicant]
US 20120198056A1 · Shama et al. · 2012 [cited by applicant]
US 20120316904A1 · Eder · 2012 [cited by applicant]
US 20130007627A1 · Monaco · 2013 [cited by applicant]
US 20130047034A1 · Salomon et al. · 2013 [cited by applicant]
US 20130054622A1 · Karmarkar et al. · 2013 [cited by applicant]
US 20130073336A1 · Heath · 2013 [cited by applicant]
US 20130138555A1 · Shishkov · 2013 [cited by applicant]
US 20130238715A1 · Sanyal et al. · 2013 [cited by applicant]
US 20130339456A1 · Nikolayev et al. · 2013 [cited by applicant]
US 20140006139A1 · Aggarwal et al. · 2014 [cited by applicant]
US 20140025683A1 · Howland et al. · 2014 [cited by applicant]
US 20140025763A1 · Furlong et al. · 2014 [cited by applicant]
US 20140105508A1 · Arora · 2014 [cited by applicant]
US 20140108309A1 · Frank et al. · 2014 [cited by applicant]
US 20140156681A1 · Lee et al. · 2014 [cited by applicant]
US 20140214974A1 · Kurzanski et al. · 2014 [cited by applicant]
US 20140236663A1 · Smith · 2014 [cited by applicant]
US 20140258169A1 · Wong et al. · 2014 [cited by applicant]
US 20140279622A1 · Bharadwaj et al. · 2014 [cited by applicant]
US 20140280453A1 · Mattison et al. · 2014 [cited by applicant]
US 20140328172A1 · Kumar et al. · 2014 [cited by applicant]
US 20140372363A1 · Chestnut et al. · 2014 [cited by applicant]
US 20140372566A1 · Milne et al. · 2014 [cited by applicant]
US 20150006647A1 · Steinberg et al. · 2015 [cited by applicant]
US 20150032826A1 · Gunaratnam · 2015 [cited by applicant]
US 20150032827A1 · Tyler et al. · 2015 [cited by applicant]
US 20150081611A1 · Shivakumar · 2015 [cited by applicant]
US 20150100896A1 · Shmarovoz et al. · 2015 [cited by applicant]
US 20150154664A1 · Dawson et al. · 2015 [cited by applicant]
US 20150188874A1 · Feinstein · 2015 [cited by applicant]
US 20150248490A1 · Myslinski · 2015 [cited by applicant]
US 20150286357A1 · Penha et al. · 2015 [cited by applicant]
US 20150310446A1 · Tuchman · 2015 [cited by examiner]
US 20150312187A1 · Menna et al. · 2015 [cited by applicant]
US 20150324469A1 · Keyngnaert et al. · 2015 [cited by applicant]
US 20150347924A1 · Zeng et al. · 2015 [cited by applicant]
US 20150379018A1 · Gur et al. · 2015 [cited by applicant]
US 20150381552A1 · Vijay et al. · 2015 [cited by applicant]
US 20160012364A1 · Filgueiras · 2016 [cited by applicant]
US 20160020917A1 · Tuatini et al. · 2016 [cited by applicant]
US 20160026720A1 · Lehrer · 2016 [cited by examiner]
US 20160036750A1 · Yuan · 2016 [cited by applicant]
US 20160063560A1 · Hameed et al. · 2016 [cited by applicant]
US 20160078455A1 · O'Donnell · 2016 [cited by examiner]
US 20160119260A1 · Ghafourifar et al. · 2016 [cited by applicant]
US 20160156858A1 · Lee et al. · 2016 [cited by applicant]
US 20160180248A1 · Regan · 2016 [cited by applicant]
US 20160226808A1 · Lin · 2016 [cited by applicant]
US 20160232540A1 · Gao et al. · 2016 [cited by applicant]
US 20160307191A1 · Turgeman et al. · 2016 [cited by applicant]
US 20160315969A1 · Goldstein · 2016 [cited by applicant]
US 20160359793A1 · Kraios et al. · 2016 [cited by applicant]
US 20170005954A1 · Shaltiel et al. · 2017 [cited by applicant]
US 20170031894A1 · Bettersworth et al. · 2017 [cited by applicant]
US 20170068982A1 · Vangala et al. · 2017 [cited by applicant]
US 20170103439A1 · Kolb et al. · 2017 [cited by applicant]
US 20170103441A1 · Kolb et al. · 2017 [cited by applicant]
US 20170186042A1 · Wong et al. · 2017 [cited by applicant]
US 20170221089A1 · Zhu et al. · 2017 [cited by applicant]
US 20170264577A1 · Ganin et al. · 2017 [cited by applicant]
US 20170289287A1 · Modi et al. · 2017 [cited by applicant]
US 20170317962A1 · Chen · 2017 [cited by applicant]
US 20170337569A1 · Sasson · 2017 [cited by applicant]
US 20170353410A1 · Gonzales · 2017 [cited by applicant]
US 20180039696A1 · Zhai et al. · 2018 [cited by applicant]
US 20180097759A1 · Brechbuhl et al. · 2018 [cited by applicant]
US 20180097828A1 · Coskun · 2018 [cited by applicant]
US 20180121986A1 · Akkiraju et al. · 2018 [cited by applicant]
US 20180336495A1 · Chestnut et al. · 2018 [cited by applicant]
US 20200067861A1 · Leddy · 2020 [cited by applicant]
US 20200106630A1 · Bourassa · 2020 [cited by examiner]
US 20210342785A1 · Mann · 2021 [cited by examiner]
US 20230246860A1 · Hahn · 2023 [cited by examiner]