SocialEpochHelp Center
Browse Help Topics
Messaging and translationFor: Employees and administrators

View Messages in the Unified Inbox

Review messages from connected channels in one inbox and confirm the channel and account before responding.

Page contentsBefore you startAggregated chat for centralized viewingFirst confirm that the source account is availableIdentify the source of the message at the aggregation portalHow to continue communication after viewingWhen a platform is not displayedCheck your resultFrequently asked questions

Before you start

  • You have logged in to each platform account you want to view and have access to the corresponding messages.
  • The aggregation chat entrance can be found on the client; whether the platform supports it depends on the currently available login entrance.

Where to find it
Client→Aggregation Chat.

Aggregated chat for centralized viewing #

Aggregated chat puts messages from multiple logged-in platforms into one viewing portal. Examples of data clarity: After logging into your Facebook Messenger and Telegram accounts, you can view messages from these platforms here.

Centralized display does not mean merging customer identities from different platforms into one customer, nor does it mean that all platforms have the same functions. When encountering a contact with the same name, you should still check based on the platform and account, rather than judging based on the display name alone.

First confirm that the source account is available #

  1. Confirm that the platform account you need to view has logged into the client.
  2. Check the account identity and current availability status respectively.
  3. If there is no news on only a certain platform, first go back to the platform account to confirm whether it is normal.
  4. Prepare a known test message as a basis for verification, and then open the aggregate chat.

Just because there is no content in the aggregation list, it cannot be directly judged that the platform has not received the message; the login status, current account and specific session need to be checked separately.

Identify the source of the message at the aggregation portal #

  1. Open the client's aggregation chat.
  2. Review the message list to find the test session you are ready to review.
  3. Combine the platform and account information that can be displayed on the current interface to confirm the message ownership.
  4. Check the sender, message content and corresponding records in the source platform.
  5. If you encounter a session with unclear identity, please return to the corresponding platform account to confirm before proceeding with subsequent processing.

The material does not describe fixed filter, sort, or search buttons, so messages should be positioned as provided by the current interface.

How to continue communication after viewing #

This article supports viewing multi-platform messages in aggregate chats, and does not expand on the operations of replying, forwarding, batch processing or assigning conversations here. When you need to reply, you should use the corresponding platform conversation entrance that is currently confirmed to be available, and confirm the sending account and recipient again.

Don’t assume that modifying customer information, read status, or tags on one platform will necessarily change records on another platform simultaneously. Cross-platform customer merging and status synchronization require additional clear functional basis.

When a platform is not displayed #

First check whether the platform account has been logged in, whether messages can be seen in the corresponding platform session, and whether the current team member has access rights. If the source platform itself cannot see the message, the source issue should be dealt with first.

If the source platform is visible but the aggregation portal is not, record the platform type, account range, test message occurrence time and phenomenon for further verification. When giving feedback, cover the contact identity and chat content, and do not provide platform passwords or login credentials.

Check your result

  • Logged-in target platform messages can be found in aggregate chats.
  • The source platform, account and contact person of the test message can be verified correctly.
  • Cross-platform contacts with the same name are not mistaken for the same customer.

Frequently asked questions

Does it necessarily support all social platforms?

You can't promise that. The current information clearly gives examples of Facebook Messenger and Telegram. Other platforms should be based on the currently available login portals and permissions of the product.

Can I reply directly in the aggregate chat?

This information is only for clear and centralized viewing, and does not expand the reply entry and behavior. Please use the corresponding platform conversation entrance that has been confirmed to be available. It does not infer that all platforms can respond in the same way.

Will customers with the same name on multiple platforms be automatically merged?

The data does not demonstrate automatic merging. The platform, account and actual contact identity should be checked to avoid merging two contacts with the same name.