Onboarding Guide

Getting Maximum Value from Sonus

Your First 30 Days: A practical roadmap to transform raw data into actionable intelligence.

The Goal

What success looks like

By Day 30, your team shouldn't just be connected to Sonus—you should be relying on it to flag anomalies before your stakeholders do.

Success means moving from "data ingestion" to "signal detection." You'll have a stable pipeline running against your primary warehouse, a library of three to five critical metrics actively monitoring for drift, and a workflow established for sharing insights with the broader organization.

Week 1

Connect and Configure

Establish your foundation. This week is about getting data flowing and your team on board.

Connect Data Source

Link your Snowflake or BigQuery instance. We recommend starting with your highest-traffic tables to ensure meaningful baselines.

Invite Team Members

Add your analysts and stakeholders. Assign roles based on access needs to ensure security and accountability.

Define 3 Signals

Select your North Star metrics. Examples: Revenue, Customer Churn Rate, or Server Latency. Sonus will watch these daily.

Week 2

First Insights

Review the system's output and tune its sensitivity.

Log into Sonus on Day 14 to review your first Narrative Report. This digest explains exactly what happened to your selected metrics over the last two weeks. Look for the "Anomalies Detected" section to verify the system is flagging real issues.

Tip: Adjust your Signal Sensitivity thresholds. If you're seeing too many false positives, increase the confidence interval. If you're missing critical trends, lower it.

Week 3

Team Adoption

Scale usage by integrating Sonus into your daily workflows.

  • Share Reports: Publish your Narrative Reports to Slack or Teams using our native integrations. This keeps the team informed without manual email threads.
  • Set Alerts: Configure email or SMS notifications for high-priority anomalies so key stakeholders are alerted immediately.
  • Train a Champion: Identify your CS or Ops Lead to take ownership of the dashboard. They can refine the signal library and troubleshoot setup issues.
Week 4

Optimize

Refine your monitoring strategy for long-term efficiency.

Review the Signal Quality metrics in your dashboard. Archive any signals that are consistently producing low-value alerts or noise. This keeps your signal-to-noise ratio high.

Schedule your first recurring report. Set it to run every Monday morning so your leadership team starts every week with a clear view of what has changed in the business data since the previous week.

Resources

Need more help?

Documentation

Deep dive into integration guides and API references.

Read Docs

Video Tutorials

Step-by-step walkthroughs for common setup scenarios.

Watch Videos

Support Center

Contact our technical team for dedicated assistance.

Get Support
Success Call

Ready to level up?

Schedule a 30-minute success call with your Customer Success Manager to review your progress and plan for Month 2.