Superkabe protects your outbound email infrastructure in minutes. Connect Google Workspace, Microsoft 365, or SMTP mailboxes — or wrap the protection layer around Smartlead / Instantly / EmailBison / Reply.io. Every lead flows through validation → health gate → ESP-aware routing → post-send monitoring → 5-phase auto-healing.
Getting Started
Set up Superkabe to protect your outbound infrastructure in minutes
What is Superkabe?
Superkabe is an AI-powered cold email platform with native deliverability protection. Draft sequences with AI, send across unlimited mailboxes (Google Workspace, Microsoft 365, or any SMTP provider), validate every lead, and let the protection layer auto-pause, reroute, and heal your senders in real time. You can also run Superkabe in Protection Mode — connecting your Gmail, Microsoft 365, or SMTP mailboxes to send natively with the same safety layer.
Every lead that enters Superkabe flows through the same pipeline: email validation (syntax, MX, disposable, catch-all, plus MillionVerifier API on risky leads), the GREEN/YELLOW/RED health gate, ESP-aware mailbox routing, and continuous post-send monitoring with a 5-phase auto-healing recovery pipeline for any mailbox that degrades.
What Superkabe Does
How It Works
When a lead enters Superkabe — from a Clay webhook, API call, or CSV upload — it passes through a multi-stage pipeline before reaching your sending platform:
- Email Validation: Every email is checked for syntax, MX records, disposable domains, and catch-all detection. Growth and Scale plans additionally verify risky leads through the MillionVerifier API. Invalid emails are blocked here — they never reach your sender.
- Health Gate: Each lead receives a GREEN (safe), YELLOW (proceed with caution), or RED (block) classification based on validation score, domain health, and engagement signals. RED leads are blocked.
- Routing: GREEN and YELLOW leads are matched to campaigns using your routing rules (persona + minimum score). YELLOW leads are distributed with per-mailbox risk caps — no more than 2 risky leads per 60 sends per mailbox.
- Native Send: Validated, routed leads enter Superkabe's sequencer for dispatch through your connected mailboxes. Lead status changes to ACTIVE when enrolled in a sequence.
- Monitoring: Once campaigns are running, Superkabe monitors mailbox health every 60 seconds — bounce rates, SMTP/IMAP connectivity, DNS authentication (SPF, DKIM, DMARC), and domain reputation.
- Protection: When a mailbox exceeds bounce thresholds, Superkabe auto-pauses it and removes it from campaigns on the platform. The correlation engine checks if the root cause is the mailbox, the domain, or a bad campaign before deciding what to pause.
- Healing: Paused mailboxes enter a 5-phase recovery pipeline: Pause (cooldown) → Quarantine (DNS verification) → Restricted Send (conservative warmup) → Warm Recovery (graduated volume) → Healthy (re-added to campaigns). Each phase has specific graduation criteria.
- Alerts: Every significant action — pauses, rotations, healings, threshold breaches — triggers a Slack notification with context about what happened and what Superkabe did.
Quick Start
1. Create an Account
Sign up at superkabe.com/signup and choose your pricing tier.
2. Connect Your Sending Platform
Navigate to Mailboxes and connect your sending mailboxes via OAuth (Gmail or Microsoft 365) or encrypted SMTP credentials:
Settings → Integrations → Add API Key3. Set Up Clay Webhook
In Clay, configure your webhook to send enriched leads to Superkabe:
https://api.superkabe.com/api/ingest/clayInclude header: x-organization-id: YOUR_ORG_ID
Include fields: email, firstName, lastName, company, persona (job title), lead_score. See the full Clay integration guide for detailed setup.
4. Choose System Mode
Superkabe operates in 3 modes:
- OBSERVE:Logs events without blocking (testing)
- SUGGEST:Provides recommendations without automated action
- ENFORCE:Fully automated protection (production)
5. Monitor Your Dashboard
View real-time stats on:
- Active leads by state (held, active, paused)
- Mailbox health and bounce rates
- Domain-level aggregations
- Execution gate blocking reasons
What Happens Next?
Once integrated, Superkabe will automatically:
- Validate every incoming lead (syntax, MX, disposable, catch-all, MillionVerifier for risky leads)
- Block invalid and disposable emails before they reach your sender
- Classify leads as GREEN/YELLOW/RED and route them to campaigns by persona and score
- Enroll validated leads in Superkabe sequencer campaigns for native dispatch
- Monitor mailbox health every 60 seconds (bounce rates, connectivity, DNS)
- Auto-pause mailboxes when bounce thresholds are breached
- Correlate failures across mailboxes, domains, and campaigns to find root cause
- Rotate in standby mailboxes to keep campaigns sending
- Heal paused mailboxes through the 5-phase recovery pipeline
- Send Slack alerts for every significant infrastructure event
💡 Pro Tip
Start in OBSERVE mode for your first week to understand baseline metrics before enabling ENFORCE mode for production protection.
Frequently Asked Questions
How long does Superkabe take to set up?
+
Most teams are sending or protected within 15 minutes. Connect your sending platform (Gmail OAuth, Microsoft OAuth, SMTP credentials, or a Smartlead/Instantly/EmailBison API key), upload a lead list or wire up a Clay webhook, and the protection layer is active on the first send.
Do I need to change my existing Smartlead/Instantly setup?
+
No. Superkabe runs in Protection Mode by connecting via API and webhook — your existing campaigns, mailboxes, and sequences stay exactly where they are. Superkabe observes every send and can pause/reroute via the platform's API when thresholds are breached.
Can I send natively from Superkabe instead?
+
Yes. Connect Google Workspace, Microsoft 365, or custom SMTP mailboxes directly, and Superkabe runs your campaigns end-to-end — AI sequence generation, variant testing, ESP-aware routing, and the same protection layer on top.
What happens when a mailbox exceeds the bounce threshold?
+
It auto-pauses and enters the 5-phase recovery pipeline: Pause → Quarantine (DNS verification) → Restricted Send (15 clean sends) → Warm Recovery (50 sends over 3 days) → Healthy. Each phase has deterministic graduation criteria, not timers.