How to Track Product Requests From Instagram and WhatsApp

To track product requests from Instagram and WhatsApp, record the product or variant, what the customer requested, when they asked, the relevant buying condition, and a reference to the original conversation. Count repeat follow-ups separately from independent demand. Review the register regularly with the team that can act on it.

This workflow can start in a restricted spreadsheet. Outlined can support the conversation and customer-context side of the process; the worksheet is an editorial method, not a claim that the application includes a dedicated restock campaign system.

Decide which requests belong in the register

Include clear requests for an unavailable item, another size or colour, a product variation, or information needed to decide on a purchase. Keep general praise and unrelated product mentions in separate categories.

Write inclusion examples before collecting data. “Please make this in green” is a variation request. “The green packaging looks nice” is not necessarily interest in a green product. A customer asking whether an existing order can change colour has an order-service task that should not automatically become new demand.

Read surrounding messages and images where authorised. If the product cannot be established, preserve the request as unmatched instead of assigning a convenient catalogue item.

Use this tracking worksheet

Keep addresses, phone numbers, payment information, and unnecessary personal details out of a general demand worksheet. Source references should preserve the original workspace's access restrictions.

Set a counting rule

A useful starting rule is one request per verified person, product or variant, request type, and review window. Retain additional follow-ups as activity linked to that request. If identity across channels is uncertain, report channel-level totals and possible overlap.

For a fictional example, four messages in one WhatsApp conversation asking about the same restock represent one request with several follow-ups. A later request for a different size can be a separate product-variant request. State the rule so another reviewer can reproduce your total.

Do not count agent suggestions as customer requests unless the customer actually expresses interest. Keep withdrawn interest or corrected product matches traceable rather than silently accumulating stale demand.

Capture buying conditions

A request becomes more useful when it includes the condition that matters: delivery date, destination, size, quantity, or acceptable alternative. Ask only what is needed to help the customer. Avoid creating a survey burden during a simple support exchange.

Record “needed before the wedding date” as a time constraint, not a guaranteed purchase. If the item becomes available after that date, the original interest may no longer be relevant.

Review with merchandising and CX

Group requests by product and variant, inspect the strongest examples, and disclose unmatched cases. Compare with current stock, past sales, supplier constraints, margins, and campaign exposure. Decide whether the next step is better product information, a stock investigation, or further research.

Shopify documents product-interest and product-detail topic labels, illustrating that these are distinct conversation themes. Your demand register needs a more specific evidence rule than a broad topic label alone.

Keep follow-up separate from tracking

Do not promise a future automated notification unless you have a supported process, the required permission, and current channel eligibility. Capturing a request is not consent to marketing. Ask your channel owner to confirm the applicable outreach rules before contacting customers later.

A successful first review produces a small set of decisions with owners, not an inflated forecast. Use the merchandising review guide to translate the register into a bounded commercial discussion.