CHATBOTS

Reorder Assistant: Scheduled Replenishment Nudge

On a daily schedule, finds customers whose consumable purchase is due to run out.

CategoryChatbots
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily schedule fires
  • ActionFind customers past their reorder window in PostgresPostgreSQLPostgres
  • LogicDedupe recently nudged or open-thread customers
  • ActionResolve historical SKUs to active products and pricesPostgreSQLPostgres
  • ActionOpen proactive replenishment message in IntercomIntercomIntercom
  • OutputLog nudge to Postgres for next-run dedupePostgreSQLPostgres

What it does

Predicts when a repeat customer is about to run out of a consumable and reaches out first. Each day it scans order history for items past their typical reorder interval and starts a personalized Intercom conversation pre-loaded with the right SKUs and quantities.

When to use it

For subscription-adjacent brands selling consumables on a predictable cadence who want to lift repeat revenue without forcing customers into a rigid subscription.

How it works

  1. 1A daily schedule triggers the flow.
  2. 2The flow queries Postgres for customers whose last purchase of a consumable SKU is now past its average reorder window.
  3. 3Logic dedupes anyone already nudged in the last cycle or with an open reorder thread.
  4. 4For each eligible customer it resolves the historical SKUs to current active products and prices.
  5. 5It opens a proactive Intercom conversation with a tailored replenishment offer and reorder summary.
  6. 6The flow logs the nudge back to Postgres so the dedupe check works on the next run.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect IntercomConversations, contacts, articles.
  2. 2
    Connect PostgresAny Postgres URL — query, write, migrate.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.