Kubbly guides
How to turn a reorder reminder into a completed order
A useful reorder reminder starts with a reason the customer might need the product again. It gives them a straightforward way to respond, change the request, and complete the next order. The conversation should preserve the product and purchase context instead of making the customer start over.
Choose a purchase pattern that makes sense
Start with products that have a plausible repeat-purchase rhythm. Coffee and consumable goods behave differently from a jacket or a piece of furniture. Do not put every product into a fixed thirty-day reminder simply because the automation tool offers that template.
Look at the interval between completed purchases, the quantity bought, and the customer's recent activity. Treat those signals as a starting point, not certainty about what somebody needs. A customer who has just reordered should not receive an overdue reminder. A person with an unresolved delivery problem needs help before another sales message.
Make the message useful without forcing a discount
The message can offer convenience: 'Need another bag of the blend you ordered last time?' That is an illustrative prompt, not a claim about a particular customer's preferences. Use the actual product context available to the workflow and the messaging permissions configured for that customer.
Let the reply change the journey. 'Next week,' 'a smaller size,' or 'can I collect it?' should have a useful next step. If the only possible response is a generic checkout link, the customer still has to reconstruct much of the purchase. Sometimes that link is the right design; be clear about the experience you are offering.
Carry the right details into Shopify or WooCommerce
Product names alone are not enough. Confirm the selected variant, quantity, store context, and fulfillment details. The customer may want the same product in a different size or quantity. The connected store remains the source for what can be ordered.
Kubbly agents can complete orders in connected Shopify and WooCommerce systems. That capability is separate from importing customer and order history for audience planning. During setup, confirm both parts: which data informs the conversation and which transaction actions the agent is allowed to perform.
Do not assume that every store configuration includes the same payment method, shipping rules, or post-purchase actions. Walk through the particular customer journey you plan to enable, including the confirmation shown before the order is completed.
Handle the exceptions before increasing volume
Test an item that is unavailable, a changed variant, a customer who asks to stop receiving reminders, and a conversation that pauses before completion. Check how unresolved questions reach the team. A reminder is useful only when the response can be handled reliably.
Also test a repeated request. The team needs to know whether the previous attempt created an order before the workflow tries again. Set the intended behavior with your implementation team and verify it in your own configuration. These are evaluation requirements, not a claim that every integration handles every exception identically.
Measure the repeat purchase
Track the number of eligible customers, delivered messages, replies, completed orders, cancellations, and unsubscribes separately. Include messaging and offer costs when assessing the economics. A higher response rate alone does not tell you whether the workflow produced more profitable repeat purchases.
Where practical, compare the eligible audience with a suitable holdout over a period that matches the purchase cycle. Keep campaign attribution separate from causal lift. The goal is to learn which reminders help customers reorder, then improve the timing and conversation from that evidence.
Start with one complete workflow
Choose one product family, one intended channel, and one clear order path. Check the source data and enabled actions, agree on the review and handoff process, and run through the journey before expanding.
Kubbly connects customer insight, campaign execution, and BrandRep conversations. Start with the workflow you want to prove, then use the integration review to establish how it works in your store.