Capri Ai
  • Quickstart Guides
    • Getting Started With Capri AI
    • Video Onboarding Course
    • Setup
    • Capri AI Affiliate Program
  • Capri Portal
    • Accessing the Capri Portal
    • Navigating the Capri Portal
    • Setting up the Settings
    • Setting up an Agent
    • Setting up Actions
      • GHL Channel
        • Contact/Custom Fields
      • GHL Calendar
      • Google Calendar
      • Google Sheets
      • Google Docs
      • Website Reading
    • Adding a User to your Organization
    • Using the Emulator
      • Adding the Emulator as a Custom Menu Item
      • Iframe Emulator Settings
    • Understanding Fallbacks
    • Setting up Rebilling
    • Snapshots
  • Spreadsheet and Knowledge Base
    • Setting up and Using a Spreadsheet
    • Having the Spreadsheet Auto-Update
  • PROMPT DESIGN
    • Creating Prompts
    • Prompt Examples
  • INTEGRATING WITH CRM AND WEBHOOK INFORMATION
    • GoHighLevel (GHL)
    • HubSpot
    • Webhook Information
    • Triggers
      • Automated Follow-Up For Stale Leads
    • Using Multiple Webhooks
    • Uphex
  • API and Developer Tools
    • Using The New Public API
      • Agent API
    • Email and Plain Text Make Modules
    • Model Pricing
  • Customer Support
    • Contact Us!
  • Legacy Information
    • Legacy Information
      • Setup (Legacy)
      • Accessing the Capri Portal (Legacy)
      • Navigating the Capri Portal (Legacy)
      • Capri Portal Settings (Legacy)
      • Using the Emulator (Legacy)
      • Adding the Emulator as a Custom Menu Item (Legacy)
      • Connecting to the CRM (Legacy)
        • GoHighLevel (GHL)
        • Webhook Information
      • Custom Tags (Legacy)
      • Handoff and Disqualify (Legacy)
      • Testing and Debugging (Legacy)
      • Understanding Fallbacks (Legacy)
      • Overview of the calendar integration (Legacy)
      • Respond Tasks (Legacy)
      • Outreach Tasks (Legacy)
      • Evaluate Tasks (Legacy)
      • Custom Tasks (Legacy)
      • Setting up a Spreadsheet (Legacy)
      • Using the Knowledge Base Extension (Legacy)
Powered by GitBook
On this page
  1. Capri Portal

Understanding Fallbacks

PreviousIframe Emulator SettingsNextSetting up Rebilling

Last updated 10 months ago

Fallbacks are what happens whenever the AI runs into a situation that it doesn't know how to handle. This could be something like the contact giving a gibberish answer, sending photos, which the AI can't understand, or something unexpected happening in the conversation. When this happens, the AI will, by default, stop responding to the contact, add a tag called "fallback_reached", and there will usually be an entry added to the fallback section of the portal!

Fallbacks can also potentially happen whenever the AI fails to book an appointment, such as the booking function failing, and when this happens our system will add a fallback_reached tag in this instance as well.

To solve for this sort of thing, you can set up a workflow that notifies a team member to come and take over whenever the fallback_reached tag is added!

The Fallback Section

Whenever a fallback happens, it is added to the fallback section in the Capri portal.

Here you're given information about each fallback event, with information about the agent that triggered it, the time of the fallback, what the AI was going to say, etc. and you can click on the details button for each occurrence for more specific information!

To help train the AI to handle fallbacks better, you can also use the "acknowledge" or "reject" actions here, denoted by the check and x buttons in the actions section. What this does is tell the AI if the fallback was correct, and it should've reached a fallback there, using the "acknowledge" button, or if the fallback was wrong, and it shouldn't have reached a fallback there and sent the message through, using the "reject" button. Training the AI like this will help the AI be more accurate in the future, and help prevent incorrect fallbacks going forward!