Architecture
What you configure, and what we run.
The setup the customer owns, and the loop RevReply runs against every event.
The setup block
Each customer defines their own programs, objectives, sentiments, and per-step toggles.
Everything else runs from there.
Dynamic fields
Customer-defined catalogs
- Programs12 active
- ObjectivesSign up · Create · Launch
- Sentiments8 custom labels
- Pipeline stages5 stages, mapped to CRM
- Channel profiles3 profiles
Per-step toggles
How each step behaves
- Follow-up context allowances
- Reply handling toggles
- Channel allow-list
- Persona profile assignment
- Sentiment routing
Runtime loop
Same loop for every customer. Reads the setup block on every event.
01 · Trigger→02 · Interrupt→03 · Context→04 · Decide→05 · Act→06 · Writeback
Why this architecture
Generic spine, custom edges, compounds with use.
Generic at the spine
Every customer runs the same six-phase loop. We invest in making the loop strong because every tenant benefits at once.
Custom at the edges
What makes Riipen's setup different from a freight broker's is the configuration block — programs, objectives, sentiments, toggles. The customer owns that.
Compounds with use
Every loop deepens the per-customer learned data: which channels work for which buyers, which sentiments map to which deals, which signals actually move replies.