Hero cards that display contextual information and actions for backend systems
Systems herein supply hero cards that display contextual information and actions based on backend systems. The information and actions are related to a trigger content item in an application that does not have access to the backend systems. A hero agent running a user device can communicate the trigger content to a hero server. The hero server can determine which connectors to backend systems relate to the user device, and then can retrieve result information from one or more of the backend systems. The result information populates the hero card, which the hero agent displays within the application. Action buttons on the hero card cause the hero agent to contact one or more of the backend systems to cause an action to take place there.
1. A system for prompting action in a backend system, the system comprising:
a non-transitory, computer-readable medium that contains instructions;
a processor that executes the instructions to perform stages including:
sending, from a hero server, a hero agent to a user device for installation at the user device, the hero agent enabling the user device to communicate with the hero server;
receiving, at the hero server, an indication from the hero agent of a detection of trigger content within an application of the user device, the application being unassociated with a plurality of backend systems;
based at least in part on receiving the indication, identifying at the hero server at least a first backend system from the plurality of backend systems;
constructing, at the hero server, hero content for visually displaying a relationship between the trigger content within the application and a suggested action to be performed in the first backend system; and
sending the hero content from the hero server to the user device for displaying a first action button for performing the suggested action in the first backend system from the application.
2. The system of claim 1 , wherein the indication received by the hero server from the hero agent includes a service request.
3. The system of claim 2 , wherein the application is an email application and the service request is generated by the email application based on an email being the trigger content.
4. The system of claim 3 , wherein the first action button is displayed within a hero card that is displayed simultaneously with other emails in the email application.
5. The system of claim 1 , the stages further comprising identifying at the hero server a second backend system from the plurality of backend systems based at least in part on the trigger content, wherein the hero content includes additional information for visually displaying a relationship between the trigger content and a second suggested action to be performed in the second backend system.
6. The system of claim 5 , wherein the hero content is sent from the hero server to the user device for further displaying a second action button for performing the suggested action in the second backend system from the application, the second action button being displayed simultaneously with the first action button.
7. The system of claim 1 , the stages further comprising the hero server receiving an instruction from the hero agent to perform the suggested action at the first backend system in response to a selection of the first action button at the application.
8. A non-transitory, computer-readable medium containing instructions executed by at least one processor to perform stages for generating hero cards, the stages comprising: sending, from a hero server, a hero agent to a user device for installation at the user device, the hero agent enabling the user device to communicate with the hero server;
receiving, at the hero server, an indication from the hero agent of a detection of trigger content within an application of the user device, the application being unassociated with a plurality of backend systems;
based at least in part on receiving the indication, identifying at the hero server at least a first backend system from the plurality of backend systems;
constructing, at the hero server, hero content for visually displaying a relationship between the trigger content within the application and a suggested action to be performed in the first backend system; and
sending the hero content from the hero server to the user device for displaying a first action button for performing the suggested action in the first backend system from the application.
9. The non-transitory, computer-readable medium of claim 8 , wherein the indication received by the hero server from the hero agent includes a service request.
10. The non-transitory, computer-readable medium of claim 9 , wherein the application is an email application and the service request is generated by the email application based on an email being the trigger content.
11. The non-transitory, computer-readable medium of claim 10 , wherein the first action button is displayed within a hero card that is displayed simultaneously with other emails in the email application.
12. The non-transitory, computer-readable medium of claim 8 , the stages further comprising the hero server receiving an instruction from the hero agent to perform the suggested action at the first backend system in response to a selection of the first action button at the application.
13. The non-transitory, computer-readable medium of claim 8 , the stages further comprising identifying at the hero server a second backend system from the plurality of backend systems based at least in part on the trigger content, wherein the hero content includes additional information for visually displaying a relationship between the trigger content and a second suggested action to be performed in the second backend system.
14. A method for presenting backend content within an application using hero cards, comprising:
sending, from a hero server, a hero agent to a user device for installation at the user device, the hero agent enabling the user device to communicate with the hero server;
receiving, at the hero server, an indication from the hero agent of a detection of trigger content within an application of the user device, the application being unassociated with a plurality of backend systems;
based at least in part on receiving the indication, identifying at the hero server at least a first backend system from the plurality of backend systems;
constructing, at the hero server, hero content for visually displaying a relationship between the trigger content within the application and a suggested action to be performed in the first backend system; and
sending the hero content from the hero server to the user device for displaying a first action button for performing the suggested action in the first backend system from the application.
15. The method of claim 14 , further comprising, in response to detecting the trigger content, sending a service request from the hero agent to the hero server.
16. The method of claim 15 , wherein the indication received by the hero server from the hero agent includes a service request.
17. The method of claim 16 , wherein the first action button is displayed within a hero card that is displayed simultaneously with other emails in the email application.
18. The method of claim 14 , further comprising identifying at the hero server a second backend system from the plurality of backend systems based at least in part on the trigger content, wherein the hero content includes additional information for visually displaying a relationship between the trigger content and a second suggested action to be performed in the second backend system.
19. The method of claim 18 , wherein the hero content is sent from the hero server to the user device for further displaying a second action button for performing the suggested action in the second backend system from the application, the second action button being displayed simultaneously with the first action button.
20. The method of claim 14 , further comprising receiving, at the hero server, an instruction from the hero agent to perform the suggested action at the first backend system in response to a selection of the first action button at the application.