A public complaint needs an answer that other readers can understand and a private route for details that do not belong under a post. The public acknowledgement and the investigation serve different purposes: one shows that the business has heard the concern; the other establishes what happened.
In Momo Business, Comments handles public threads and Inbox handles private conversations. The Comments reply composer is explicitly public. Treat moving the issue into private support as a deliberate handover, not a change in privacy caused by pressing Reply.
Check that private follow-up is possible
You need access to the connected social account, permission to manage comments and permission to use the relevant Inbox conversation. A colleague creating or assigning tickets also needs the corresponding ticket permissions.
Confirm that the account's private messaging connection works before inviting customers to use it. Supported actions differ between platforms and accounts. A Facebook, Instagram or TikTok filter in Comments does not guarantee that every account supports the same messaging capabilities.
Choose the teammate who will investigate. If public-comment AI replies are enabled, review how this complaint will be handled before another automatic response repeats or contradicts your acknowledgement. Public comments and private messages have separate automation settings.
Read the thread before answering
- Open Comments, choose the account and locate the original post. Use Posts for context or the Comments queue to find work needing attention.
- Read the complaint and the business's existing replies. Check whether the customer already shared the same issue privately.
- Use Assign to give the comment a clear owner. Keep it open while the promised next action still needs attention.
- Prepare a short public response. Acknowledge the reported problem without treating an unverified claim as a confirmed finding.
For a missing-delivery complaint, a suitable response is:
We are sorry you have not received the update you expected. Please message this business account privately with your order reference so our team can check it. Please do not post your phone number or address here.
Replace “this business account” with the verified contact route when that account cannot receive private messages. Do not ask for a mobile-money PIN, password or complete payment credentials in either channel.
Move into the correct Inbox conversation
The current Comments composer sends public replies; it is not a one-click conversion into a private chat. Ask the customer to initiate a message through the supported account, or continue an already available private conversation after checking that it belongs to the right person.
Open Inbox, select the correct account and find the customer's message. Match the reported order or request reference before disclosing account-specific details. Similar display names alone are weak evidence that two records concern the same person.
Confirm what your team will check: “Thank you for messaging us. We will check the dispatch record for this reference and update you here.” Give a time only when the assigned person can meet it. Keep any contact details received privately out of subsequent public replies.
Create one ticket for the investigation
In the conversation's Tickets area, select New or Create first ticket. Create a subject such as “Delivery update needed for example order.” Include the public post link or comment reference, a concise description of the customer's report, the verified order reference and the next investigation step.
Creating the ticket from the conversation preserves that context. Assign the responsible teammate and add suitable labels or priority. Use an Internal Note for findings and colleague instructions. A note such as “Warehouse to verify dispatch; customer update remains with reception” is more useful than copying the whole public thread.
Search for an existing ticket first if the customer has contacted the business several times. Three comments about one delivery usually need one coordinated investigation, not three owners working independently.
Work through an example
A customer comments that a parcel is late. Reception acknowledges the comment, receives the order reference in Inbox and creates a linked ticket. The warehouse colleague verifies that the carrier has the parcel but has not supplied a delivery estimate. Reception updates the private conversation with those confirmed facts and records when the next check is due.
The public thread can receive a brief “Our team is following up with you privately” once that is true. It should not expose the customer's reference or imply that the parcel has arrived. Resolve the comment and ticket according to the work actually completed; their statuses are separate.
Handle problems without losing context
If the private message is missing, check the connected account, assigned-account access and Inbox filters. If a public reply is pending, inspect its result before submitting it again. If a customer posts private details, use the platform's available moderation actions according to your team's policy; resolving a comment does not remove it from public view.
If the investigation resumes, reopen the appropriate record and keep its existing history. For complete note, reply and ownership controls, follow the support-ticket guide and the Comments guide.