proactive-send

Name: proactive-send
Availability: InStock
Author: wiseflow

Publish REPLY_MESSAGE outbound events to the Redis stream for awada customers.

8.4k|1.4k|Updated Apr 24, 2024

Search Tags:#proactive messaging #awada #redis streams #customer follow-up #sales-cs #outbound events

Ready to run

npx skills add https://github.com/TeamWiseFlow/wiseflow --skill proactive-send

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: proactive-send
Source: https://github.com/TeamWiseFlow/wiseflow/tree/main/addons/officials/crew/sales-cs/skills/proactive-send
Command: npx skills add https://github.com/TeamWiseFlow/wiseflow --skill proactive-send

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires ioredis, and includes scripts (resource) components.

What problem does it solve?

It solves the need to follow up with customers proactively by sending messages immediately, without requiring the customer to start a conversation first.

Core Features & Use Cases

Proactive awada outbound messaging: Writes directly to the Redis outbound stream so the message is picked up outside the normal openclaw message handling loop.
Deterministic script interface: Takes the customer identifier and message text as inputs and publishes a correctly structured REPLY_MESSAGE event.
Workflow-friendly follow-ups: Suitable for heartbeat-driven follow-ups, reminders, and business check-ins in sales-cs scenarios (e.g., “Do you have time to review the plan?”).

Quick Start

Run the proactive-send script with your awada customer external user id and the exact follow-up text to publish the outbound message to Redis.

Frequently Asked Questions about proactive-send

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I proactively send messages to customers without waiting for them to initiate a dialogue?▼

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.

How does Redis outbound stream handle proactive customer follow-up messaging?▼

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.

Can I use proactive-send for heartbeat-driven check-ins and sales follow-ups?▼

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.

Do I need ioredis to publish outbound events to the awada platform?▼

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.

What configuration is required before running the proactive-send script?▼

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.

Best way to trigger outbound reminders in a sales-cs workflow?▼

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.