How to Use the Inbox Health View in Mydrop to Monitor Community Signals

By the end of this tutorial you will have a filtered Health view in Mydrop that surfaces community and operational signals, shows applied filter counts, lets you search results, and gives clear next actions to reassign, escalate, or update rules.

Before you start

Checklist:

• You can access the main navigation and open Inbox.
• You have permission to view queues, rules, and Health.
• You know which profiles or queues you want to check.
• There are recent or live messages in the inbox to test filters.

1. Open the feature

2. Click Inbox in the main navigation.

3. Inside the Inbox interface, choose the Health view tab (located alongside Inbox and Rules).

4. Use the chevron icon to expand or collapse any section you need to see. Expanding shows signal groups and counts; collapsing hides details you do not need.

5. Set up the basics

6. At the top of the Health view, pick the surface you want to inspect (for example, a specific social surface).

7. Choose platform if you need to narrow results (select the platform or leave it broad).

8. Select a profile or a queue to focus on messages tied to that account or team queue.

9. Set Assignee to me, unassigned, or allAssignees depending on whether you want items assigned to you, items nobody owns, or all items.

10. Set Priority to allPriorities or pick a specific priority to limit results to urgent or low-priority signals. What to expect: applied filter counts should update as you change selections. If appliedFiltersCount increases, your filter set is active.

11. Add search and fine filters

12. Use the search box to find keywords, handles, or text inside signals.

13. Open Filters and toggle values for surface, platform, profile, assignee, and priority to refine results further.

14. Confirm the Filters label shows the number of applied filters. This tells you filters are active and which scope is returned. What to expect: search results and filtered lists should refresh immediately and show matching signal items.

15. Inspect items and act

16. Click any signal item from the list to open its context pane. The pane shows the message thread, associated profile, and links to the related queue or rule.

17. Review context, then choose an action:

    • Reassign: change the assignee to a team member or queue.
    • Mark handled: mark the signal as handled or resolved.
    • Escalate: apply the appropriate escalation action or add a note for follow up.

18. If you see routing gaps or repeated missed messages, click Rules to open the Rules view and inspect routing or response rules. What to expect: after reassigning or marking handled, item status or assignee should update in the Health list.

Verification checks

• The Health list shows only items matching your selected surface, platform, profile, assignee, and priority.
• The applied filters count is visible and increments when filters are active.
• Search returns matching items and highlights hits in context.
• Reassigned items show the new assignee; handled items move out of the active Health list or change status.
• Rules link opens to rule details so you can edit routing when needed.

Common mistakes to prevent

• Leaving restrictive filters active (platform, surface, or profile), which hides signals.
• Overlooking assignee state (me versus unassigned) when testing routing.
• Expecting historical-only data to appear; confirm live messages exist before testing.

Conclusion Use the Health view to get a focused list of community and operational signals, confirm applied filters and search results, and take immediate actions to reassign, escalate, or open Rules to fix routing gaps. This workflow reduces missed messages and helps teams prioritize replies.

You will open the Health view and prepare filters so the view surfaces community and operational signals to prioritize replies, fix routing gaps, and reduce missed messages.

Step 1: Open the feature

1. From the main navigation, click Inbox.

   • This opens the inbox interface that contains Inbox, Rules, and Health views.

2. In the inbox header, click the Health tab.

   • Health appears alongside the Inbox and Rules tabs. Clicking Health switches the view to health-specific signals.

3. Use the section chevrons to expand or collapse areas.

   • Look for a small chevron icon next to section headers. Click it to expand a list of signal items or collapse it to hide details.

4. Confirm you are on the Health view by checking the page labels.

   • The header should read Health and the UI will show filters and a search field labeled "search".
   • You should see grouped signal rows (community or operational items) rather than the standard inbox message list.

5. If you do not see Health, verify permissions and try again.

   • Health is only visible where you have access to inbox queues and rules. If the tab is missing, ask an admin to confirm your Inbox and Rules permissions.

Step 2: Set up the basics

1. Open the filters panel and locate these controls: "surface", "platform", "profile" (or queue), "assignee", and "priority".

   • These labels are visible in the inbox header or filter menu. Use them to focus the Health view on the signals you care about.

2. Choose a surface.

   • Click "surface" and select either a specific surface or "allSurfaces" to include everything.
   • Narrowing by surface avoids showing unrelated operational signals.

3. Choose a platform.

   • Click "platform" and select the social network of interest (or "allPlatforms").
   • Selecting the correct platform prevents platform-specific messages from being missed.

4. Select a profile or queue.

   • Click "profile" and pick a profile or queue tied to the team you are monitoring.
   • If you want every queue, leave profile set to "allProfiles" or the equivalent option.

5. Set assignee state.

   • Click "assignee" and choose "me" to show items assigned to you, "unassigned" to surface items without owners, or "allAssignees" to see everything.
   • Remember: testing should include "unassigned" to find routing gaps that cause missed messages.

6. Set priority.

   • Click "priority" and pick a level or "allPriorities" to include all.
   • Choosing a high-priority filter surfaces items that need immediate action.

7. Check the applied filters count.

   • Look at the badge or number next to "filters" (the applied filters count). It should update to reflect the filters you selected.
   • If the count does not change, re-open the filter menu and reapply selections.

8. Use the search box for quick queries.

   • Type a keyword into the "search" field and press Enter. Search filters the current Health results by text so you can find specific signals fast.

9. Verify the Health list updates immediately.

   • After each change, the list of signal items should refresh to match the chosen surface, platform, profile, assignee, and priority.
   • Confirm the visible items now match your intent (for example, only items for the selected profile and platform appear).

10. Save or note the setup for repeat use.

• If your team uses the same filters regularly, remember the combination or take a screenshot. This reduces time reconfiguring when monitoring shifts.

Verification checks (quick)

• The header shows Health and a "search" field.
• The filters badge next to "filters" shows the applied filters count.
• The list only contains items for the selected surface, platform, profile/queue, assignee, and priority.
• Expanding a section with the chevron reveals individual signal items.

These steps ensure the Health view is open and focused so the team can start prioritizing replies, identify routing gaps, and reduce missed messages.

Step 3: Add the content or settings

You will use search and filters to surface the specific community and operational signals you need to act on.

Checklist before starting:

• Confirm the Health tab is open.
• Confirm you have the correct profile or queue selected.
• Confirm live messages exist to test results.

1. Open the filter bar at the top of the Health view.
2. Choose Surface. Click the Surface dropdown and pick the platform surface(s) you want to inspect (for example, all Platforms or a single surface). Expanding the chevron shows more surface options; collapse it when done.
3. Choose Platform. Open the Platform dropdown and select one or more networks if you need network-specific signals.
4. Narrow by Profile or Queue. Click Profile or Queue and pick the profile or queue to limit results to the account or inbox that matters.
5. Set Assignee. Click Assignee and choose Me, Unassigned, or All assignees to filter items by ownership. If you expect unassigned signals, pick Unassigned to avoid hiding them.
6. Set Priority. Use Priority to include all priority levels or a specific priority. If nothing appears, verify you did not leave an overly restrictive priority selected.
7. Use Search. Type a keyword or handle into the Search box and press Enter. Search filters the current Health results; it does not replace the other filters.
8. Confirm applied filters count. Look for the applied filter count near the Filters control. It should increment as you add or remove filters. If it remains zero after selecting filters, clear and reapply them.
9. Inspect items. Click any signal item in the list to open its context panel. The panel shows the conversation, timestamps, and links to the related queue or rule if available.
10. Follow related links. From the item panel, click the queue or rule link to open the inbox view or Rules view. Use those links to examine routing and response history.
11. Save a view if available. If the Health view supports saving or pinning filter sets, save the combination you will reuse to avoid repeating setup.

Quick checks to avoid mistakes:

• If results are empty, clear all filters and rerun the search to confirm live messages exist.
• If you expected unassigned items but see none, verify Assignee is set to Unassigned, not Me.
• If counts seem low, confirm Platform and Surface are not restricting the view to a single channel.

Step 4: Review the workflow

You will verify items, take next actions, and confirm that rules or routing changes are effective.

1. Verify result counts. Check the list header for item counts or badges. The count should reflect the filtered set you applied.
2. Spot operational signals. Scan for messages that show delayed replies, repeated routing failures, or high-priority mentions. Each item opens into its context panel when clicked.
3. Reassign an item. From the item panel, choose Assignee and set to another team member or Unassigned to route for triage. Confirm the assignee label updates in the list.
4. Mark handled. Use the action to mark an item as handled, replied, or resolved according to the available action labels. Confirm the item either updates its status in the list or disappears from active results based on your filters.
5. Escalate when needed. If an item requires escalation, use the escalation option in the panel or add a note and assign to the escalation queue. Verify the queue or assignee change appears immediately.
6. Check rule links. For items that indicate routing problems, click the rule link in the panel to open Rules. From Rules, confirm whether a rule exists or needs editing.
7. Fix a routing gap. If a missing or incorrect rule is identified, open Rules, update the rule or create a new rule, then return to Health.
8. Re-run the Health filters. After making rule or assignee changes, clear and reapply filters or refresh the view to confirm items are routed differently or no longer appear in problem lists.
9. Compare with Inbox. Open the Inbox tab for the same profile or queue to ensure messages now appear in the correct queue and assignee.
10. Final verification checklist:

• Applied filters count matches the number of filters you set.
• Search returns expected items.
• Reassigned items show the new assignee immediately.
• Marked-handled items update or leave the active Health list.
• Items linked to rules open in Rules and reflect any edits after refresh.

If any step does not produce the expected result, clear filters, confirm you have permission to view queues/rules, and repeat the verification. After these checks, the Health view should show the community and operational signals you need, with clear next actions to reassign, escalate, or update rules.

Troubleshooting and next steps

After troubleshooting, the Health view should display the expected community and operational signals, show updated applied filter counts, let you search results, and present clear next actions to reassign, escalate, or update rules.

Checklist before troubleshooting

1. Confirm Inbox permission and access to the Health tab.
2. Verify relevant profiles or queues are selected.
3. Make sure at least one live message exists to test against.

Step-by-step fixes

1. Clear restrictive filters

   • Click the filters menu and choose the default options: surface = allSurfaces, platform = allPlatforms, assignee = allAssignees, priority = allPriorities.
   • Check that the applied filter count (appliedFiltersCount) drops to zero or shows the expected number.
   • Result: more signals appear and missing items are no longer hidden by a filter.

2. Confirm assignee state

   • Use the assignee selector and try me, unassigned, and allAssignees.
   • If items appear under unassigned but not under me, reassign one item to yourself to test routing and visibility.
   • Result: the item moves to the chosen assignee and appears in your filtered view.

3. Use search to scope results

   • Type a keyword in the search box (search) that matches a known message or handle.
   • Observe that results narrow and appliedFiltersCount increments for search.
   • Result: search lets you find signals by text so you can inspect related rules or queues.

4. Expand collapsed sections

   • Click the chevron next to any collapsed section to expand it.
   • Expand both queue summaries and signal groups to view individual items.
   • Result: hidden items become visible and counts refresh.

5. Inspect an item and act

   • Select a signal to open its context panel.
   • From the panel, reassign the item, mark it handled, or follow any visible rule or queue link to open Rules.
   • Result: assignment and status changes should reflect immediately in Health and Inbox.

6. Compare Health with Inbox and Rules

   • Open the Inbox view and then the Rules view from the same interface.
   • Confirm the same item appears in Inbox if it remains outstanding.
   • If a routing gap is suspected, open Rules and view the rule linked from the Health item.
   • Result: misrouted or unhandled messages can be traced to rule conditions you can edit.

Common problems and quick remedies

1. No items after filters reset
   • Confirm live messages exist. If none do, create a test message or wait for live traffic.
2. Counts differ between Health and Inbox
   • Widen filters and re-run search. Check assignee and priority filters.
3. Reassign or handled action not reflected
   • Refresh the view. If still unchanged, confirm you have permission to modify assignments.

Next steps after fixing issues

1. Update or create a rule in Rules for messages that repeatedly miss routing.
2. Reassign recurring problem signals to a queue or owner to reduce missed messages.
3. If you need a task reminder, create a Calendar reminder for follow-up or handoff.
4. Repeat this check weekly or after major profile or rule changes to confirm continued coverage.

Verification checklist

1. Health shows items matching your search and filters.
2. appliedFiltersCount reflects active filters and search terms.
3. Reassigned items appear under the correct assignee in both Health and Inbox.
4. Rules view links open and show the rule responsible for routing the signal.

Conclusion

Use the troubleshooting steps above until the Health view reliably surfaces the expected signals, applied filter counts update correctly, searches return relevant items, and actions (reassign, mark handled, open Rules) reflect immediately. After verification, update any routing rules or assignee defaults that caused gaps so the team loses fewer messages.