Conversations Inbox Dashboard

Purpose

Start here if you are new to this: the Conversations Inbox is where every client channel lands in one thread, so you are never replying to the same person twice in two different places.

At a Glance

• One contact, one thread. Whether they message us by email, Facebook, or live chat, everything from that contact merges into a single conversation.
• The unassigned inbox holds every message no one has claimed yet, so nothing sits unnoticed.
• Group inboxes route to specific teams; the CC and Shea trainers group inbox is one example, and replies land back in that same shared inbox.
• Chat messages are a live channel today, the same as email or Facebook. They are not an upcoming feature.
• Snippets are pre-filled responses that can carry a pricing sheet, the Cave Creek discovery program info, a meeting link, or a knowledge article, and can auto-fill a contact's name or their dog's name when we have it on file.
• Spam is auto-tagged and can be closed without a reply.
• A conversation can become a ticket in the trainers, sales, or support pipeline, whichever fits what the client needs tracked.

Running the Conversations Inbox

1. Check the unassigned inbox at the start of your shift. Claim what is yours before starting anything else.
2. Work the thread, not the channel. A client who messaged on Facebook and then emailed still shows as one thread; reply once, with full context, and close it once it is resolved.
3. Watch your group inbox if you're on one. Replies from a group inbox route back to that same shared inbox automatically, so the whole team stays in the loop.
4. Reach for a snippet instead of typing from scratch. Pull in a pricing sheet, the Cave Creek discovery info, a meeting link, or a template built for exactly this kind of reply.
5. Let personalization tokens do their job. A contact's name, and their dog's name when we have it, should fill in on their own; check that it actually populated before you send.
6. Skip anything auto-tagged spam. Close it out; it does not need a reply.
7. Create a ticket when the thread needs service-side tracking. Pick the pipeline that matches the conversation: trainers for a training question, sales for a program inquiry, support for anything else.

Edge Cases and Troubleshooting

• A client messages on two channels for the same issue. You will still see one thread per contact, so read the whole thread before replying instead of assuming you are seeing the full picture from one channel alone.
• A chat message shows up and it catches you off guard. Chat is a normal, currently-live channel into this inbox; treat it the same as an email or a Facebook message, not as something new or experimental.
• A snippet's content is not what this thread needs. Snippets are pre-filled starting points that can carry a pricing sheet, the Cave Creek discovery info, a meeting link, a knowledge article, or a post-call template. Pick a different one, or write the reply yourself.
• A personalization token did not fill in. The contact's name, and their dog's name, only auto-fill when we have that detail on file. Check before sending rather than letting a blank token go out.

Vendor Reference

• Overview of the conversations inbox: HubSpot's generic walkthrough of the unassigned inbox, snippets, and ticket creation from a conversation. Our group-inbox routing (CC and Shea trainers), our specific snippet content, and our pipeline choices are our own setup on top of that generic mechanic.

Who to Ask

If you are unsure, do not send it or close it yet. Check with your manager first, whether that is a snippet you are not sure is current or a thread you have not fully read.

The contact record behind a thread lives in Contact Dashboard Overview. Once a thread turns into real program interest, walk through how that intake and deal-opening step works.