Vonage AI Studio
  • Welcome to AI Studio!
  • ✨Platform Updates
  • AI Studio
    • Create a new agent
    • NLU AI Engine Preferences
    • Agent Building Features
    • Agent Templates
      • Take Message
      • Updating Details
      • Survey
      • FAQ
      • Package Tracking
      • Caller Identification
      • Customer Service
      • Hotels
      • Appointment Management
    • Tester
    • Editor Mode & Publish
    • Reports
    • Users
    • Knowledge AI
  • Properties
    • Entities
      • System Entities List
      • Best Practices
    • Intents
      • How do we analyze user input?
      • Generate Training Data
      • System Intents
      • Intent Annotation
    • Parameters
    • Contacts
    • Tags
    • Recordings
  • Voice
    • Get started
      • Create your first conversational flow!
      • Triggering Outbound Call API
      • Sending an Outbound Call Request via Postman
      • Integration via SIP for Telephony Agents
    • Nodes
      • Start node
      • Conversation
        • Classification
          • Intent Ambiguity
        • Collect Input
          • Entity Ambiguation
        • Speak
        • Conditions
        • Listen
        • Q&A Node
      • Advanced
        • Reset Counter
        • Counter
        • Set Parameter
        • Custom Code
        • NCCO Node
      • Actions
        • Send Email
        • Call Routing
        • End Call
        • Start Recording
        • Stop Recording
        • Send SMS
      • Integrations
        • Webhook
        • Legacy SalesForce Authentication Node
          • SalesForce Authentication
            • How to create a SalesForce Connected App
        • SalesForce Actions
        • Generative AI
          • Setting up Generative AI Node Integration
          • Migrating from the GenAI node to Knowledge AI
      • Flow Control
        • Context Switch
        • Flows
    • Events
  • WhatsApp
    • Get started
      • Create your first conversational flow!
      • Triggering an outbound WhatsApp virtual agent
    • Nodes
      • Start node
      • Conversation
        • Collect Input
          • Entity Ambiguation
        • Classification
          • Intent Ambiguity
        • Send Message
        • Conditions
      • Advanced
        • Reset Counter
        • Counter
        • Set Parameter
        • Custom Code
      • Actions
        • Send Email
        • End Conversation
        • Send SMS
        • Live Agent Routing
      • Integrations
        • Webhook
        • Legacy SalesForce Authentication Node
          • SalesForce Authentication
            • How to create a SalesForce Connected App
        • SalesForce Actions
        • Generative AI
          • Setting up Generative AI Node Integration
          • Endless FAQs on WhatsApp With Generative AI and AI Studio
      • Flow Control
        • Context Switch
        • Flows
    • Events
  • SMS
    • Get started
      • Create your first conversational flow!
      • Triggering an outbound SMS Virtual Agent
    • Nodes
      • Start node
      • Conversation
        • Classification
          • Intent Ambiguity
        • Conditions
        • Send Message
        • Collect Input
          • Entity Ambiguation
      • Advanced
        • Reset Counter
        • Counter
        • Set Parameter
        • Custom Code
      • Actions
        • Send Email
        • End Conversation
        • Send SMS
        • Live Agent Routing
      • Integrations
        • Webhook
        • Legacy SalesForce Authentication Node
          • SalesForce Authentication
            • How to create a SalesForce Connected App
        • SalesForce Actions
        • Generative AI
          • Setting up Generative AI Node Integration
          • Use Case Example: Gym Business
      • Flow Control
        • Context Switch
        • Flows
    • Events
  • HTTP
    • Get started
      • Create your first conversational flow!
    • Nodes
      • Start node
      • Conversation
        • Classification
          • Intent Ambiguity
        • Collect Input
          • Entity Ambiguation
        • Send Message
        • Conditions
      • Advanced
        • Reset Counter
        • Counter
        • Set Parameter
        • Custom Code
      • Action
        • Send Email
        • Send SMS
        • Live Agent Routing
          • Websockets connections for Live agent Routing
      • Integrations
        • Webhook
        • Legacy SalesForce Authentication Node
          • SalesForce Authentication
            • How to create a SalesForce Connected App
        • SalesForce Actions
        • Generative AI
          • Setting up Generative AI Node Integration
          • Use case Example : Online Shopping
      • Flow Control
        • Context Switch
        • Flows
    • Events
  • API Integration
    • Authentication
    • Insights
  • There's more
    • FAQs
    • Languages Available
Powered by GitBook
On this page

Was this helpful?

  1. AI Studio
  2. Agent Templates

Package Tracking

Order Tracking with the help of a Virtual Assistant

PreviousFAQNextCaller Identification

Last updated 1 year ago

Was this helpful?

Use this template when you want to enable seamless self-service to help your customers track their orders.

To use this template, simply choose it from the templates page when you create a new agent. You can then make changes to customize it based on your business needs.

Flow Overview

Step 1 - Starting the conversation

We start with a Speak node introducing the company to the caller. Using the Speak node we don't expect any input from the caller in this node.

Step 2 - Collect the Caller's Query

After the greeting, we want to understand why the caller is calling. This means that we are looking to collect a value from the user input - with the help of the Collect Input node.

In case we can't collect the caller's input, the agent will route the call to a live representative. Therefore, the No Input and Missed tabs are connected to a Speak node, notifying the caller that in this case the call is being routed, followed by the Route Call action node.

Step 3 - Match the Caller's Input

The Classification node will match the caller's input to the right response in the right intent. In this use case, the caller requests the whereabouts of his recently ordered package.

If the agent can't match the input to the right intent, the Missed tab is triggered, which in this case is connected to the Speak and Route Call node that transfers the call to an agent.

Step 4 - Check Package ID

In another Collect Input node, the agent collects the Order ID and then sends it over to the third-party service via the Webhook node to retrieve the order status.

In case we can't collect the caller's input, the agent will route the call to a live representative. Therefore, the No Input and Missed tabs are connected to a Speak node, notifying the caller that in this case the call is being routed, followed by the Route Call action node.

If the Webhook fails to retrieve the order number, we also want to route the call to a live representative. Therefore, the exit point of the Failed tab in the Webhook node is connected to the entry point of the Speak node indicating that the call is going to be transferred.

Step 5 - Inform Caller about Delivery Status

One we retrieved the delivery status, we are going to inform the caller about their ETA and ask them if they'd like to receive a text message with a tracking link for the future in a new Collect Input node ("Your estimated delivery date is scheduled for $ARRIVAL_DATE . Do you want me to send you a tracking link via SMS?")

The confirmation of the caller is being collected in the Conditions node. If the Caller would like to receive a text message, the agent is going to send the message in a Send SMS action node and a Speak node indicating the arrival of the message. After sending the message, the agent will terminate the call.

If the caller denies, the agent will simply terminate the call. Therefore, the endpoint of the Default tab in the Conditions node that indicates the caller's "no" is connected to the entry point of the Speak node letting the caller know this call is going to be terminated.