LR
Lead Reply PipelineOperations console
connecting Open CRM ↗
Nothing here sends a real message. The target is a mock CRM running beside this service that reproduces the live platform's URL structure, its three segment cap, the opt-out line it appends to every message, and its opted-out state. The pipeline reaches it the only way the real platform allows: a logged-in browser session driven by headless Chrome.
01

Inbound message

Write a reply as the seller. This lands in the mock CRM exactly as a real inbound text would.

02

Run the pipeline

Every step is idempotent. Run any of them twice and nothing duplicates.

03

Duplicate send guard

Fires five overlapping runs at once, the way a five minute schedule does when one run outlasts its interval. One job row is created and one message reaches the seller. The other four find nothing to claim.

Invariants

checking
STEP 1
Ingest
idle
STEP 2
Generate
idle
STEP 3
Send & verify
idle
0
Jobs
0
Delivered
0
Skipped
0
Failed

Reply queue

0
JobSellerInboundStatusReply sent
loading

Run output

Start at step 1. Pick a conversation, choose a preset, then run all three steps.