Skip to main content

​
Overview

Chat Follow-ups let you ask questions about your charts directly within Slack or Microsoft Teams. By tagging @chartcastr in a pulse thread or channel, you can get contextual answers about your data without leaving your conversation.

​
How It Works

When you tag @chartcastr in a channel where the bot is present, it analyzes the context of your message and provides an intelligent response inline.

​
Thread Context

Chartcastr is context-aware. When you tag it within a thread attached to a Pulse notification:
  • It knows which pulse you’re asking about
  • It understands the specific chart data in that pulse
  • It has access to External Context and User Notes linked to that source
  • It remembers the conversation history in the thread
Example: 
[Chartcastr Pulse in #sales-reports]
📊 Weekly Revenue: $125,000 (+12%)
AI Summary: Revenue exceeded targets driven by enterprise upgrades...

--- Thread ---
You: @chartcastr Which specific customers drove the increase?
Chartcastr: The increase was primarily driven by 3 enterprise 
accounts upgrading to annual plans: Acme Corp (+$15K), TechStart 
(+$12K), and Global Industries (+$8K). These were all Q4 contract 
renewals that moved from monthly to annual billing.

You: @chartcastr How does this compare to last quarter?
Chartcastr: Q4 upgrades are tracking 23% higher than Q3. Last 
quarter had 5 major upgrades totaling $28K, while this quarter 
already has 8 upgrades totaling $45K with 3 weeks remaining.

​
Channel Questions

You can also ask general questions in channels where Chartcastr is a member: 
You: @chartcastr What's our current MRR?
Chartcastr: Your current MRR is $487,500 as of today. This is up 
2.3% from last month. The main growth driver has been the new 
Starter plan tier which contributed $18K in new revenue.

You: @chartcastr Show me all active pulses
Chartcastr: You have 12 active pulses:
• Weekly Revenue → #exec-reports (Mondays 9am)
• Daily Active Users → #product-team (Daily 8am)
• Campaign Performance → #marketing (Fridays 4pm)
...and 9 more. View all in your dashboard: https://chartcastr.com/admin/pulses

​
Supported Platforms

Full support for tagging @chartcastr in:
  • Pulse threads for contextual follow-ups
  • Channels where Chartcastr is a member
  • Direct messages to the Chartcastr app
The bot understands thread context and can reference the specific pulse data when replying.

Slack Integration

Learn more about setting up Slack
Coming Soon — Microsoft Teams follow-up support is in development alongside the Teams integration.
When launched, you’ll be able to:
  • Tag @chartcastr in Teams channels
  • Ask follow-ups in pulse threads
  • Get contextual answers about your data

Teams Integration

View Teams integration status

​
What You Can Ask

​
In Pulse Threads

  • “What caused this spike?”
  • “Break down the top contributors”
  • “Which segments performed best?”
  • “Show me the underlying data”
  • “How does this compare to last week?”
  • “What’s the MoM trend?”
  • “Compare this to Q3 performance”
  • “How are we tracking against goal?”
  • “Explain what this metric means”
  • “Why is this important?”
  • “What should we do about this?”
  • “Summarize the key takeaways”
  • “Who should I notify about this?”
  • “Should we schedule a follow-up meeting?”
  • “Create a task to investigate the drop”
  • “Alert the team if this drops below X”

​
General Questions

  • “What’s the status of [source/connection]?”
  • “Show me my active pulses”
  • “When is the next pulse sending?”
  • “Help me create a new connection”
  • “Why didn’t my last pulse send?”
  • “What’s our [metric] for [time period]?”

​
Best Practices

When asking about a specific pulse, reply in the pulse thread. The AI automatically knows which chart you’re referring to.
Good: “@chartcastr What was our revenue last Tuesday?”Vague: “@chartcastr show me numbers”
The AI maintains conversation history in threads. You can reference previous answers:“@chartcastr Expand on that last point about churn”
Request specific formats for better readability:
  • “@chartcastr Show this as a table”
  • “@chartcastr Give me bullet points”
  • “@chartcastr Keep it brief”

​
Privacy & Thread Access

  • Only users who can see the pulse can tag @chartcastr in the thread
  • The bot respects your workspace permissions
  • External context is only used if the source has linked documents
  • Thread conversations are stored for context but not shared across workspaces

​
Limitations

Follow-up messages count toward your AI Chat daily limits based on your plan:
PlanMessages Per Day
Free2
Starter10
Pro100
EnterpriseUnlimited
Chartcastr only responds when tagged. It won’t proactively message channels or start conversations.
The AI can only access data and connections within your Chartcastr workspace.

​
Troubleshooting

  • Ensure @chartcastr is invited to the channel
  • Check that the bot is online in your workspace
  • Verify you haven’t hit your daily message limit
  • Try re-inviting the bot if issues persist
  • Make sure you’re in a pulse thread (not just a regular channel message)
  • Be specific about which source or metric you’re asking about
  • The bot may ask clarifying questions if context is unclear
  • The AI can only access sources and connections you have permission to see
  • External context documents must be properly linked to the source
  • Some historical data may not be available depending on retention settings

​
Example Workflows

​
Weekly Standup

[Monday 9am - Weekly Revenue Pulse in #sales]
You: @chartcastr What's the breakdown by product tier?
Chartcastr: Enterprise: $85K (68%), Pro: $28K (22%), Starter: $12K (10%)

You: @chartcastr Any concerning churn signals?
Chartcastr: No immediate concerns. Churn is at 2.1%, below the 3% 
threshold. However, 2 enterprise customers have contracts expiring 
this month worth $24K total. I recommend proactive outreach.

You: @chartcastr Draft an alert for the team
Chartcastr: 📋 Draft alert:
"🎯 Weekly Revenue: $125K (+12%)
⚠️ Action needed: 2 enterprise renewals at risk ($24K)
✅ Next steps: Review expiring contracts"

Reply "send" to post this to the channel.

​
Incident Response

[Alert Pulse in #engineering]
📉 Error Rate Spike: 5.2% (normal: <1%)

You: @chartcastr When did this start?
Chartcastr: Error rate began increasing at 14:32 UTC, approximately 
45 minutes ago. First spike coincided with deployment #2847.

You: @chartcastr Which endpoints are affected?
Chartcastr: Top 3 affected endpoints:
1. /api/v2/checkout (2.1% error rate)
2. /api/v2/payments (1.8% error rate)  
3. /webhooks/stripe (0.9% error rate)

You: @chartcastr Is this related to the payment service issues?
Chartcastr: Based on the error patterns and your linked incident 
response doc, this matches the symptoms of the payment gateway 
timeout issue. The checkout and payment endpoint errors both 
involve 504 gateway timeouts.

​
Next Steps

Tagging @chartcastr

Learn how to interact with the bot directly in Slack channels.

Set Up Slack

Connect Slack to start using follow-ups.