Social CRM uses selected social interactions in customer relationship work. Use the actual message and the proposed contact link to decide what a colleague needs for the next conversation.
Start with the interaction
Keep the sender’s question and where it appeared. Identify what the person is asking someone to do before choosing a customer record.
HubSpot documents assigning an existing or new contact from its social inbox, with Marketing Hub Professional or Enterprise and Social permissions.
For a confirmed match, HubSpot lists Instagram comments, Facebook comments, X retweets and X quote tweets on the contact timeline, depending on the profile. Segmentation and scoring have different lists.
Review a suggested contact
Sprout’s Salesforce integration guide asks users to verify a suggested Contact or Lead match and continue searching when it is wrong.
A fictional shoe-repair handoff
Imagine a fictional shoe-repair shop receiving “Is my pair ready?” A suggested contact shares the sender’s first name. The shop has not confirmed the association or which pair the question concerns.
| What is known | Still unresolved | Chosen handling |
|---|---|---|
| Question received | Pair readiness unknown. | Repair desk checks the request. |
| Contact suggested | Link to sender unconfirmed. | Review before associating. |
| Repair desk chosen | No answer recorded. | Keep the question open. |
Pass the question with its unresolved association, rather than presenting the suggested record as confirmed history.
Keep the next handler visible
The same guide describes creating a Case from a selected inbox message. It also notes that cases without a linked Related Contact are not viewable in Sprout.
Check that the receiving colleague can find the request. Creating a case and replying to the sender are separate actions.
For the wider conversation history, inspect the CRM record. Keep the sender’s question distinguishable from subsequent staff notes.