👋 New to Recommendations? Learn how Recommendations work first.
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 only runs a fresh analysis once a week (early Monday morning) — so each upload or sync should happen often enough to be included in that cycle.
With the Guest Feedback Signal, Opus needs at least 50 reviews per month per location to generate quality Recommendations. If a location is generating fewer reviews than that, its Recommendations may be less frequent or less reliable — worth keeping in mind when you're reviewing coverage across locations.
Build a strong training library
Keep your training library organized and current, so Recommendations can point to something you already have instead of drafting new content every time.
When Opus does draft 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 — right after Opus's Monday analysis is a natural rhythm, since that's when most new Recommendations appear.
Start with high-priority Recommendations. See Taking Action on Recommendations for how to read it.
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 exactly what pattern Opus found and why.
Review each Recommendation before taking action, and dismiss the ones that aren't relevant to your operation. This keeps your board focused on what matters — and you can always move a dismissed Recommendation back to your inbox later if it becomes relevant.
Don't stop at "assigned." Once you've acted, check Recommendations Impact Tracking after about two weeks to see whether the issue is actually improving. If it's not, assign additional training or a follow-up action rather than letting it sit.
Get the right people involved
Recommendations doesn't have to be an Admin-only habit.
Admins have access by default, but Managers can be granted 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 visibility into their Recommendations.
➡️ Once you've built these habits, keep an eye on Recommendations Impact Tracking to confirm they're paying off.
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 runs a fresh analysis once a week (early Monday morning). For CSV uploads, add new data regularly so each upload feeds into the next analysis.
How much guest feedback do I need for reliable Recommendations?
With the Guest Feedback Signal, Opus needs at least 50 reviews per month per location to generate quality Recommendations. Locations with less volume may see fewer or less reliable 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.