# US 2025/0219974 A1 · System and method of managing channel agnostic messages in a multi-client customer platform

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2025/0219974 A1
- Document ID: US20250219974A1
- Status: Published application
- Kind: A1
- Application number: 19/086,502
- Filed: 2025-03-21
- Published: 2025-07-03
- Earliest claimed: 2022-09-09
- Assignees: HubSpot, Inc.
- Applicants: Hubspot, Inc.
- Inventors: Vijay VADLAMANI; Antoinette HOCBO; Harminder SINGH; Nathaniel DEMPKOWSKI
- Web page: https://patentgrep.com/patent/US20250219974A1

## CPC

- H04L 51/046: Interoperability with other network applications or services
- H04L 51/02: using automatic reactions or user delegation, e.g. automatic replies or chatbot-generated messages
- H04L 51/21: Monitoring or handling of messages
- H04L 51/56: Unified messaging, e.g. interactions between e-mail, instant messaging or converged IP messaging [CPM]
- H04L 51/066: Format adaptation, e.g. format conversion or compression
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## 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

### Claim 1

A method comprising:
utilizing a data framework 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;
defining a first set of flows for sending and receiving messages across the channel according to messaging functionality supported by the service;
defining a second set of flows for viewing and interacting with the messages based upon context for viewing and interacting with the messages through the service; and
executing the first set of flows and the second set of flows for processing the messages.

### Claim 2 (depends on 1)

The method of claim 1, wherein the customer platform supports a team workspace service connected to the channel.

### Claim 3 (depends on 1)

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.

### Claim 4 (depends on 1)

The method of claim 1, comprising:
utilizing a user experience framework to discover and connect the channel to the service.

### Claim 5 (depends on 1)

The method of claim 1, comprising:
utilizing the 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.

### Claim 6 (depends on 1)

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.

### Claim 7 (depends on 1)

The method of claim 1, comprising:
integrating the channel with workflows associated with a ticket automation service.

### Claim 8 (depends on 1)

The method of claim 1, comprising:
utilizing the data framework to facilitate message composition and channel and recipient searching.

### Claim 9 (depends on 1)

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.

### Claim 10 (depends on 1)

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.

### Claim 11 (depends on 1)

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.

### Claim 12

A non-transitory machine-readable storage medium comprising instructions that when executed by a machine, causes the machine to perform operations comprising:
utilizing a data framework 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;
defining a first set of flows for sending and receiving messages across the channel according to messaging functionality supported by the service;
defining a second set of flows for viewing and interacting with the messages based upon context for viewing and interacting with the messages through the service; and
executing the first set of flows and the second set of flows for processing the messages.

### Claim 13 (depends on 12)

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

### Claim 14 (depends on 12)

The non-transitory machine-readable storage medium of claim 12, wherein the utilizing comprises:
utilizing a channel integration application programming interface to define and set a channel configuration for the channel.

### Claim 15 (depends on 12)

The non-transitory machine-readable storage medium of claim 12, comprising:
utilizing the 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.

### Claim 16 (depends on 12)

The non-transitory machine-readable storage medium of claim 12, 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.

### Claim 17

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 a data framework 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;
defining a first set of flows for sending and receiving messages across the channel according to messaging functionality supported by the service;
defining a second set of flows for viewing and interacting with the messages based upon context for viewing and interacting with the messages through the service; and
executing the first set of flows and the second set of flows for processing the messages.

### Claim 18 (depends on 17)

The computing device of claim 17, wherein the operations comprise:
integrating the channel with workflows associated with notifications, routing automation, and ticket automation.

### Claim 19 (depends on 17)

The computing device of claim 17, wherein the operations comprise:
utilizing the data framework to facilitate message composition comprising text formatting, media handling, attachment handling, recipient search, and channel searching.

### Claim 20 (depends on 17)

The computing device of claim 17, wherein the operations comprise:
enabling a user to move from utilizing the channel in a context to utilizing a different channel in the context.
