AI Journey Builder
Use the AI Journey Builder when you know the journey that is broken but do not want to build the workspace by hand. Describe the customer journey, the outcome the team owns and where the process gets stuck.
- Start from a vertical template or describe a custom journey.
- Define stages, blockers, owners, evidence and allowed actions.
- Generate the first operating view for review before publishing it to the team.
Connected sources
Journeys usually break because the context lives across systems. Connect the sources behind the work so the team can see the full picture without replacing the systems that own the data.
- Connect systems such as CRM, case tools, KYC providers, document stores, ledgers and messages.
- Use endpoints, managed imports or file uploads depending on what the source system supports.
- Map source fields to journey context such as customer, owner, status, evidence, blocker and next action.
Operating views
An operating view is the place where the team runs the journey. It brings together the status, evidence, blocker, owner, deadline and next step so people can move the work forward without jumping between tools.
- Use views for queues, exceptions, escalations, evidence collection and approvals.
- Show the source-system record next to the journey context and team-owned actions.
- Write approved updates back to systems of record when the team takes action.
Embedded AI
Embedded AI is useful because the journey is unified first. Once ascentX understands the journey, AI can reason across the data, evidence, owners, blockers and allowed actions.
- Explain what happened across systems, documents, cases and messages.
- Find what is missing, where the journey is stuck and who owns the decision.
- Recommend approved next steps such as requesting evidence, escalating or writing back status.
Agents and MCP
Agents are optional. Teams use the operating view first. When the business is ready, the same journey context can be exposed to agents through MCP so they can reason against modeled work instead of raw system records.
- Expose current journey state, blockers, owners, evidence and allowed actions.
- Keep action boundaries clear with permissions, audit trails and approved writebacks.
- Use MCP for agent-assisted research, summaries, recommendations and controlled actions.
Admin and support
Admins can manage workspaces, sources, permissions, users, billing and audit settings. For account support, contact the ascentX team from your workspace or use the support email below.
- Manage team access, roles, connected sources and workspace permissions.
- Review audit trails for source reads, generated summaries, recommendations and writebacks.
- Email support@ascentx.dev for help with setup, billing or account access.