✅ Before you start: New to Recommendations? Learn how Recommendations work first.
Table of Contents:
Keep your Signals fresh and complete
Recommendations are only as good as the data behind them.
Connect every Signal that applies to your business. The more Signals feeding Opus, the sharper and more complete your Recommendations become.
If you're not using an integration, upload a CSV of your guest feedback regularly. Reviews synced through an integration update daily, but Opus analyzes that feedback once a week, on Sunday. A CSV upload with new feedback starts its own analysis within a few minutes.
With the Guest Feedback Signal, Opus raises an issue only when at least 5 different reviews point to it, and each analysis reads reviews from the past 90 days. Locations with few reviews may see fewer Recommendations, so keep that in mind when you compare coverage across Locations.
Build a strong training Library
Keep your Library organized and current, so Recommendations can point to something you already have instead of drafting new content every time.
When Opus drafts something new through Create training, or proposes changes to existing content through Update existing content, review and refine it before publishing. See Taking Action on Recommendations for how each action works.
Triage your board regularly
A Recommendation only creates value once someone reviews it.
Check your Inbox on a regular cadence. Early in the week is a natural rhythm, since most new Recommendations appear after Opus's Sunday analysis. Check Analysis history to see when the last one ran.
Start with High priority Recommendations. See Inside a Recommendation for how to read one.
If you manage multiple brands or Locations, use the Brand and Locations shown on each Recommendation to route it to the right owner.
Act deliberately, then follow through
Read the issue description and Sample reviews before acting. They explain what pattern Opus found and why.
Review each Recommendation before taking action, and click Dismiss recommendation on the ones that aren't relevant to your operation. This keeps your board focused, and you can open a dismissed Recommendation later and click Move to inbox if it becomes relevant.
Assigning training isn't the finish line. Once it's live with your team, click Start measuring impact and pick the day the training went live. Check back after about two weeks to see whether the issue is improving. If it's not, assign additional training or a follow-up action.
➡️ Learn more: Recommendations Actions & Impact Tracking: how Opus tracks whether your training is working.
Get the right team members involved
Recommendations isn't only for Admins.
Admins have access by default, and Managers can be given access through the Manage Org Integrations permission. See Getting Started: Recommendations for details. If Location-level follow-through matters to your operation, consider giving the Managers closest to the affected Locations access to Recommendations.
FAQ
Which Recommendations should I review first?
Start with high-priority Recommendations — they reflect the trends affecting the most reviews or locations, so they typically offer the biggest impact.
How current does my data need to be for accurate Recommendations?
Reviews sync daily from connected integrations, and Opus analyzes new feedback every Sunday. A CSV upload with new feedback starts an analysis within a few minutes, so upload regularly if you don't use an integration.
How much guest feedback do I need for reliable Recommendations?
Opus raises an issue only when at least 5 different reviews from the past 90 days point to it. Locations with fewer reviews may see fewer Recommendations.
Should I dismiss Recommendations that don't apply to my operation?
Yes. Review each Recommendation before acting, and dismiss the ones that aren't relevant. This keeps your board focused on what matters.