A cart left behind is a signal, not a confirmed request for a discount. The shopper may have bought elsewhere on your site, encountered an error, or needed a product detail that was missing.
This is a proposed workflow to configure and test with your business. It does not assume that Dots already has access to your sales systems.
Recover the purchase without duplicating messages
Define the result, the records the agent should use, and who owns the decisions. Keep the opportunity state in a shared tracker your team can inspect, with stable IDs, current sources, and the next action.
Prepare the information Dots needs
Cart and order data
Stable cart ID, items, timestamps, checkout state, and completed orders across the relevant channels.
Customer eligibility
Contact availability, messaging permissions, exclusions, and any existing recovery sequence.
Current offer
Live stock, price, delivery options, promotion rules, and product information.
Support context
Known checkout problems, recent customer questions, and unresolved order issues.
Verify app access before assigning work. Configure recurring tasks explicitly. Define action permissions before sending or changing records.
If a needed connection is unavailable, use an approved export for research and draft preparation. Keep source timestamps visible and require a current system check before an action depends on price, availability, or status.
Build the agentic workflow
1. Check that the purchase is unfinished
Match the cart to current orders before creating a follow-up. Suppress recovered carts and reconcile against any native recovery automation already running.
2. Identify a supported reason to help
Use observed errors or actual customer questions where available. Do not claim to know why a shopper left when the data only shows inactivity.
3. Prepare the next useful message
Answer a known product or delivery question, or provide an approved way to resume checkout. Use discounts only under a defined policy.
4. Recheck immediately before sending
Validate stock, price, contact eligibility, and order status again. A queued message can become wrong between preparation and delivery.
5. Learn from the result
Track recovery, returns, unsubscribes, and discount cost. Stop when the customer buys, declines, or becomes ineligible; investigate repeated checkout problems separately.
A worked example
Illustrative scenario; this is not a reported customer result.
A shopper asks whether a bag fits a particular laptop and then leaves checkout. Dots finds the verified dimensions and drafts a useful answer. It checks for a later order before the message enters the approved send queue.
A starter instruction for your dot
Review eligible abandoned carts using our approved export or connection. Reconcile them against completed orders and existing recovery messages. Draft helpful follow-ups using current product and delivery facts.
Do not invent an abandonment reason or add discounts. Flag stock changes, checkout errors, and missing contact permission. Measure recovery net of discounts and returns.
For a repeating check, add a time, time zone, end date, and where results should arrive. Ask for confirmation that the schedule was saved. Define which exceptions deserve a notification and when the workflow should stop.
Measure the commercial result
Use a comparable holdout group where practical to estimate incremental purchases. Report contribution margin, message volume, returns, and customer opt-outs alongside recovered revenue, rather than crediting every later purchase to Dots.
Keep the handoff clear
Verify that your storefront connection exposes both current cart state and order state. If it does not, start with analysis and reviewed drafts; a browser session alone does not establish reliable cart event handling.
Begin with a small, reviewable pilot. Inspect the records and actual outcomes before expanding its scope. Give the agent enough authority to complete the agreed work, with clear ownership of exceptions.
Talk to Looski about this workflow. We can help map the data, integrations, decisions, and measurement before implementation.
Frequently asked questions
Does Dots have a native abandoned-cart integration for every store?
No universal storefront integration is established here. Verify the tools available to your account, or begin with an approved export and a reviewed draft workflow.
Should every abandoned cart receive a coupon?
No. Some shoppers need information or a functioning checkout. Define eligibility and margin limits, and test whether an offer adds profitable purchases rather than discounting orders you would have received anyway.