Lead Follow-Up Agent
Outcome: Reply to new inbound leads with consistent follow-up messaging.
Workspace is organized into Guided Setup, Operate, and Advanced so new users can launch quickly while expert controls stay out of the way.
Complete these steps in order to finish first-run setup without entering advanced tooling.
Choose one outcome to begin. Detailed setup happens in the guided flow immediately after selection.
Outcome: Reply to new inbound leads with consistent follow-up messaging.
Outcome: Improve retention with automated reminders before renewals lapse.
Outcome: Handoff signed deals to delivery with complete context and next steps.
Outcome: Generate weekly summaries of wins, risks, and priorities.
Outcome: Send proactive client updates on a reliable cadence.
Use this assisted flow to set up one provider, create your first usable agent, run a test prompt, and publish the agent in one pass.
Lead Follow-Up
Quickstart score: 0/5 complete
Next step: Select a provider to continue.
Run and maintain active workflows after onboarding. Keep Guided Setup focused on first launch.
Recent runs
Your first workflow run will appear here after launch.
Internal admin/dev tooling for evaluating workflow, agent, and network ownership suggestions.
No sample tasks available yet. Refresh to load the latest snapshot.
Optional admin workspace for catalog and guardrail reviews. Keep this collapsed for guided demos.
Catalog controls are available for advanced governance workflows.
Select a provider, optionally add a friendly name, and store its API key for reuse across this workspace. Providers that do not require an API key can be saved without one, and saving a credential will update existing entries for the same provider.
Saved connections appear here and are automatically available in setup and workflow tools.
Verify stored credentials and capture the latest connectivity snapshot per provider.
Recent connection checks include latency and estimated cost signals for advanced troubleshooting.
Agent design, network orchestration, provider grouping, and deployment controls are optional during first-run setup.
Run history summarised by the performance evaluator to reveal success trends.
Latest provider requests captured by the provider service help contextualise health signals.
Configure lightweight agents that can react immediately or subscribe to Redis events. Provide contextual hints so the CaiEngine network can determine when to connect peers.
Blueprint templates are available for quick starts—use “Create example agents” to instantiate the curated set or apply a template below before saving.
Give your agent a clear purpose and decide how it should come online. Ad-hoc agents run on demand, while Redis event agents listen for messages to join the workflow instantly.
Ad-hoc — a research agent you invite when crafting a proposal.Redis Event — subscribe to sales.hand-off.ready when new SQLs
arrive.
Outline the files or structured payloads the agent will publish so peers know how to use its results.
{
"artifact_outputs": [
"lead_summary.json",
{ "type": "csv", "tag": "weekly-metrics" }
]
}
You can enter JSON as shown above or a simple list like
persona_brief.pdf, next_steps.txt.
Describe the background information, tone, and constraints the agent needs when joining a conversation. Blueprint guidance is merged with the artifact outputs you defined above.
{
"primary_goal": "Nurture trial sign-ups",
"tone": "Consultative",
"handoff_notes": "Escalate marketing qualified leads to sales within 2 hours"
}
Mix structured JSON with concise bullet points to capture expectations.
Agents appear here with their configured triggers and any connected networks. Edit an agent to fine-tune its context or remove it to detach from the network graph.
Showing 0 of 0 agents.
Group agents into a CaiEngine-powered network. The tolerance slider determines the minimum context similarity required for agents to link dynamically at runtime.
Document reproducible setup steps your operators should run alongside this network. Leave blank when no manual setup is required.
Provision the Artifact Exchange blueprint to give agents a shared drop zone for files and structured payloads during a run.
Quickly exercise a provider integration. You can supply a one-off API key here or reuse a stored credential.
Payment is overdue. WorkflowAI access is temporarily disabled until billing is settled.