Skip to main content

Customer Health Summaries in Slack

Use Dana and a playbook to pull customer account metrics from your database and surface them in Slack on demand.
AuthorCognition
CategoryData & Analytics
FeaturesIntegrations, Playbooks, MCP
1

Connect your customer database via MCP

Dana needs access to the database where your customer data lives. Go to Settings > MCP Marketplace, find your database provider, and click Enable.Common setups for customer metrics:
  • PostgreSQL for application data (users, accounts, feature flags)
  • Redshift or BigQuery for analytics warehouse data (usage events, revenue)
  • Snowflake for combined operational + analytics data
If your provider isn’t listed, click Add Your Own and provide a connection string. For production databases, always use a read-only connection string or a database user with restricted permissions.Once connected, verify it works by starting a quick Dana session from the Devin webapp:If Dana returns your table names, your MCP is working. If not, double-check credentials in Settings > MCP Marketplace and ensure your database allows connections from Devin’s IP ranges.
2

Create a customer health playbook

Go to Settings > Playbooks > Create playbook and name it !customer-health — the ! prefix turns it into a macro you can invoke from Slack.Define the metrics Dana should pull for any given account. Keep the playbook general — Dana will figure out the right tables and queries from your schema:You can also use Advanced Devin to generate a customer health playbook tailored to your specific schema and metrics.
3

Run it from Slack

Make sure you’ve connected the Slack integration in Settings > Integrations and that Devin is added to the channel where your team discusses customer accounts.Invoke the playbook using the !dana keyword and your macro name:Dana queries your connected databases, runs the SQL from your playbook, and replies in-thread with a formatted summary:
Acme Corp — At Risk
MetricValueTrend
Monthly Active Users342-8% MoM
Features Used (30d)6 of 10Stable
Open Support Tickets12 (avg 8.2h resolution)+3 vs last month
MRR$4,850Flat for 3 months
Risk factors: MAU declining, no expansion in 3 months, 3 recent tickets about login failures.
You can follow up in the same thread to drill deeper:
4

Make it routine

Once the playbook works well for ad-hoc lookups, consider automating it:
  • Scheduled sessions: Use scheduled Devin sessions to have Dana post a health summary for your top 10 accounts every Monday morning into a #customer-health channel.
  • Pre-meeting prep: Before a quarterly business review, ask Dana to pull summaries for all accounts in a specific tier — @Devin !dana !customer-health Run this for all accounts where plan = 'Enterprise'.