How can we explain the sudden 20% decrease in API calls for ADVANCE.AI's identity verification service last week?

Introduction

The sudden 20% decrease in API calls for ADVANCE.AI's identity verification service last week is a critical issue that demands immediate attention. This significant drop could impact revenue, customer satisfaction, and our market position. I'll approach this problem systematically, focusing on identifying the root cause, validating hypotheses, and developing both short-term and long-term solutions.

Step 1

Clarifying Questions (3 minutes)

• Looking at the timing, I'm thinking this could be related to a recent product update. Have there been any changes to the API or its documentation in the past two weeks?

Why it matters: Recent changes often correlate with sudden metric shifts. Expected answer: Yes, there was a minor API update. Impact on approach: If yes, we'd focus on the update's impact; if no, we'd look at external factors.

• Considering user segments, I'm wondering if this decrease is uniform across all clients. Can you provide a breakdown of the API call reduction by customer type or industry?

Why it matters: Helps identify if the issue is global or specific to certain users. Expected answer: The decrease varies across segments. Impact on approach: Segment-specific issues would require targeted solutions.

• Given the nature of identity verification, I'm curious about any recent regulatory changes. Have there been any new compliance requirements or legal shifts in our key markets?

Why it matters: Regulatory changes can significantly impact usage patterns. Expected answer: No major regulatory changes. Impact on approach: If yes, we'd need to assess our compliance; if no, we'd focus on other factors.

• Thinking about system health, I'm concerned about potential technical issues. Have there been any reported outages, increased error rates, or performance degradation?

Why it matters: Technical problems can directly cause API usage drops. Expected answer: No significant technical issues reported. Impact on approach: If yes, we'd prioritize technical fixes; if no, we'd explore user behavior changes.