Hootsuite Social Marketing study materials
Hootsuite Social Marketing study resources

Hootsuite Social Marketing: Nest Inbox and Customer Care

Hootsuite Social Marketing · Work through your exam, one topic at a time.

All guide sections

Nest Inbox and Customer Care

Nest is the unified inbox where comments, direct messages, mentions and reviews from connected channels arrive. The exam tests triage design, routing and assignment, reply standards, and how response metrics are actually defined.

Inbox structure

  • Views and filters are the backbone: by network, team, tag, assignment status or keyword. Build one saved view per use case - complaints, sales leads, spam - rather than one giant stream.
  • Status hygiene matters: unassigned, assigned, resolved. Without it, everything looks urgent and nothing is owned.
  • Saved replies handle repeat questions; they must be personalised before sending, or they read as a bot answering the wrong question.
  • Tags capture topic and sentiment, and become the cohort you report on later.

Public versus private

  • Answer publicly when the answer helps other customers; move to direct message when account details, order numbers or personal data are involved.
  • Hiding a comment and deleting it are different moderation actions with different visibility consequences.
  • Every escalation path needs a named owner and a time threshold, not just a policy statement.

Measurement

  • First-response time and resolution rate depend on business hours and time zone settings. A four-hour SLA measured across a weekend is a definition choice, not an objective fact.
  • Volume by tag drives staffing decisions and reveals product issues a single reply can never fix.

Worked example

A delivery outage produces 200 complaints in an hour. Build: a view filtered to "late" OR "refund" across Facebook and X; an auto-assignment rule to the care team; a holding reply that acknowledges the issue and links to the status page; a tag such as outage-; an escalation rule to the operations owner. Afterwards, report first-response median for that tag separately from baseline. Reasoning: the tag creates a measurable cohort after the incident, and the holding reply protects the SLA while the real answer is drafted.

Traps

  • Asking for order numbers in a public reply.
  • Deleting criticism rather than responding to it.
  • Measuring response time without defining business hours and time zone.
  • Sending a saved reply that answers a different question than the one asked.
  • Assuming all channels are connected - an unconnected inbox silently misses messages.