Abandoned cart: a Telegram reminder, no developer needed
A customer fills a cart and leaves. An hour later Oxta checks whether an order appeared and, if it did not, messages them. You can open every reminder: who got it, when, and what came back.
How it works
Three steps that run on their own, every time your CRM or shop reports a new cart.
- The cart is abandoned
Your CRM or a form on the site passes the cart contents and the customer’s contact to Oxta. No contact means the run stops at step one — and the history says so.
- Wait an hour, then check
The pause is yours to set: an hour, three, a day. Oxta then asks the CRM whether an order arrived from that customer. If it did, the run ends quietly.
- Message the customer
A message with the product name and a link back to the cart goes to Telegram, to email, or to any chat that exposes an open API.
What you need to connect
The scenario lists the access it needs before you install it — nothing to hunt for.
- The CRM or shop the carts come from: KeyCRM, SalesDrive, Sitniks, Horoshop, WooCommerce or your own database.
- The channel you write to: a Telegram bot or a mailbox.
- Optionally, your own wording and your own delay before the reminder.
What a run looks like
The useful part is not the reminder itself but being able to look at each one. Oxta keeps the whole run, not a “done” tick.
Open any case from yesterday and you see what the CRM sent at 14:02, what was in the cart, whether an order had appeared by the 15:02 check, the exact text that went out, and what Telegram answered. If delivery failed, the reason is there.
Before you switch it on, the scenario does a dry run: every step executes on real data but nothing is sent to anyone. You see what the customer would have received, then you decide.
What it costs
One abandoned cart is one run, however many steps the scenario has. The free tier gives 1,000 runs a month, for good, without a card. For most shops that covers the first few months.
Services that meter every single step charge several times more for the same scenario — we put the numbers on a separate page.
The essentials, briefly
Will a customer be reminded after they have already ordered?
No. Right before sending, Oxta asks the CRM again whether an order exists for that customer. If it does, the run ends without a message.
How many reminders are sent?
One by default. You can add a second one a day later — it is another step in the same scenario, so the price per run does not change.
What if the CRM stops returning the cart contents?
Oxta notices that an expected field went missing and tells you. Customers do not get messages with an empty product list.
Can I see what would go out before it does?
Yes — that is the dry run. The scenario executes on real data but sends nothing and writes nothing.