Adobe Coworker
5 min
Overview
Adobe CX Enterprise Coworker is an AI-powered teammate that reimagines the nature of work for organizations, teams, and individuals. Coworker elegantly automates customer experience and marketing workflows so organizations can focus on realizing their business goals and transforming outcomes, not coordinating tasks. As an agentic engine, Coworker takes a new innovative approach to automating business process. It elevates AI model performance and accuracy by bringing together data, intelligence, collaboration and agentic skills execution with enterprise context, governance, and human oversight built in.
Login Info
Sample Chat Prompts
- General
- What can you help me with?
- Product Knowledge
- How does CJA integrate with AEP?
- How does RTCDP use integrations with CJA and Adobe Target?
- What are the guardrails and limits for RTCDP streaming audiences?
- When was the latest release of RTCDP and what were the updates?
- What is the difference between batch, streaming, and edge audiences
- How does the Target integration work in RTCDP?
- Audiences
- How many audiences have the same logic?
- If I wanted to build an audience that was based on someone starting an application then not completing that application what would your recommend what fields I should use and the PQL that would be used.
- Simple Prompt
- Build a rule-based people audience in Adobe Experience Platform for application abandonment. The Audience name: Application Started – Not Completed (Last 7 Days) - Initials. With the Intent: Qualify profiles who started the "Application Form" in the last 7 days but did not submit it within that same window. The Evaluation type: Streaming (fall back to batch if streaming is unavailable for these fields).
- Detailed Prompt
- Build me an audience of people who started an application but never finished it. I want to find everyone who began filling out our "Application Form" in the last 7 days but did not submit it during that same period — in other words, people who abandoned the application partway through.
- Please:
- Name the audience something like "Application Started – Not Completed (Last 7 Days)"
- Base it on our website form-interaction events (the fields that record which form someone touched and whether they started it or submitted it), coming from our profile-enabled website event data
- Qualify a person if they have a "start" event for the Application Form but no matching "submit" event within the last 7 days
- Evaluate it in near-real-time (streaming) if possible, otherwise a daily batch is fine
- Before you build it, please double-check the actual values in our data — the real form name and the exact wording used for the "start" and "submit" actions — and adjust if they differ from what I've described. Also confirm 7 days is a sensible window for "abandoned."