Integration Desk
Where every partner sits in technical integration, how long they've been there, and what's actually blocking them — without waiting for someone to ask.
Reading the track: five stops from access granted to certified. A hollow ringed stop is where the partner is now — teal if they're moving, rust if they've gone quiet. The number next to it is days in that stop, not days in the deal.
You're on step 3 of 5
First successful API call. Your last 41 attempts returned an error — here's what to do about it.
- ✓Access grantedJul 22 · keys issued to eng@lumenbookings.co
- ✓Sandbox connectedJul 29 · first handshake
- 3First successful callIn progress since Jul 31 · 41 failed attempts
- 4Test suite passed23 checks · not started
- 5Certified and listedReview takes about 5 business days
Reads your last 24 hours of sandbox calls alongside what you paste.
Why this side matters: most stalls aren't hard engineering problems, they're a partner's developer stuck on something answerable in a paragraph and unwilling to open a ticket for it. Self-serve here is what keeps the internal queue short.
Buildable as-is? Roughly. The partner list, type, stage and owner are Salesforce fields that mostly exist already — the new ones are stage-entered-date (to compute aging) and a stall reason. Sandbox call logs are the real dependency, and the AI layer is a prompt over those logs plus the docs, not a model that needs training. Everything shown here is illustrative — no real partner data.