# Dashboard Console

Analyze and act on your Stripe data using a single conversational interface.

The Stripe Dashboard Console lets you query data, manage customers, and so on. Type your question, and Console learns from your conversations and retains context over time. You can ask follow-up questions about results, or act on what you find without starting over. It uses a combination of persistent business context, conversation history, and reusable skills:

- **Business context:** Define business-specific terms and thresholds that Console applies automatically going forward.

- **Conversation history:** Corrections and refinements from past conversations improve accuracy without the need to teach the Console again.

- **Skills:** Save repeatable processes as skills that Console can use to answer questions and take actions.

Console uses generative AI supported by a third party. Always review and verify its responses, because they might contain mistakes.

## What Console can do

To start a new conversation, select **New conversation**. Each conversation maintains its own context, so you can run multiple queries independently. To revisit a previous conversation, open the conversation history from the sidebar.

> #### Feedback
> 
> To share feedback on a Console response, type `/feedback` into a conversation. Your feedback helps improve Console’s accuracy.

### Query and diagnose data 

Console lets you ask questions and get structured, sourced answers from your Stripe data. Among other things, it can chart revenue, find customers with failed payments, and analyze subscription churn. When you ask a diagnostic question—such as what caused a revenue change—Console returns a list of potential root causes.

### Take action on results 

After diagnosing a problem or identifying an opportunity, you can act on the results directly. Actions include retrying failed payments, issuing refunds, creating coupons, adjusting subscriptions, and drafting customer communications.

## Console use cases 

The following use cases show how Console handles common tasks, from answering questions and diagnosing issues to taking action.

### Investigate a revenue drop 

1. **Ask:** “Why did revenue drop 12% this week?”
1. **Diagnose:** Console shows root causes, including enterprise downgrades, increased churn among small and mid-sized businesses, and a spike in failed payments, along with the dollar impact of each.
1. **Get more details:** “Select the failed payments cause.”
1. **Review:** Console shows 19 recoverable payments totaling 4,200 USD. You retry them with a 10% discount offer.

### Recover failed payments 

1. **Ask:** “Find failed payments over 500 USD from the last 7 days”.
1. **Review:** Console returns a table of results with customer details, failure reasons, and amounts.
1. **Retry:** “Select the recoverable payments and retry them.”

### Analyze subscription churn 

1. **Ask:** “Show me customers who churned last month because of price.”
1. **Review:** Console returns a table of matching customers and churn details.
1. **Refine:** “Show their usage in the 3 months before churn.”
1. **Diagnose:** Console reveals that most were power users, suggesting price sensitivity rather than low engagement.

### Build a report 

1. **Ask:** “Chart MRR and churn for Q4 compared to Q3.”
1. **Review:** Console shows a chart of MRR and churn for Q4 compared to Q3.
1. **Refine:** “Add a column for net revenue retention.”
1. **Review:** Console updates the chart to include net revenue retention.

## Join the waitlist