Techniques for messaging bot rich communication
Abstract
Techniques for messaging bots with rich communication are described. In one embodiment, an apparatus may comprise a messaging component operative to receive a message from a client device; and add the message to a message queue; a message queue monitoring component operative to monitor the message queue; detect that the message indicates messaging bot invocation; and submit the message to a bot framework component based on detecting that the message indicates messaging bot invocation; and the bot framework component operative to determine a messaging bot associated with the message; and submit the message to the messaging bot. Other embodiments are described and claimed.
Claims
exact text as granted — not AI-modifiedWhat is claimed is:
1 . A computer-implemented method, comprising:
accessing, by a messaging system, a first message in a message queue, the first message directed to one of a plurality of messaging bots and comprising a predetermined bot invocation symbol followed by a bot alias; determining, for the first message, that the bot alias of the first message corresponds to a name registered with the messaging system for a first messaging bot of the plurality of messaging bots; and submitting the first message to the first messaging bot, wherein the first message comprises a bot command text segment.
2 . The method of claim 1 , wherein the first message is associated with a message thread of a messaging application on a client device, and wherein the method further comprises:
receiving, from the client device, a command initial text portion of the bot command text segment; and submitting the command initial text portion to the first messaging bot, wherein the bot command text segment is a first predicted bot command text segment received from the first messaging bot in response to the submitted command initial text portion.
3 . The method of claim 2 , further comprising:
receiving a response from the first messaging bot to the submitted first message; and adding the response to the message queue for delivery to the messaging application on the client device.
4 . The method of claim 3 , wherein the response from the first messaging bot is added to the message queue marked for display in the message thread, and wherein the response includes an in-thread bot control empowering a user of the client device to take an action related to the response.
5 . The method of claim 2 , further comprising:
receiving, in response to the submitted command initial text portion, a plurality of predicted bot command text segments including the first predicted bot command text segment from the first messaging bot, wherein the command initial text portion is a respective portion of each of the plurality of predicted bot command text segments, and wherein each of the plurality of predicted bot command text segments comprises a respective command compatible with the first messaging bot; transmitting the plurality of predicted bot command text segments to the client device; and receiving, from the client device and as the bot command text segment, the first predicted bot command text segment.
6 . The method of claim 1 , wherein the first message is associated with a message thread, and wherein the bot command text segment of the first message comprises a bot subscription command, the method further comprising:
subscribing the message thread to the first messaging bot in response to the bot subscription command; receiving a broadcast message from the first messaging bot; determining a plurality of subscriber threads for the broadcast message based on the first messaging bot, the plurality of subscriber threads including the message thread; dividing the plurality of subscriber threads into a plurality of subscriber thread chunks; assigning each of the plurality of subscriber thread chunks to a broadcast worker of a plurality of broadcast workers; and adding the broadcast message to a plurality of message queues based on the assignments, the plurality of message queues comprising the message queue.
7 . The method of claim 1 , wherein the first message is associated with a message thread of a messaging application on a client device, and wherein the method further comprises:
receiving, from the client device, a partial bot address including at least the predetermined bot invocation symbol; generating, in response to the received partial bot address, a subset of the plurality of messaging bots as suggested bots; transmitting the suggested bots to the client device; and receiving a selection of one of the suggested bots from the client device as the first messaging bot.
8 . The method of claim 7 , wherein the subset of the plurality of messaging bots generated as the suggested bots is based on at least one of contents of the message thread, or a history of one or more users associated with the message thread.
9 . The method of claim 7 , wherein the partial bot address further includes a bot alias initial text portion, and wherein the subset of the plurality of messaging bots generated as the suggested bots is based on the bot alias initial text portion.
10 . The method of claim 9 , wherein the bot alias initial text portion is a respective portion of each of the suggested bots in the subset.
11 . The method of claim 7 , further comprising receiving, from the first messaging bot, one or more suggested bot commands based on at least one of contents of the message thread, or a history of one or more users associated with the message thread.
12 . The method of claim 11 , further comprising receiving a selection of one of the suggested bot commands from the client device, wherein the first message is submitted to the first messaging bot based on the received selection of the one of the suggested bot commands.
13 . At least one non-transitory computer-readable storage medium comprising instructions that, when executed, cause a processor to:
access, by a messaging system, a first message in a message queue, the first message directed to one of a plurality of messaging bots and comprising a predetermined bot invocation symbol followed by a bot alias; determine, for the first message, that the bot alias of the first message corresponds to a name registered with the messaging system for a first messaging bot of the plurality of messaging bots; and submit the first message to the first messaging bot, wherein the first message comprises a bot command text segment.
14 . The non-transitory computer-readable storage medium of claim 13 , wherein the first message is associated with a message thread of a messaging application on a client device, and wherein the instructions, when executed, further cause the processor to:
receive, from the client device, a command initial text portion of the bot command text segment; and submit the command initial text portion to the first messaging bot, wherein the bot command text segment is a first predicted bot command text segment received from the first messaging bot in response to the submitted command initial text portion.
15 . The non-transitory computer-readable storage medium of claim 14 , wherein the instructions, when executed, further cause the processor to:
receive a response from the first messaging bot to the submitted first message; and add the response to the message queue for delivery to the messaging application on the client device.
16 . The non-transitory computer-readable storage medium of claim 14 , wherein the instructions, when executed, further cause the processor to:
receive, in response to the submitted command initial text portion, a plurality of predicted bot command text segments including the first predicted bot command text segment from the first messaging bot, wherein the command initial text portion is a respective portion of each of the plurality of predicted bot command text segments, and wherein each of the plurality of predicted bot command text segments comprises a respective command compatible with the first messaging bot; transmit the plurality of predicted bot command text segments to the client device; and receive, from the client device and as the bot command text segment, the first predicted bot command text segment.
17 . The non-transitory computer-readable storage medium of claim 13 , wherein the first message is associated with a message thread of a messaging application on a client device, and wherein the instructions, when executed, further cause the processor to:
receive, from the client device, a partial bot address including at least the predetermined bot invocation symbol; generate, in response to the received partial bot address, a subset of the plurality of messaging bots as suggested bots; transmit the suggested bots to the client device; and receive a selection of one of the suggested bots from the client device as the first messaging bot.
18 . The non-transitory computer-readable storage medium of claim 17 , wherein the subset of the plurality of messaging bots generated as the suggested bots is based on at least one of contents of the message thread, or a history of one or more users associated with the message thread.
19 . The non-transitory computer-readable storage medium of claim 17 , wherein the partial bot address further includes a bot alias initial text portion, and wherein the subset of the plurality of messaging bots generated as the suggested bots is based on the bot alias initial text portion.
20 . A messaging system comprising:
a processor; and memory storing instructions which when executed by the processor cause the processor to:
access, by the messaging system, a first message in a message queue, the first message directed to one of a plurality of messaging bots and comprising a predetermined bot invocation symbol followed by a bot alias;
determine, for the first message, that the bot alias of the first message corresponds to a name registered with the messaging system for a first messaging bot of the plurality of messaging bots; and
submit the first message to the first messaging bot, wherein the first message comprises a bot command text segment.Join the waitlist — get patent alerts
Track US2023015178A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.