diff --git a/docs.json b/docs.json
index ddf85285..934bc03b 100644
--- a/docs.json
+++ b/docs.json
@@ -123,7 +123,6 @@
"build/agents/build-your-agent/alerts",
"build/agents/build-your-agent/memory",
"build/agents/build-your-agent/variables",
- "build/agents/build-your-agent/version-history",
{
"group": "Trigger Types",
"pages": [
@@ -167,27 +166,6 @@
}
]
},
- {
- "group": "Evaluating Performance",
- "pages": [
- "build/agents/evals/introduction",
- "build/agents/evals/test-sets",
- "build/agents/evals/checks",
- "build/agents/evals/running-evaluations",
- "build/agents/evals/monitor"
- ]
- },
- {
- "group": "Running Tasks",
- "pages": [
- "build/agents/give-your-agent-tasks/task-overview",
- "build/agents/give-your-agent-tasks/tasks-page",
- "build/agents/give-your-agent-tasks/interact-with-your-agent",
- "build/agents/give-your-agent-tasks/bulk-schedule",
- "build/agents/give-your-agent-tasks/task-queue"
- ]
- },
- "build/agents/share-your-agent",
"build/agents/delete-agent"
]
},
@@ -207,7 +185,6 @@
]
},
"build/tools/delete-tool",
- "build/tools/share-your-tool",
{
"group": "Tool Steps",
"pages": [
@@ -369,8 +346,7 @@
"build/workforces/workforce-features/workforce-task-view",
"build/workforces/workforce-features/approvals-and-escalations"
]
- },
- "build/workforces/share-your-workforce"
+ }
]
},
{
@@ -391,6 +367,40 @@
"build/knowledge/knowledge-tool-steps",
"build/knowledge/use-snippets-for-quick-access"
]
+ },
+ {
+ "group": "Platform",
+ "pages": [
+ {
+ "group": "Evaluating Performance",
+ "pages": [
+ "build/platform/evals/introduction",
+ "build/platform/evals/test-sets",
+ "build/platform/evals/checks",
+ "build/platform/evals/running-evaluations",
+ "build/platform/evals/monitor"
+ ]
+ },
+ {
+ "group": "Running Tasks",
+ "pages": [
+ "build/platform/tasks/task-overview",
+ "build/platform/tasks/tasks-page",
+ "build/platform/tasks/interact-with-your-agent",
+ "build/platform/tasks/bulk-schedule",
+ "build/platform/tasks/task-queue"
+ ]
+ },
+ {
+ "group": "Sharing",
+ "pages": [
+ "build/platform/sharing/share-your-agent",
+ "build/platform/sharing/share-your-tool",
+ "build/platform/sharing/share-your-workforce"
+ ]
+ },
+ "build/platform/version-history"
+ ]
}
]
},
@@ -783,6 +793,62 @@
}
},
"redirects": [
+ {
+ "source": "/build/agents/evals/introduction",
+ "destination": "/build/platform/evals/introduction"
+ },
+ {
+ "source": "/build/agents/evals/test-sets",
+ "destination": "/build/platform/evals/test-sets"
+ },
+ {
+ "source": "/build/agents/evals/checks",
+ "destination": "/build/platform/evals/checks"
+ },
+ {
+ "source": "/build/agents/evals/running-evaluations",
+ "destination": "/build/platform/evals/running-evaluations"
+ },
+ {
+ "source": "/build/agents/evals/monitor",
+ "destination": "/build/platform/evals/monitor"
+ },
+ {
+ "source": "/build/agents/give-your-agent-tasks/task-overview",
+ "destination": "/build/platform/tasks/task-overview"
+ },
+ {
+ "source": "/build/agents/give-your-agent-tasks/tasks-page",
+ "destination": "/build/platform/tasks/tasks-page"
+ },
+ {
+ "source": "/build/agents/give-your-agent-tasks/interact-with-your-agent",
+ "destination": "/build/platform/tasks/interact-with-your-agent"
+ },
+ {
+ "source": "/build/agents/give-your-agent-tasks/bulk-schedule",
+ "destination": "/build/platform/tasks/bulk-schedule"
+ },
+ {
+ "source": "/build/agents/give-your-agent-tasks/task-queue",
+ "destination": "/build/platform/tasks/task-queue"
+ },
+ {
+ "source": "/build/agents/share-your-agent",
+ "destination": "/build/platform/sharing/share-your-agent"
+ },
+ {
+ "source": "/build/tools/share-your-tool",
+ "destination": "/build/platform/sharing/share-your-tool"
+ },
+ {
+ "source": "/build/workforces/share-your-workforce",
+ "destination": "/build/platform/sharing/share-your-workforce"
+ },
+ {
+ "source": "/build/agents/build-your-agent/version-history",
+ "destination": "/build/platform/version-history"
+ },
{
"source": "/enterprise/org-project-controls-governance",
"destination": "/enterprise/manage-projects-and-users-api"
@@ -1145,15 +1211,15 @@
},
{
"source": "/evals",
- "destination": "/build/agents/evals/introduction"
+ "destination": "/build/platform/evals/introduction"
},
{
"source": "/build/agents/evals",
- "destination": "/build/agents/evals/introduction"
+ "destination": "/build/platform/evals/introduction"
},
{
"source": "/build/agents/build-your-agent/evals",
- "destination": "/build/agents/evals/introduction"
+ "destination": "/build/platform/evals/introduction"
}
]
}
diff --git a/enterprise/rbac.mdx b/enterprise/rbac.mdx
index b91f756c..c4c9a2d7 100644
--- a/enterprise/rbac.mdx
+++ b/enterprise/rbac.mdx
@@ -239,7 +239,7 @@ This means when sharing a workforce, you must:
-Learn more about [sharing workforces](/build/workforces/share-your-workforce) as cloneable templates.
+Learn more about [sharing workforces](/build/platform/sharing/share-your-workforce) as cloneable templates.
----
diff --git a/get-started/pricing.mdx b/get-started/pricing.mdx
index 16aa5ee4..e41b92f2 100644
--- a/get-started/pricing.mdx
+++ b/get-started/pricing.mdx
@@ -161,7 +161,7 @@ Start delegating work to agents today. Grow as your AI Workforce expands.
| **Bring your own LLM** | ✗ | ✓ | ✓ | ✓ |
| **A/B Testing** | ✗ | ✓ | ✓ | ✓ |
| **[Analytics Dashboard](/enterprise/analytics)** | ✗ | ✗ | ✓ | ✓ |
-| **[Agent Evaluations](/build/agents/evals/introduction)** | ✗ | ✗ | ✗ | ✓ |
+| **[Agent Evaluations](/build/platform/evals/introduction)** | ✗ | ✗ | ✗ | ✓ |
| **Work Hour Controls** | ✗ | ✗ | ✗ | ✓ |
### Security & compliance
diff --git a/get-started/quick-start-guide.mdx b/get-started/quick-start-guide.mdx
index 9969d22a..354bd760 100644
--- a/get-started/quick-start-guide.mdx
+++ b/get-started/quick-start-guide.mdx
@@ -105,10 +105,10 @@ Test again after each change. A few rounds of this and you'll have a solid agent
Once you're happy with the output, put your agent to work:
-- [Share your agent](/build/agents/share-your-agent) with your team so others can use it
+- [Share your agent](/build/platform/sharing/share-your-agent) with your team so others can use it
- Use [Relevance Chat](/get-started/chat/introduction) to give your team instant access to your agents
- Set up [triggers](/build/agents/build-your-agent/triggers) to run it automatically — on a schedule, from a webhook, or when something happens in your CRM
-- Use [bulk schedule](/build/agents/give-your-agent-tasks/bulk-schedule) to run it across a list of inputs
+- Use [bulk schedule](/build/platform/tasks/bulk-schedule) to run it across a list of inputs
- Add [alerts](/build/agents/build-your-agent/alerts) so you get notified when something needs attention, and the agent knows when to loop in a human
## Beyond building
diff --git a/get-started/troubleshooting/troubleshooting-agents-not-working.mdx b/get-started/troubleshooting/troubleshooting-agents-not-working.mdx
index 8f6c6fa9..52ebe04e 100644
--- a/get-started/troubleshooting/troubleshooting-agents-not-working.mdx
+++ b/get-started/troubleshooting/troubleshooting-agents-not-working.mdx
@@ -34,7 +34,7 @@ Learn how to monitor your credit and action usage at both the [organization leve
When agents fail, it's often because one of their tools is not working properly. Here's how to troubleshoot tool issues:
-Use the **Has active tool failures** filter in the Task list to quickly identify which Tasks had Tool failures — including cases where the Agent continued running despite a Tool error. See [Filtering Tasks](/build/agents/give-your-agent-tasks/task-overview#filtering-tasks) for details.
+Use the **Has active tool failures** filter in the Task list to quickly identify which Tasks had Tool failures — including cases where the Agent continued running despite a Tool error. See [Filtering Tasks](/build/platform/tasks/task-overview#filtering-tasks) for details.
#### Step 1: Test the tool independently
diff --git a/guides/customer-success/account-health.mdx b/guides/customer-success/account-health.mdx
index 51a57200..ea508ca8 100644
--- a/guides/customer-success/account-health.mdx
+++ b/guides/customer-success/account-health.mdx
@@ -67,13 +67,13 @@ Once it's running, deepen it in three moves:
- Shape it with a [prompt](/build/agents/build-your-agent/prompt), your CS playbook in [Knowledge](/build/knowledge/create-knowledge), and [Bulk Schedule](/build/agents/give-your-agent-tasks/bulk-schedule).
+ Shape it with a [prompt](/build/agents/build-your-agent/prompt), your CS playbook in [Knowledge](/build/knowledge/create-knowledge), and [Bulk Schedule](/build/platform/tasks/bulk-schedule).
Wrap it in a [workflow](/build/workforces/create-a-workforce) that fires on a [trigger](/build/agents/build-your-agent/triggers).
- Pipe churn outcomes back into the Agent's [evals](/build/agents/evals/introduction) so scoring tracks what predicted cancellation.
+ Pipe churn outcomes back into the Agent's [evals](/build/platform/evals/introduction) so scoring tracks what predicted cancellation.
diff --git a/guides/customer-success/getting-started.mdx b/guides/customer-success/getting-started.mdx
index ced90a17..6d1292e0 100644
--- a/guides/customer-success/getting-started.mdx
+++ b/guides/customer-success/getting-started.mdx
@@ -105,7 +105,7 @@ How hands-on do you want to be? Pick a tab — the rest of the page is written f
Set up evals so health scoring or QBR-prep regressions get caught before they reach the CSM.
-
+
Define test cases in the UI. Run them on every change.
diff --git a/guides/customer-success/qbr-prep.mdx b/guides/customer-success/qbr-prep.mdx
index 3bbb4952..91e9280c 100644
--- a/guides/customer-success/qbr-prep.mdx
+++ b/guides/customer-success/qbr-prep.mdx
@@ -73,7 +73,7 @@ Once it's running, deepen it in three moves:
Wrap it in a [workflow](/build/workforces/create-a-workforce) that fires on a [trigger](/build/agents/build-your-agent/triggers).
- Feed back which QBR sections landed into the Agent's [evals](/build/agents/evals/introduction) so the format tracks what's used.
+ Feed back which QBR sections landed into the Agent's [evals](/build/platform/evals/introduction) so the format tracks what's used.
diff --git a/guides/customer-success/renewal-expansion.mdx b/guides/customer-success/renewal-expansion.mdx
index 54b11892..73fd3a0d 100644
--- a/guides/customer-success/renewal-expansion.mdx
+++ b/guides/customer-success/renewal-expansion.mdx
@@ -67,13 +67,13 @@ Once it's running, deepen it in three moves:
- Shape it with a [prompt](/build/agents/build-your-agent/prompt), your renewal playbook in [Knowledge](/build/knowledge/create-knowledge), and [Bulk Schedule](/build/agents/give-your-agent-tasks/bulk-schedule).
+ Shape it with a [prompt](/build/agents/build-your-agent/prompt), your renewal playbook in [Knowledge](/build/knowledge/create-knowledge), and [Bulk Schedule](/build/platform/tasks/bulk-schedule).
Wrap it in a [workflow](/build/workforces/create-a-workforce) that fires on a [trigger](/build/agents/build-your-agent/triggers).
- Feed renewal outcomes back into the Agent's [evals](/build/agents/evals/introduction) so it leans on the plays that saved accounts.
+ Feed renewal outcomes back into the Agent's [evals](/build/platform/evals/introduction) so it leans on the plays that saved accounts.
diff --git a/guides/customer-support/getting-started.mdx b/guides/customer-support/getting-started.mdx
index edd13dc0..437c109a 100644
--- a/guides/customer-support/getting-started.mdx
+++ b/guides/customer-support/getting-started.mdx
@@ -105,7 +105,7 @@ How hands-on do you want to be? Pick a tab — the rest of the page is written f
Set up evals so regressions in tone or accuracy get caught before the Agent replies to a customer.
-
+
Define test cases in the UI. Run them on every change.
diff --git a/guides/customer-support/kb-generation.mdx b/guides/customer-support/kb-generation.mdx
index 1806f2c0..ae0fcecc 100644
--- a/guides/customer-support/kb-generation.mdx
+++ b/guides/customer-support/kb-generation.mdx
@@ -67,13 +67,13 @@ Once it's running, deepen it in three moves:
- Shape it with a [prompt](/build/agents/build-your-agent/prompt), your style guide in [Knowledge](/build/knowledge/create-knowledge), and [Bulk Schedule](/build/agents/give-your-agent-tasks/bulk-schedule).
+ Shape it with a [prompt](/build/agents/build-your-agent/prompt), your style guide in [Knowledge](/build/knowledge/create-knowledge), and [Bulk Schedule](/build/platform/tasks/bulk-schedule).
Wrap it in a [workflow](/build/workforces/create-a-workforce) that fires on a [trigger](/build/agents/build-your-agent/triggers).
- Feed read and deflection data back into the Agent's [evals](/build/agents/evals/introduction) so it drafts the formats that help.
+ Feed read and deflection data back into the Agent's [evals](/build/platform/evals/introduction) so it drafts the formats that help.
diff --git a/guides/customer-support/response-drafting.mdx b/guides/customer-support/response-drafting.mdx
index 4e0babe2..8f3961f4 100644
--- a/guides/customer-support/response-drafting.mdx
+++ b/guides/customer-support/response-drafting.mdx
@@ -73,7 +73,7 @@ Once it's running, deepen it in three moves:
Wrap it in a [workflow](/build/workforces/create-a-workforce) that fires on a [trigger](/build/agents/build-your-agent/triggers).
- Feed back which drafts shipped untouched, plus CSAT, into the Agent's [evals](/build/agents/evals/introduction) so it matches what your team sends.
+ Feed back which drafts shipped untouched, plus CSAT, into the Agent's [evals](/build/platform/evals/introduction) so it matches what your team sends.
diff --git a/guides/customer-support/ticket-triage.mdx b/guides/customer-support/ticket-triage.mdx
index c85563cf..80f562d4 100644
--- a/guides/customer-support/ticket-triage.mdx
+++ b/guides/customer-support/ticket-triage.mdx
@@ -67,13 +67,13 @@ Once it's running, deepen it in three moves:
- Shape it with a [prompt](/build/agents/build-your-agent/prompt), [Knowledge](/build/knowledge/create-knowledge), and [Bulk Schedule](/build/agents/give-your-agent-tasks/bulk-schedule).
+ Shape it with a [prompt](/build/agents/build-your-agent/prompt), [Knowledge](/build/knowledge/create-knowledge), and [Bulk Schedule](/build/platform/tasks/bulk-schedule).
Wrap it in a [workflow](/build/workforces/create-a-workforce) that fires on a [trigger](/build/agents/build-your-agent/triggers).
- Feed resolved-ticket outcomes back into the Agent's [evals](/build/agents/evals/introduction) so its triage tracks what actually held up.
+ Feed resolved-ticket outcomes back into the Agent's [evals](/build/platform/evals/introduction) so its triage tracks what actually held up.
diff --git a/guides/marketing/campaign-analytics.mdx b/guides/marketing/campaign-analytics.mdx
index 24a2781a..a7085cfe 100644
--- a/guides/marketing/campaign-analytics.mdx
+++ b/guides/marketing/campaign-analytics.mdx
@@ -73,7 +73,7 @@ Once it's running, deepen it in three moves:
Wrap it in a [workflow](/build/workforces/create-a-workforce) that fires on a [trigger](/build/agents/build-your-agent/triggers).
- Weight the Agent's [evals](/build/agents/evals/introduction) toward the metrics that actually predicted pipeline.
+ Weight the Agent's [evals](/build/platform/evals/introduction) toward the metrics that actually predicted pipeline.
diff --git a/guides/marketing/content-repurposing.mdx b/guides/marketing/content-repurposing.mdx
index 4a930faa..b6f2f717 100644
--- a/guides/marketing/content-repurposing.mdx
+++ b/guides/marketing/content-repurposing.mdx
@@ -67,13 +67,13 @@ Once it's running, deepen it in three moves:
- Shape it with a [prompt](/build/agents/build-your-agent/prompt), your brand voice in [Knowledge](/build/knowledge/create-knowledge), and [Bulk Schedule](/build/agents/give-your-agent-tasks/bulk-schedule).
+ Shape it with a [prompt](/build/agents/build-your-agent/prompt), your brand voice in [Knowledge](/build/knowledge/create-knowledge), and [Bulk Schedule](/build/platform/tasks/bulk-schedule).
Wrap it in a [workflow](/build/workforces/create-a-workforce) that fires on a [trigger](/build/agents/build-your-agent/triggers).
- Feed channel engagement back into the Agent's [evals](/build/agents/evals/introduction) so it leans on what performed.
+ Feed channel engagement back into the Agent's [evals](/build/platform/evals/introduction) so it leans on what performed.
diff --git a/guides/marketing/getting-started.mdx b/guides/marketing/getting-started.mdx
index 10fb51e8..d688e21d 100644
--- a/guides/marketing/getting-started.mdx
+++ b/guides/marketing/getting-started.mdx
@@ -105,7 +105,7 @@ How hands-on do you want to be? Pick a tab — the rest of the page is written f
Set up evals so brand-voice regressions get caught before they ship to your list.
-
+
Define test cases in the UI. Run them on every change.
diff --git a/guides/marketing/lifecycle-campaigns.mdx b/guides/marketing/lifecycle-campaigns.mdx
index e8e6370c..552732ed 100644
--- a/guides/marketing/lifecycle-campaigns.mdx
+++ b/guides/marketing/lifecycle-campaigns.mdx
@@ -67,13 +67,13 @@ Once it's running, deepen it in three moves:
- Shape it with a [prompt](/build/agents/build-your-agent/prompt), your brand voice in [Knowledge](/build/knowledge/create-knowledge), and [Bulk Schedule](/build/agents/give-your-agent-tasks/bulk-schedule).
+ Shape it with a [prompt](/build/agents/build-your-agent/prompt), your brand voice in [Knowledge](/build/knowledge/create-knowledge), and [Bulk Schedule](/build/platform/tasks/bulk-schedule).
Wrap it in a [workflow](/build/workforces/create-a-workforce) that fires on a [trigger](/build/agents/build-your-agent/triggers).
- Feed opens, clicks, and conversion back into the Agent's [evals](/build/agents/evals/introduction) so drafts track what converts.
+ Feed opens, clicks, and conversion back into the Agent's [evals](/build/platform/evals/introduction) so drafts track what converts.
@@ -87,7 +87,7 @@ Once it's running, deepen it in three moves:
The HubSpot trigger fires on the wrong field and the sequence drafts the wrong campaign. Gate triggers tightly and review what actually causes them to fire in week one.
- A prompt tweak changes tone everywhere. Use [evals](/build/agents/evals/introduction) on a few canonical drafts to catch drift before it ships to subscribers.
+ A prompt tweak changes tone everywhere. Use [evals](/build/platform/evals/introduction) on a few canonical drafts to catch drift before it ships to subscribers.
Tempting to skip marketing approval and queue directly. Don't — one bad subject line in production costs trust. Gate L3 with a Slack approval until you've watched it run for a quarter.
diff --git a/guides/revops/data-dedup.mdx b/guides/revops/data-dedup.mdx
index dbf1815d..b069f393 100644
--- a/guides/revops/data-dedup.mdx
+++ b/guides/revops/data-dedup.mdx
@@ -67,13 +67,13 @@ Once it's running, deepen it in three moves:
- Shape it with a [prompt](/build/agents/build-your-agent/prompt), your matching rules in [Knowledge](/build/knowledge/create-knowledge), and [Bulk Schedule](/build/agents/give-your-agent-tasks/bulk-schedule).
+ Shape it with a [prompt](/build/agents/build-your-agent/prompt), your matching rules in [Knowledge](/build/knowledge/create-knowledge), and [Bulk Schedule](/build/platform/tasks/bulk-schedule).
Wrap it in a [workflow](/build/workforces/create-a-workforce) that fires on a [trigger](/build/agents/build-your-agent/triggers).
- Feed merge undos and disputes back into the Agent's [evals](/build/agents/evals/introduction) so its confidence thresholds track what's reliable.
+ Feed merge undos and disputes back into the Agent's [evals](/build/platform/evals/introduction) so its confidence thresholds track what's reliable.
diff --git a/guides/revops/getting-started.mdx b/guides/revops/getting-started.mdx
index e61df374..c666ea42 100644
--- a/guides/revops/getting-started.mdx
+++ b/guides/revops/getting-started.mdx
@@ -105,7 +105,7 @@ How hands-on do you want to be? Pick a tab — the rest of the page is written f
Set up evals so routing or enrichment regressions get caught before they propagate across thousands of records.
-
+
Define test cases in the UI. Run them on every change.
diff --git a/guides/revops/lead-routing.mdx b/guides/revops/lead-routing.mdx
index d3104f60..203f1cad 100644
--- a/guides/revops/lead-routing.mdx
+++ b/guides/revops/lead-routing.mdx
@@ -67,13 +67,13 @@ Once it's running, deepen it in three moves:
- Shape it with a [prompt](/build/agents/build-your-agent/prompt), your territory rules in [Knowledge](/build/knowledge/create-knowledge), and [Bulk Schedule](/build/agents/give-your-agent-tasks/bulk-schedule).
+ Shape it with a [prompt](/build/agents/build-your-agent/prompt), your territory rules in [Knowledge](/build/knowledge/create-knowledge), and [Bulk Schedule](/build/platform/tasks/bulk-schedule).
Wrap it in a [workflow](/build/workforces/create-a-workforce) that fires on a [trigger](/build/agents/build-your-agent/triggers).
- Feed back which routing held up into the Agent's [evals](/build/agents/evals/introduction) so edge-case handling tracks real outcomes.
+ Feed back which routing held up into the Agent's [evals](/build/platform/evals/introduction) so edge-case handling tracks real outcomes.
diff --git a/guides/revops/pipeline-hygiene.mdx b/guides/revops/pipeline-hygiene.mdx
index 32141a42..390fd888 100644
--- a/guides/revops/pipeline-hygiene.mdx
+++ b/guides/revops/pipeline-hygiene.mdx
@@ -73,7 +73,7 @@ Once it's running, deepen it in three moves:
Wrap it in a [workflow](/build/workforces/create-a-workforce) that fires on a [trigger](/build/agents/build-your-agent/triggers).
- Feed back which at-risk signals predicted slippage into the Agent's [evals](/build/agents/evals/introduction) so flagging sharpens.
+ Feed back which at-risk signals predicted slippage into the Agent's [evals](/build/platform/evals/introduction) so flagging sharpens.
diff --git a/guides/sales/competitive-intelligence.mdx b/guides/sales/competitive-intelligence.mdx
index 855c4fce..a702d1fc 100644
--- a/guides/sales/competitive-intelligence.mdx
+++ b/guides/sales/competitive-intelligence.mdx
@@ -73,7 +73,7 @@ Once it's running, deepen it in three moves:
Wrap it in a [workflow](/build/workforces/create-a-workforce) that fires on a [trigger](/build/agents/build-your-agent/triggers).
- Feed win/loss notes back into the Agent's [evals](/build/agents/evals/introduction) so it tracks the signals that matter.
+ Feed win/loss notes back into the Agent's [evals](/build/platform/evals/introduction) so it tracks the signals that matter.
diff --git a/guides/sales/crm-data-enrichment.mdx b/guides/sales/crm-data-enrichment.mdx
index 2c719f54..faa176fb 100644
--- a/guides/sales/crm-data-enrichment.mdx
+++ b/guides/sales/crm-data-enrichment.mdx
@@ -73,7 +73,7 @@ Once it's running, deepen it in three moves:
Wrap it in a [workflow](/build/workforces/create-a-workforce) that fires on a [trigger](/build/agents/build-your-agent/triggers).
- Tune it through [evals](/build/agents/evals/introduction) so it maintains the fields your team actually uses.
+ Tune it through [evals](/build/platform/evals/introduction) so it maintains the fields your team actually uses.
diff --git a/guides/sales/getting-started.mdx b/guides/sales/getting-started.mdx
index 825fcc80..214bbe2c 100644
--- a/guides/sales/getting-started.mdx
+++ b/guides/sales/getting-started.mdx
@@ -104,7 +104,7 @@ How hands-on do you want to be? Pick a tab — the rest of the page is written f
Once you're shaping prompts and tools, set up evals so you catch regressions before customers do.
-
+
Define test cases in the UI. Run them on every change.
diff --git a/guides/sales/lead-scoring.mdx b/guides/sales/lead-scoring.mdx
index 1901257c..71f48935 100644
--- a/guides/sales/lead-scoring.mdx
+++ b/guides/sales/lead-scoring.mdx
@@ -67,13 +67,13 @@ Once it's running, deepen it in three moves:
- Shape it with a [prompt](/build/agents/build-your-agent/prompt), your ICP in [Knowledge](/build/knowledge/create-knowledge), and [Bulk Schedule](/build/agents/give-your-agent-tasks/bulk-schedule) to backfill.
+ Shape it with a [prompt](/build/agents/build-your-agent/prompt), your ICP in [Knowledge](/build/knowledge/create-knowledge), and [Bulk Schedule](/build/platform/tasks/bulk-schedule) to backfill.
Wrap it in a [workflow](/build/workforces/create-a-workforce) that fires on a [trigger](/build/agents/build-your-agent/triggers).
- Feed closed-won and closed-lost outcomes back into the Agent's [evals](/build/agents/evals/introduction) so "qualified" tracks what closes.
+ Feed closed-won and closed-lost outcomes back into the Agent's [evals](/build/platform/evals/introduction) so "qualified" tracks what closes.
diff --git a/guides/sales/meeting-briefs.mdx b/guides/sales/meeting-briefs.mdx
index 30cea4aa..9851c4fc 100644
--- a/guides/sales/meeting-briefs.mdx
+++ b/guides/sales/meeting-briefs.mdx
@@ -73,7 +73,7 @@ Once it's running, deepen it in three moves:
Wrap it in a [workflow](/build/workforces/create-a-workforce) that fires on a [trigger](/build/agents/build-your-agent/triggers).
- Feed back which sections reps actually use into the Agent's [evals](/build/agents/evals/introduction) so briefs sharpen over time.
+ Feed back which sections reps actually use into the Agent's [evals](/build/platform/evals/introduction) so briefs sharpen over time.
diff --git a/guides/sales/personalized-outbound.mdx b/guides/sales/personalized-outbound.mdx
index 6e11709e..f2f9d73c 100644
--- a/guides/sales/personalized-outbound.mdx
+++ b/guides/sales/personalized-outbound.mdx
@@ -67,13 +67,13 @@ Once it's running, deepen it in three moves:
- Shape it with a [prompt](/build/agents/build-your-agent/prompt), [Knowledge](/build/knowledge/create-knowledge), and [Bulk Schedule](/build/agents/give-your-agent-tasks/bulk-schedule).
+ Shape it with a [prompt](/build/agents/build-your-agent/prompt), [Knowledge](/build/knowledge/create-knowledge), and [Bulk Schedule](/build/platform/tasks/bulk-schedule).
Wrap it in a [workflow](/build/workforces/create-a-workforce) that fires on a [trigger](/build/agents/build-your-agent/triggers).
- Feed reply and meeting rates back into the Agent's [evals](/build/agents/evals/introduction) so drafts work from what converts.
+ Feed reply and meeting rates back into the Agent's [evals](/build/platform/evals/introduction) so drafts work from what converts.
diff --git a/guides/sales/prospect-research-use-case.mdx b/guides/sales/prospect-research-use-case.mdx
index 9a3cde11..a58a242e 100644
--- a/guides/sales/prospect-research-use-case.mdx
+++ b/guides/sales/prospect-research-use-case.mdx
@@ -67,13 +67,13 @@ Once it's running, deepen it in three moves:
- Shape it with a [prompt](/build/agents/build-your-agent/prompt), [Knowledge](/build/knowledge/create-knowledge), and [Bulk Schedule](/build/agents/give-your-agent-tasks/bulk-schedule).
+ Shape it with a [prompt](/build/agents/build-your-agent/prompt), [Knowledge](/build/knowledge/create-knowledge), and [Bulk Schedule](/build/platform/tasks/bulk-schedule).
Wrap it in a [workflow](/build/workforces/create-a-workforce) that fires on a [trigger](/build/agents/build-your-agent/triggers).
- Feed won-deal signals back into the Agent's [evals](/build/agents/evals/introduction) so it tracks what closes.
+ Feed won-deal signals back into the Agent's [evals](/build/platform/evals/introduction) so it tracks what closes.
diff --git a/guides/solution-engineering/demo-prep.mdx b/guides/solution-engineering/demo-prep.mdx
index 22e4f850..3d9db8e1 100644
--- a/guides/solution-engineering/demo-prep.mdx
+++ b/guides/solution-engineering/demo-prep.mdx
@@ -73,7 +73,7 @@ Once it's running, deepen it in three moves:
Wrap it in a [workflow](/build/workforces/create-a-workforce) that fires on a [trigger](/build/agents/build-your-agent/triggers).
- Feed back which brief sections SEs use into the Agent's [evals](/build/agents/evals/introduction) so briefs sharpen over time.
+ Feed back which brief sections SEs use into the Agent's [evals](/build/platform/evals/introduction) so briefs sharpen over time.
diff --git a/guides/solution-engineering/discovery-summaries.mdx b/guides/solution-engineering/discovery-summaries.mdx
index ca45b43b..633191da 100644
--- a/guides/solution-engineering/discovery-summaries.mdx
+++ b/guides/solution-engineering/discovery-summaries.mdx
@@ -67,13 +67,13 @@ Once it's running, deepen it in three moves:
- Shape it with a [prompt](/build/agents/build-your-agent/prompt), your discovery framework in [Knowledge](/build/knowledge/create-knowledge), and [Bulk Schedule](/build/agents/give-your-agent-tasks/bulk-schedule).
+ Shape it with a [prompt](/build/agents/build-your-agent/prompt), your discovery framework in [Knowledge](/build/knowledge/create-knowledge), and [Bulk Schedule](/build/platform/tasks/bulk-schedule).
Wrap it in a [workflow](/build/workforces/create-a-workforce) that fires on a [trigger](/build/agents/build-your-agent/triggers).
- Feed back which sections SEs reference into the Agent's [evals](/build/agents/evals/introduction) so summaries track what matters.
+ Feed back which sections SEs reference into the Agent's [evals](/build/platform/evals/introduction) so summaries track what matters.
diff --git a/guides/solution-engineering/getting-started.mdx b/guides/solution-engineering/getting-started.mdx
index 9f7edf5b..2064b15f 100644
--- a/guides/solution-engineering/getting-started.mdx
+++ b/guides/solution-engineering/getting-started.mdx
@@ -105,7 +105,7 @@ How hands-on do you want to be? Pick a tab — the rest of the page is written f
Set up evals so a wrong security answer or hallucinated architecture detail gets caught before it lands in front of a prospect.
-
+
Define test cases in the UI. Run them on every change.
diff --git a/guides/solution-engineering/rfp-responses.mdx b/guides/solution-engineering/rfp-responses.mdx
index 1895b2c2..dcaf1212 100644
--- a/guides/solution-engineering/rfp-responses.mdx
+++ b/guides/solution-engineering/rfp-responses.mdx
@@ -67,13 +67,13 @@ Once it's running, deepen it in three moves:
- Shape it with a [prompt](/build/agents/build-your-agent/prompt), your prior-response archive in [Knowledge](/build/knowledge/create-knowledge), and [Bulk Schedule](/build/agents/give-your-agent-tasks/bulk-schedule).
+ Shape it with a [prompt](/build/agents/build-your-agent/prompt), your prior-response archive in [Knowledge](/build/knowledge/create-knowledge), and [Bulk Schedule](/build/platform/tasks/bulk-schedule).
Wrap it in a [workflow](/build/workforces/create-a-workforce) that fires on a [trigger](/build/agents/build-your-agent/triggers).
- Feed back which answers customers accepted into the Agent's [evals](/build/agents/evals/introduction) so it promotes the strong ones.
+ Feed back which answers customers accepted into the Agent's [evals](/build/platform/evals/introduction) so it promotes the strong ones.