Payments · Case Study · October 24, 2026 · 2 min read

Part of Creator Billing Escalations

Built with Fin AI

One standard handoff note across three creator billing procedures, with results as of October 8, 2026

Results to date, as of October 8, 2026. Live since August 27, 2026. This page will be updated as more data comes in.

---

Situation

Three Fin procedures handle creator subscription billing: refund requests, and identity verification for each of two billing systems. Their handoffs to a person were inconsistent. Sometimes a note came with them and sometimes not, so the agent picking up often had to verify the customer again and ask what they wanted.

---

Action

I put one standard handoff note on every exit path, covering verification status, billing system, an account snapshot, what the customer asked for, and why it's escalating. I also fixed a branch that treated verified owners as students, and guarded against two crash bugs that simulations turned up before go-live.

---

Results to date (August 27 to October 8, 2026)

What the numbers say so far

• Most conversations end in a planned handoff, which is the design whenever money would move.
• The 81 "asked for a person" on billing system B are mostly one week. In the week of September 28 the count jumped to 54, against 0 to 4 before. Reading all 54: 38 came from an upstream issue outside the procedure, and it has been handed to the team that owns it.
• In the last two weeks, billing system B resolved more on its own: 33 and then 59 a week, up from 2 to 5. That's two weeks, so it's too early to call a trend.
• Billing system B logged 60 procedure failures in the window, which haven't been investigated yet.

Not measured yet: whether agents still re-verify identity or re-ask intent when they pick up a handed-off conversation. That's what this project was for, and it needs a read of real handed-off conversations.