Integrations
Order submission and exceptions queue
Actifai builds the online shops where telecom customers order service, for about a third of North America’s 25 largest telecom companies. I built the integration that submits those orders into each provider’s billing system, and I work with each provider through go-live.
3 Telecom providers live
- Company
- Actifai
- Role
- Built the billing integration and exceptions queue, and worked with each provider and its integration partners through go-live
- Period
- 2026
- Stack
- TypeScript · Node.js · NestJS · PostgreSQL · Datadog · Bun · Vue 3 · Nuxt · REST
“Add to cart” takes you to the store with this project in your cart.
What made it hard
- Two sources of truthOne of the first external APIs on Actifai’s order framework where state lives on both sides: an order lives in Actifai and in the provider’s billing system, and the two have to agree. The provider calls back with each order’s status, which is how we catch a mismatch.
- Plan mappingSingle, double, and triple play orders (internet, TV, and phone, alone or bundled) have to map onto each provider’s billing products.
- Go-live coordinationEach launch lines up the provider and its integration partners, and I gather the requirements with them. A runbook covers each new provider’s credentials and config, plan mapping, and go-live checklist.
When an order fails
A failed submission goes into an exceptions queue in Actifai’s manager portal, where staff fix and resend it, and the provider gets an email when one of its orders is flagged.
A correlation ID on every submission ties logs, Datadog monitors, and the queue to one order, with personal data redacted first.