Each module solves a problem worth solving on its own. What makes them different is that they share one memory of your customer — so the second one you switch on is cheaper, faster, and better than the first.
Conversational cross-sell & recommendations
Every conversation becomes a buying moment, with suggestions that read live browsing and cart signals rather than static rules.
Automated support across messaging
Close out the repetitive majority of tickets instantly and route the rest to a human with full context intact.
AI voice agents
A phone agent that listens, understands intent, and actually completes the task.
Commerce data platform
Unify first-party data across your stack and query it in plain English.
Loyalty & referral engine
Turn repeat buyers into a distribution channel.
Agentic commerce protocol layer
Make your stack legible to the agent-to-agent internet before your competitors do.
Custom copilots & automation
For the workflows no off-the-shelf product covers.
If you are trying to work out where to start, find your bottleneck in the middle column.
| Module | Start here if | Primary metric it moves | Also known as |
|---|---|---|---|
| Uplift | Conversations convert but baskets stay small | Average order value · attach rate | Attach, Basket |
| Resolve | Your support queue is mostly the same dozen questions | Auto-resolution rate · cost per contact | Desk, Frontline |
| Dial | Calls go unanswered, or your IVR is losing people | Containment · task completion | Voice, Echo |
| Atlas | Every number takes three weeks and two analysts | Time to answer · decision quality | Core, Graph |
| Loop | Acquisition costs rise and repeat rate is flat | Repeat purchase rate · referral revenue | Orbit, Bond |
| Mesh | You want to be transactable by third-party shopping agents | Agent-sourced sessions · checkout conversion | Bridge, Relay |
| Forge | The workflow that matters most has no product for it | Task success rate · time per workflow | Studio, Workbench |
"Also known as" lists internal working names you may see in early documentation and pilot agreements.
We do not publish a price list, because the honest number depends on which modules you run, your conversation and call volume, and how much integration work your stack needs. A list price would be wrong for most of the people reading it.
What we will do is give you a specific figure quickly. A scoping call is usually enough.
Tell us the bottleneck and we will tell you which module moves it — including if the answer is none of them yet.