A subscription works when the product and delivery cadence match how someone actually consumes it. Too much stock, the wrong selection, or unclear delivery timing can undermine an otherwise useful offer.
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.
Match the subscription to the customer’s routine
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
Purchase patterns
Completed orders, product choices, order intervals, returns, and current subscription status.
Subscription terms
Available plans, prices, delivery frequency, shipping charges, pause options, and change deadlines.
Customer preferences
Stated tastes, gift purchases, messaging eligibility, and service conversations.
Fulfillment limits
Current availability, substitutions policy, delivery coverage, and upcoming product changes.
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. Identify plausible fit
Look for repeat purchases and expressed replenishment needs. Separate household consumption from gifts or office buying, and avoid treating an estimated reorder date as a fact.
2. Prepare a relevant offer
Match a current plan to the customer’s known preferences. Explain actual price and cadence without inventing a saving or enrolling anyone automatically.
3. Support the decision
Use approved terms to answer questions about changes, shipping, and product selection. Escalate questions the plan documentation does not resolve.
4. Watch for a mismatch
Review permitted subscription and service records for repeated skips, surplus-stock complaints, or delivery failures. Prepare a helpful adjustment for the customer to consider.
5. Measure retained use
Distinguish new enrollment from a subscription that survives several fulfilled cycles. Record cancellations and their stated reasons so the next offer improves.
A worked example
Illustrative scenario; this is not a reported customer result.
A tea buyer says a monthly box arrives faster than they can use it. Dots finds an available slower cadence, explains it in a draft response, and waits for the customer’s agreement before any authorized system change.
A starter instruction for your dot
Review eligible repeat customers and prepare subscription suggestions using current plans and their stated preferences. Exclude active subscribers from acquisition messages. Flag cadence or service problems for the account owner.
Do not enroll customers, change billing, or alter subscriptions without explicit authorization. Report fulfilled cycles and retained contribution.
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
Track eligible customers, offer acceptance, fulfilled subscription cycles, cancellations, and contribution after shipping, discounts, and refunds.
Compare acquisition messages against an appropriate baseline rather than measuring signups alone.
Keep the handoff clear
Keep commercial consent separate from inferred preference. Purchase history may suggest an offer, but it is not authorization to establish recurring charges or change a delivery schedule.
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
Can Dots automatically subscribe repeat buyers?
A repeat purchase is not subscription consent. The workflow should present a relevant option and rely on an explicit customer enrollment process with approved terms.
What is more useful than raw subscription signup count?
Fulfilled cycles, retention, contribution, refunds, and the reasons people pause or cancel. A signup followed by an immediate cancellation may not add profitable revenue.