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
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 ask Devin to generate a customer health playbook tailored to your specific schema and metrics.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 RiskYou can follow up in the same thread to drill deeper:Risk factors: MAU declining, no expansion in 3 months, 3 recent tickets about login failures.
Metric Value Trend Monthly Active Users 342 -8% MoM Features Used (30d) 6 of 10 Stable Open Support Tickets 12 (avg 8.2h resolution) +3 vs last month MRR $4,850 Flat for 3 months
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-healthchannel. - 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'.
