proactive-send

To proactively send messages without waiting for customer initiation, this Skill publishes a REPLY_MESSAGE event payload directly to the Redis outbound stream, bypassing the normal message handling loop. It resolves the target lane from your configuration to deliver the outbound message.

Redis outbound stream handles proactive messaging by picking up the REPLY_MESSAGE event payload written by the script outside the standard openclaw processing loop. This mechanism ensures immediate delivery of outbound follow-ups and reminders.

Yes, you can use proactive-send for heartbeat-driven check-ins and sales follow-ups. It is specifically designed for sales-cs scenarios, taking the customer identifier and text as inputs to publish correctly structured outbound events.

Yes, you need the ioredis dependency to publish outbound events to the awada platform. The script relies on it to connect to Redis and write the REPLY_MESSAGE payload to the resolved outbound stream.

Before running the proactive-send script, you must configure the platform and lane settings in your ~/.openclaw/openclaw.json file. The script reads this configuration to resolve the correct Redis outbound stream for publishing the message.

The best way to trigger outbound reminders in a sales-cs workflow is running the proactive-send script with the customer external user id and exact follow-up text. It publishes a deterministic REPLY_MESSAGE event directly to the Redis stream.