Console walkthrough
Menu
Why a consoleGoals & AIConsoleFlowAboutContactConsole walkthrough

Autonomous Conversion Engine · email, SMS, WhatsApp & RCS

Your goals. Agentic execution—inside one console.

You define what “good” looks like—activation, recovery, revenue, speed to follow-up. ACE pursues that outcome agentically through segments, workflows, the optional Autonomous engine (rules or LLM when enabled), templates, provider routing (email, SMS, WhatsApp, RCS), and campaign runs—then proves progress in Analytics, per-user timelines, and the audit log.

Same surfaces your operators use in the product: nothing extra to learn for the story—only for the work.

This is a walkthrough-friendly product, not a freemium signup wall. Self-host or run privately; we show the console on your terms.

Console walkthroughGoals → execution

Where conversion work usually fragments

Teams don’t fail for lack of tools—they fail because analytics, audiences, routing, and follow-up live in different places with no shared timeline.

  • ESP for sends, spreadsheets for segments, Slack for “did we follow up?”
  • No single ledger tying events → decisions → messages → outcomes
  • Autonomous logic lives in scripts or one person’s head—hard to audit

ACE keeps signals, routing, and execution in one console—so agentic work stays accountable.

Agentic AI · goal-conditioned

Someone states a goal—ACE executes toward it through the console

The human job is intent and guardrails. The engine’s job is to keep acting until the goal advances: who to include, when to nudge, what to say, which channel, and what happens next—without losing the paper trail.

Your goals

  • “Raise 7-day activation from signup.”
  • “Bring back users who went cold after intent.”
  • “Never miss a scheduled follow-up again.”

ACE executes through

  1. 01

    Segments

    Defines who is in scope for the goal.

  2. 02

    Workflows

    Time-based and branching plays that advance the journey.

  3. 03

    Autonomous

    Agentic decisions: next action, timing, channel—rules or LLM-assisted.

  4. 04

    Templates

    Personalized copy merged per user and channel.

  5. 05

    Routing & providers

    Twilio, Resend, console channels, and RCS-style routing to MSISDN.

  6. 06

    Campaigns

    Runs, triggers, and engagement records tied to the goal.

You verify & steer

  • Users / timeline

    Every touch and pending send for a person.

  • Analytics

    Funnel, engagements, and whether the goal is moving.

  • Audit log

    Who changed configuration and when—agentic doesn’t mean anonymous.

What’s in the ACE console

Same navigation as the live app—nothing invented for marketing.

  • Analytics

    KPIs, funnel, engagements by campaign, event-type charts, simulated revenue

  • Providers

    Org connections: Resend, Twilio SMS/WhatsApp, console sinks, RCS console provider

  • Routing

    Per-channel priority for email, SMS, WhatsApp, and RCS

  • Templates

    Multi-channel bodies, merge vars; subject for email and RCS titles

  • Segments

    Rule builder (all/any) + estimates; geo rules for India-first fields

  • Workflows

    JSON graph: phases, delays (e.g. 72h follow-up), linked to campaigns

  • Campaigns

    List & run; create via manual flow or optional AI assistant (feature-flag); manual triggers with location/PIN guards

  • Users

    People directory, per-user timeline, filters when auth is on

  • Import CSV

    Template download + ingest; normalizes phones, WhatsApp, pincode/region

  • Use-case demos

    Scenario playground against live APIs

  • Connectors

    Integration entry points including Shopify webhooks when enabled

  • Audit log

    Category-filterable trail for messaging, auth, campaigns, scheduler, setup

How data moves through ACE

Data and agentic decisions flow through the same primitives you see in the sidebar.

  1. 01

    Ingest

    Activity events, CSV import (template + normalized fields), and connectors such as Shopify webhooks feed the same ledger your segments and workflows read.

  2. 02

    Evaluate

    Goal-conditioned: segments and workflows narrow who matters; Autonomous picks the next best action (rules or LLM) when enabled.

  3. 03

    Route & send

    Provider routing picks Resend, Twilio, console sinks, or RCS defaults—per channel, template, and org config.

  4. 04

    Observe

    Users shows the timeline; Analytics and Audit log show volume, funnel health, and accountability.

Why this isn’t “another campaign builder”

  • Console-first

    Operators live in Analytics, Users, Campaigns, and Routing—not in a drag-and-drop blast UI.

  • Ledger-backed

    PostgreSQL (Prisma) stores users, engagements, scheduled sends, and audit rows—timelines trace to real data, Cloud SQL–ready for production.

  • Agentic, goal-conditioned

    Autonomous closes the loop toward outcomes you define—rules-first, LLM optional—without hiding sends from the audit trail.

  • Your providers

    Wire Twilio, Resend, RCS console routing, and mock channels for dev—swap connections without fork-lifting copy.

What Analytics already surfaces

These are the live metric tiles on the dashboard—useful for reviews, not vanity billboards.

  • Total users · signups · activations
  • Conversion rate (activations ÷ signups)
  • Engagements triggered · emails / SMS / WhatsApp / RCS sends
  • Automations started · pending scheduled sends
  • Simulated revenue (configurable assumption)
  • Event mix by type
  • Engagements by campaign slug
  • Conversion funnel bars

Product preview

Styling matches the dark ACE console: Analytics overview, per-user timeline, and message preview patterns.

Dashboard

app.ace.local/
AnalyticsLive

Performance overview

Signups

128

Activations

42

Conversion

33%

Revenue

$4.2k

Conversion funnel

Signups128
Activations42

Engagements by campaign

  • onboarding drip72
  • winback34

User timeline

app.ace.local/users/u_demo

Jordan Lee

jordan@acme.co · Journey live

  1. Mar 28, 2:04 PM

    Signed up

    user_signed_up

  2. Mar 28, 2:04 PM

    Activation nudge sent

    email · engagement

  3. Mar 28, 2:04 PM

    Pending: follow-up 6h

    Scheduled

    Channel: email · SMS / WA / RCS share this timeline

AI-generated messages

app.ace.local/users/u_demo

Modal · Message preview (as in console)

email

Quick win inside your workspace

Close

Hi Jordan —

Noticed you signed up yesterday. Here’s one action that usually gets teams to “aha” in under 3 minutes: open Settings → Integrations and connect your first event source.

If you want, reply with your goal for this week and I’ll tailor the next nudge.

— ACE · autonomous outreach

Generated for this user’s stage · editable before send

See the console on your data model

Request a walkthrough, or talk through how your goals should map to segments, workflows, and agentic Autonomous behavior in your org.

Schedule walkthroughContact engineering