🧠Smart Recommendations

Which Provider
Should You Use?
We'll Tell You — Based on Real Data

When you have multiple providers for the same service, OutboundIQ analyzes your actual performance data and tells you which one to use right now — with confidence scores and reasons.

The Multi-Provider Dilemma

Smart companies don't rely on a single API provider. They have backups:

  • Payments: Stripe + Adyen + Square
  • Identity: Onfido + Jumio + Veriff
  • Banking: Plaid + Tink + TrueLayer
  • Email: SendGrid + Mailgun + SES

But when Provider A starts failing, how do you know Provider B is better right now?

🤔

"Stripe is having issues... should we switch to Adyen?"

Stripe87% success ↓
Adyen??? success
Square??? success

Without OutboundIQ, you're guessing.

Data-Driven Provider Selection

Our recommendation engine considers multiple factors to give you the best provider for your specific situation.

📊25%

Your Success Rate

How often does each provider successfully process YOUR requests?

20%

Response Latency

Which provider responds fastest from your infrastructure?

📈15%

Stability Score

How consistent is performance? Fewer spikes = higher score.

🚨25%

Status Page Health

Current operational status from their official status page.

⚠️15%

Active Incidents

Penalty for providers with ongoing reported incidents.

🎯100%

Weighted Score

All factors combined into a single actionable recommendation.

SDK Response: client.recommend('payment-processing')

{
  "decision": {
    "use": "adyen",
    "confidence": 0.92,
    "confidence_label": "high",
    "action": "proceed",
    "reason": "Adyen has 99.2% success rate vs Stripe's 87.3%. Stripe has active incident."
  },
  "recommendation": {
    "provider": "Adyen",
    "score": 94.5,
    "success_rate": 99.2,
    "avg_latency_ms": 245,
    "status": "operational"
  },
  "alternatives": [
    {
      "provider": "Square",
      "score": 88.2,
      "success_rate": 97.8,
      "status": "operational"
    },
    {
      "provider": "Stripe",
      "score": 65.1,
      "success_rate": 87.3,
      "status": "degraded",
      "warning": "Active incident affecting payments API"
    }
  ]
}

Easy to Integrate

🐘 PHP / Laravel

$client = new OutboundIQ\Client($apiKey);

$recommendation = $client->recommend('payment');

if ($recommendation->action === 'proceed') {
    $provider = $recommendation->use;
    // Route to recommended provider
} else {
    // All providers degraded
    // Queue for retry or notify user
}

JavaScript / Node

import { recommend } from '@outboundiq/core';

const { decision, alternatives } = await recommend('payment');

if (decision.action === 'proceed') {
  const provider = decision.use;
  // Route to recommended provider
} else {
  // Handle degraded state
}

Real-World Use Cases

🔄 Automatic Failover

Call recommend() before each API request. When your primary provider degrades, automatically route to the next best option — with zero manual intervention.

Result: 99.9% effective uptime even when individual providers fail

📉 Cost Optimization

Use recommendations to route low-priority traffic to the cheapest provider that meets your latency requirements, saving on API costs.

Result: 15-30% reduction in third-party API spend

📊 Vendor Evaluation

Use historical recommendation data to evaluate which providers perform best for YOUR specific use case, informing contract negotiations.

Result: Data-driven vendor selection and better contract terms

Stop Guessing Which Provider to Use

Let data drive your provider selection. Start using smart recommendations today.