All Categories Quick Tips Quick Tip: How to Set Up a Secondary AI Fallback in AskSpot

Quick Tip: How to Set Up a Secondary AI Fallback in AskSpot

What is the Secondary AI Fallback?

The Secondary AI Fallback feature in AskSpot ensures your chatbot stays online and responsive—even if your primary AI provider experiences downtime or your API key encounters any issues. This feature allows your bot to automatically switch to a backup AI model so there's no interruption in service.


Why It Matters

If your chatbot gets a lot of traffic or is used for critical tasks (like customer support, lead generation, or form processing), any AI downtime can hurt your user experience and performance. With Secondary AI Fallback, AskSpot automatically routes your chatbot to a second AI engine if the primary one fails.


How It Works

You can set a fallback AI at two levels:

  1. Chatbot-level settings – Assign specific API keys to individual chatbots.

  2. Global settings – Use API keys saved at the platform level for all bots.

If the primary AI (e.g., OpenAI) fails, AskSpot will automatically switch to the backup AI (e.g., Claude, Gemini) to keep your chatbot running without disruption.


How to Set It Up

Step 1: Add Your API Keys

  • Go to Settings > API Keys

  • Add the keys for any AI services you want to use (OpenAI, Claude, Gemini, etc.)

Step 2: Open Your Chatbot

  • From the dashboard, click on the chatbot you want to configure

Step 3: Configure AI Settings

  • Go to Chatbot Settings > AI Configuration

  • Choose your Primary AI

  • Then, select a Secondary AI Platform from the dropdown

You’ll only see options here if you’ve added API keys for multiple providers.

Step 4: Save Your Settings

  • Click Save and you’re done!


Example

  • Primary AI: OpenAI (ChatGPT)

  • Secondary AI: Claude (Anthropic)

If OpenAI’s API is unavailable or fails to respond, AskSpot will automatically switch to Claude to handle user requests without interruption.


Best Practices

  • Always test your fallback AI setup to ensure it behaves as expected.

  • Keep your API keys updated and monitor usage limits on both providers.

  • Use this feature on high-traffic or business-critical bots to ensure 24/7 uptime.

Was this article helpful?

Thanks for your feedback!