In order to create an HTTP agent, after you clicked on "Create Agent" select the HTTP option. This is a text-based agent you can integrate into any application and initialize via HTTP request.
These agents have no phone number but will be accessible via HTTP.
The nodes available will be slightly different than in the voice-based agent. Some capabilities are not supported in HTTP-based agents such as the "Listen" node.
Sessions are interactions between user and agent. One session has a time limit of 24 hours after which the session with the agent has to be reinitiated.
For the launch of the HTTP agent to work, make sure you have published your agent.
Follow these text-based agents to embed your virtual agent in any platform.
The endpoint of your query depends on the region you selected for your agent. If you selected US as the region for your agent, please use this endpoint:-
Once you have the Session ID you can start the actual conversation between agent and user.
Every step will execute all nodes until the session status turns to
AWAITING_INPUTand will return a flow response containing all of the executed nodes with their status, errors, and messages.
Step in Session
If you selected US as the region for your agent, please use this endpoint:-
AWAITING_INPUT- agent is waiting for user response
ENDED- conversation flow has ended and reached the last node in the conversation. This can be either because you added an "end call" node or this node is not connected to the following one.
The initial user input will be automatically captured as the value of the
INITIAL_MESSAGEsystem parameter and saved throughout the session of the conversation.
This is mostly relevant for inbound customer care agents.
INITIAL_MESSAGEparameter value to dictate the start of the conversation by creating custom conditions based on the customer’s input.
In the use case below, we have two intents - Office Location and Forgot Password. If the initial message of the user is not just "Hi there, I have a question" but "I need help resetting my password", the agent can use and attempt to classify that input immediately, without waiting for the agent to prompt the user.
Add the Classification node with your intents right after the START node. This way the agent will check if the user's initial message matches an intent and can direct the conversation accordingly.
If no match is found, then the user's input will go to the Classification node's Missed tab and the agent will prompt the user normally.
Same as for regular telephony agents, you are able to see the conversation of an HTTP agent in the reports.