Journey Architect Agent
Journey Architect Agent
The Journey Architect is an AI agent that runs automatically whenever a contact is assigned a category. Its job is to determine the correct nurture journey for that contact, create a journey instance, and trigger email generation — with no manual configuration required from the agent.
How It Works
1. Trigger
The Journey Architect fires immediately when a contact is categorised. This happens:
- On first-time categorisation of a contact
- When an existing contact is re-categorised (i.e. their category changes)
No manual action is needed to start a journey. Categorising the contact is the only step.
2. Template Selection
The agent selects a journey template by matching two attributes of the contact:
| Attribute | Values |
|---|---|
| Category | Seller, Landlord, Buy-to-Let Investor, Active Tenant, and other supported categories (12 total) |
| Group | prospect or existing_client |
Each unique combination of category and group maps to a specific pre-built journey template. This ensures the tone, content structure, and call-to-action of the nurture sequence are appropriate for where the contact sits in the relationship.
3. Journey Instance Creation
Once the template is selected, the Journey Architect creates a contact journey instance — a record that links the contact to the chosen template and tracks progress through the sequence.
4. Content Writer Handoff
With the journey instance created, the Journey Architect triggers the Content Writer agent, which generates the three personalised emails in the agency's brand voice. The emails are queued for agent review and approval before sending.
Edge Cases
Re-categorisation
If a contact's category is updated after a journey has already started, the Journey Architect:
- Cancels the existing in-progress journey
- Starts a new journey based on the updated category
This ensures contacts are never running through a sequence that no longer matches their current status.
Duplicate Journey Prevention
If a contact already has an active journey in the same category, the Journey Architect skips creation. No duplicate sequences are generated. This prevents contacts from receiving repeated nurture emails when, for example, a sync event re-fires a categorisation for a contact already mid-journey.
Manual Journey Override
If a property agent manually overrides a contact's journey (e.g. selecting a different template or pausing a sequence), the Journey Architect respects that override. Automated logic will not cancel or replace a manually managed journey.
Summary of Behaviours
Contact categorised
│
▼
Journey Architect fires
│
├─ Active journey in same category? ──► Skip (no duplicate)
│
├─ Manual override active? ──────────► Skip (respect override)
│
├─ Different category, journey in progress? ── Cancel old → Start new
│
└─ No existing journey? ─────────────► Select template
│
Create journey instance
│
Trigger Content Writer agent
│
3 emails generated for review
Related
- Content Writer Agent — generates the personalised email sequence
- Contact Categories — the 12 supported contact categories
- Journey Review & Approval — how agents review and approve generated emails
- CRM Sync — how contact data flows from agentOS, Reapit, Alto, Street, and Loop