What Changed
From a Single Provider to a Resilient Gateway

The aim was a support chat that keeps working whatever happens upstream. Here is how SupportGenie differs from a direct, single-provider integration.

User Research

Single Image
How We Work

How we got there

1
Catalogued what actually breaks

Outages, rate limits, latency spikes and price changes: the specific failure modes that had already hit similar integrations.

2
Built the gateway first

Started with the request and response layer both providers would sit behind, before writing any routing logic.

3
Added routing, then failover

Health-based provider selection came first; failover without losing context came once routing was proven stable.

4
Instrumented cost from day one

Token and spend logging went in alongside the routing logic, not after someone asked for a cost report.

5
Forced real outages in staging

Killed the primary provider mid-conversation repeatedly until failover held up without manual intervention.

6
Wrote the on-call runbook

An automatic switch still needs someone to understand it at 2am, including what’s safe to ignore.

Software & Tools

The Tools Behind the Innovation