By Tina17 Nov,2026
Messenger customers often start with a short question attached to a post or image. A useful reply connects that message to the correct item before it makes a claim. A generic sales script can sound efficient while making the buyer explain the same thing twice.
These original examples are starting wording, not official Meta templates or customer transcripts. Use them for individual service enquiries through the permitted workflow. Replace brackets with verified facts and check current requirements before any separate outbound campaign.
1. Identify the item without creating unnecessary work
| Situation | Reply to adapt | Check |
|---|---|---|
| Item reference unclear | “Which item are you asking about? Please send the product reference or identify it in the image so I can check the right one.” | Ask only if the existing context is insufficient |
| Availability question | “Which [variant] and quantity do you need? I will check that option.” | Do not claim live stock without a current source |
| Bundle contents | “The [exact bundle] includes [verified items]. The [accessory] is [included or separate].” | Match the promoted variant |
| Product comparison | “The main difference is [verified difference]. For your stated need, this means [relevant explanation].” | Avoid unsupported suitability claims |
When the post context already identifies the product, answer directly. Repeatedly requesting a link the system can already see makes a prepared reply feel careless.
If an image cannot be interpreted, be honest about the missing detail. Do not say “I checked the photo” when neither the person nor the assistant has done so.
For an expired-looking promotion: “Which offer or post are you referring to? I will check its dates, participating items and conditions.” The current product page may not explain what the buyer previously saw.
For a requested discount: “The currently approved offer for [item] is [offer]. I can check whether another approved option applies.” Remove the review sentence if the business has no such process.
For conflicting information: “The offer you mentioned differs from the current information for this item. I am checking the discrepancy with [responsible team] and will update you by [time].” Confirm that the team and update commitment actually exist before sending.
Do not add invented stock pressure, a false countdown or a guaranteed result to make the message more persuasive. A support reply should help the buyer decide from accurate information.
| Situation | Reply to adapt | Next action |
|---|---|---|
| Order needs identification | “Please provide the relevant order reference through [approved route] so we can check the correct order.” | Follow identity verification requirements |
| Dispatch confirmed | “The verified dispatch status is [status]. The latest available delivery information is [separate information].” | Keep dispatch and arrival distinct |
| Tracking has stalled | “The latest event is [event] on [date]. I am checking [specific issue] with [owner]. We will update you by [time].” | Assign and complete the investigation |
| Deadline-sensitive buyer | “You need it by [date]. The current estimate is [estimate], but we cannot guarantee arrival by that date.” | Do not hide uncertainty |
Do not reveal order details merely because a Facebook display name resembles a customer record. Verify the relevant identity through the approved process. Never request payment passwords or full card credentials in chat.
For a wrong or damaged item: “I am sorry about the problem with [item]. Please identify the affected part and share relevant photos if available. We will compare them with the order and review the next step.” Do not ask for unrelated documents to complete a standard script.
For a refund delay: “The verified status is [status]. The next action is [action], owned by [team]. We will update you by [achievable time].” Separate a request under review, an approval and a payment processed. They are not the same event.
For a disputed answer: “Thank you for pointing out the difference. I will check the source rather than repeat the earlier answer. The point we need to resolve is [specific issue].” Preserve the original claim so the reviewer can investigate it.
If the complaint begins publicly, move only the necessary private details into an appropriate private route. Do not post order information in a public comment to demonstrate responsiveness.
Use: “A teammate needs to review [specific decision]. I have passed on [accurate summary] and the details already supplied. We will update you by [time].” If no immediate coverage exists, state when review resumes instead.
The internal note should identify the item or order, facts checked, unresolved issue and receiving owner. Saying “escalated” is not sufficient if nobody knows who must act next.
Store replies under task names such as “offer discrepancy” and “tracking investigation update”. Keep the source, applicable Page or shop and review owner attached to the content. Archive outdated offers and duplicate versions.
If these replies feed AI in Duoke or another supported workspace, test whether the assistant has enough context to fill the fields correctly. Missing information should cause a clarification or transfer, not an invented value.
Review a few used templates each week during rollout. Look for repeated buyer questions and unnecessary requests for information already present. The best improvement may be deleting a sentence rather than adding another script.

Email:[email protected]
Address:6/F MANULIFE PLACE, 348 KWUN TONG ROAD, KOWLOON, Hong Kong, 999077