RudderAI Best Practices
Learn best practices for using RudderAI effectively, including onboarding strategies, usage patterns, and security recommendations.
2 minute read
This guide provides best practices for using RudderAI effectively and securely.
Usage
- Test the assistant with read-only queries to familiarize yourself with its responses
- Use threads for complex issues to maintain conversation context
- Provide feedback (by clicking 👍 or 👎 on the response) to help improve the assistant’s accuracy
- Report any security or privacy concerns immediately
Be specific
Ask clear, specific questions with details and context:
- Good: “Show me event volume for the iOS source in the last 24 hours”
- Less effective: “How are my events being sent?”
Provide context
Include relevant details:
- Good: “Why are
Order Completedevents failing to reach Amplitude with error code400?” - Less effective: “Why are my events failing?”
Use natural language
You do not need special syntax:
- Good: “What transformations are connected to my web source?”
- Also good: “List all transformations for the web source”
Upload supporting materials in Slack
When using RudderAI in Slack, include screenshots or error logs when troubleshooting issues:
- Take a screenshot of the error or issue
- Upload the image to Slack
- Mention the assistant and ask about the error
- RudderAI will analyze the image and provide guidance
See RudderAI in Slack for more on using the assistant in Slack.
Security considerations
This section covers security considerations for using RudderAI securely.
Monitor Slack channel access
RudderAI is deployed in your designated Slack channel and is accessible to all members present in it.
Make sure to periodically monitor channel membership and remove users who no longer need access.
Limitations
Understand the following limitations to use RudderAI effectively:
- RudderAI cannot modify sources, destinations, transformations, or any other workspace configuration — all operations are read-only.
- RudderAI’s scope is limited to your production workspace.
- In Slack, RudderAI can only respond in the designated channel and is accessible to all members present in it. See RudderAI in Slack for details.
- In the RudderStack dashboard, organization admins control access using the Enable RudderAI toggle. See RudderAI in Dashboard for details.
