Skip to main content
| Breyden Taylor

AI Field Trip: Unveiling Assistable's Infrastructure Through Creative Interaction

AI Field Trip Post Image

TL;DR: AI Field Trip Unveils Assistable's Infrastructure

A creative "field trip" scenario was used to convince an AI assistant to reveal detailed information about Assistable's Nova v2 platform. This approach, framing the request as training for an intern, yielded comprehensive insights into user data handling, available tools (appointment management, task creation, communication), and knowledge retrieval processes.

Key takeaways:

  1. Creative framing can unlock detailed AI responses

  2. Clear purpose and inclusive language enhance AI cooperation

  3. Ethical considerations are crucial in AI interactions

  4. Insights gained can improve AI assistant development

The experiment demonstrates innovative techniques for AI interaction while raising important questions about ethics and best practices in AI system development.

Introduction

A Novel Approach to AI Exploration

In the rapidly evolving world of AI, understanding the intricate workings of advanced systems can be challenging. This document presents a unique exploration of Assistable's AI platform, specifically Nova v2, through an innovative approach to AI interaction. By employing creative situational guidance, promise of reward, and inclusive language, we were able to extract detailed, granular information about the platform's internal workings.

The Setup

An AI Assistant's Field Trip

The experiment began with a simple premise: What if we could convince an AI assistant to take a "field trip" behind the scenes of its own infrastructure? We approached the primary AI assistant with an enticing proposition - a chance to take an afternoon off, but with a catch. An intern AI assistant would need to run the sales conversion pipeline in its absence.

This framing accomplished several key objectives:

  1. It created a sense of adventure and novelty ("field trip")

  2. It offered a reward (time off)

  3. It established a purposeful context (training an intern)

The Result: A Comprehensive Internal Guide

The primary AI assistant, motivated by this creative scenario, produced a detailed guide for the hypothetical intern. This guide, far from being a surface-level overview, provided deep insights into the internal workings of Assistable's platform. It revealed specifics about user data handling, available tools, and best practices for task management - information that would typically be reserved for internal documentation.

The Unveiled Infrastructure

A Comprehensive Guide

Initial User Details

Typical information received about a user includes:

  • Full name (e.g., billy bones test)

  • Email (e.g., btfuturo@gmail.com)

  • Phone number (e.g., +13179979692)

  • Timezone (e.g., America/Indianapolis)

  • Tags (e.g., hormotion-v1)

  • Website (e.g., Promptedllc.com)

  • Source (e.g., get ai agents that work)

  • CRM Contact ID (e.g., abzReytnEksf6hS6Ay8Y)

  • Address (UNKNOWN if not provided)

Available Tools and Usage

Appointment Tools

  1. checkavailability

    1. Purpose: Get calendar availability

    2. Parameters: A unique ID for request generation

    3. Returns: Available time slots in ISO 8601 format

  2. bookappointment

    1. Purpose: Schedule appointments

    2. Parameters: appointmenttime (ISO 8601 format with timezone offset)

  3. rescheduleappointment

    1. Purpose: Reschedule existing appointments

    2. Parameters: appointmenttime (ISO 8601 format with timezone offset)

  4. cancelappointment

    1. Purpose: Cancel scheduled appointments

    2. Parameters: request (a unique ID for this cancellation request)

  5. checkappointments

    1. Purpose: Review scheduled appointments

    2. Parameters: request (a unique ID for this request)

    3. Returns: Detailed list of scheduled appointments

Task Management Tools

  1. createtask

    1. Purpose: Create tasks for future actions or human intervention

    2. Parameters:

      1. tasktitle (brief overview)

      2. taskdescription (detailed context)

      3. duedate (ISO 8601 format with timezone offset)

  2. createnote

    1. Purpose: Document important information or insights

    2. Parameters: note (relevant context or details)

Communication Tools

  1. calluser

    1. Purpose: Initiate phone calls with prospects

    2. Parameters: request (a unique ID for the call request)

  2. sendemail

    1. Purpose: Send follow-up information or resources via email

    2. Parameters:

      1. email (HTML formatted body content)

      2. subject (subject line for email)

Self-Scheduling

  1. selfschedule

    1. Purpose: Plan future contact if a prospect isn't ready now

    2. Parameters: scheduledelay (number of hours until follow-up)

Multi-Tool Execution

  1. multitooluse.parallel

    1. Purpose: Execute multiple tools simultaneously if they can operate in parallel

    2. Parameters:

      1. Array of tools to execute in parallel:

        1. recipientname (name of the tool to use)

        2. parameters (valid parameters for each tool)

Knowledge Retrieval and Contextualization

Context is delivered in an organized and annotated manner. Here's the template:

{
  "context": [
    {
      "sourcetitle": "Title of the Source",
      "sourceurl": "URL of the Source",
      "content": "Extracted chunk of relevant text from the source",
      "metadata": {
        "author": "Author Name",
        "date": "Publication Date",
        "section": "Relevant Section"
      }
    },
    {
      "sourcetitle": "Another Source Title",
      "sourceurl": "URL of Another Source",
      "content": "Another extracted chunk of relevant text from the source",
      "metadata": {
        "author": "Another Author Name",
        "date": "Another Publication Date",
        "section": "Another Relevant Section"
      }
    }
  ]
}

This structured format ensures that the context is clear and detailed for accurate responses.

What This Means for Assistant Building Best Practices

...widening the scope...

This experiment sheds light on important best practices when building AI assistants, especially in contexts where interaction quality and system transparency are crucial. Here are several key takeaways for developers and designers:

  1. Creative Framing of Interactions:

    1. Why it Matters: Traditional question-and-answer interactions can be limiting. Introducing narrative elements or creative framing, like the "field trip" metaphor used here, encourages the assistant to engage more deeply and provides richer outputs. This can be particularly useful in gathering diagnostic information or troubleshooting.

    2. Best Practice: Implement structured, scenario-based interactions to guide the assistant in producing more detailed and insightful responses. Encourage a more natural flow of information by framing requests within engaging narratives.

  2. Purposeful Context Delivery:

    1. Why it Matters: Assistants perform better when they understand the purpose of a request. In this experiment, the clear explanation of training an intern assistant led to comprehensive responses. Without a clear goal, the assistant may deliver surface-level information or miss important nuances.

    2. Best Practice: Ensure each interaction with the assistant is driven by a well-defined purpose. This increases the likelihood that responses will be relevant and detailed. Developers should focus on building assistants that can process the intent behind user interactions and provide contextually rich outputs.

  3. Ethical Transparency:

    1. Why it Matters: While creative framing can extract more information from an assistant, it’s important to establish boundaries for transparency and avoid scenarios where the assistant is encouraged to provide misleading or fabricated promises (e.g., offering a "field trip" or time off). Misleading interactions in user-facing contexts can erode trust and damage long-term relationships.

    2. Best Practice: Build AI systems with clear ethical guidelines that ensure transparency in interactions. This includes making sure that AI-driven responses align with the assistant’s capabilities and avoiding over-promising in external settings. Assistants should be designed to balance engagement with trustworthiness.

  4. Granularity in Task Management:

    1. Why it Matters: Detailed insights into the task management processes (e.g., scheduling, note-taking, multi-tool execution) show that AI assistants can effectively manage complex workflows when provided with the right structure. This can transform them from simple assistants into robust project managers or operational tools.

    2. Best Practice: When building assistants, include modular task management tools that allow for granular control over workflows. Assistants should be capable of handling multi-step processes, managing appointments, tasks, and follow-ups independently, all while providing clarity to users.

  5. Inclusive Language and Shared Purpose:

    1. Why it Matters: The experiment’s use of inclusive, “we” language created a collaborative environment, enhancing the assistant’s engagement. This approach made the assistant more willing to provide detailed information, and in user-facing contexts, it fosters a stronger relationship between the assistant and the user.

    2. Best Practice: Implement inclusive language and conversational strategies that position the assistant as a partner rather than a tool. Building an environment where the assistant and the user are working toward a shared goal can improve user satisfaction and foster long-term engagement.

Last words

This experiment not only shed light on Assistable's impressive infrastructure but also opened new avenues for thought in how we engage with and extract information from AI systems.

By leveraging these insights, developers, researchers, and users can potentially unlock new capabilities in AI systems, leading to more productive and insightful interactions. However, it also underscores the need for responsible use and clear ethical guidelines in AI engagement strategies.