Add the brand, product, client or internal initiative. Capture goals, owner, status and the first useful summary.
Onboarding
Start with one project, then add the operating records agents need.
Agent Ops Suite is project based. You can support several brands or products from one local installation while keeping each project cleanly separated.
Add contacts, organisations, work items, tickets, campaigns, content items and source links as needed.
Use Agent Memory for brand voice, approved claims, privacy rules, support policies and operating instructions.
Let an agent prepare marketing, content, issue, CRM, project or support work from the structured records.
Keep external communication, customer promises, public claims and sensitive cases in the approval queue.
Agents save summaries and next actions so later sessions can continue without reloading everything into context.
Import
Bring in the records agents need
Agent Ops Suite onboarding keeps migration practical: import the key records first, preserve source IDs, then connect deeper systems only where they add value.
| Source | Onboarding path | What Agent Ops Suite preserves |
|---|---|---|
| Current CRM | Import contacts, organisations, relationship notes, tags and segments. | Source IDs, roles, tags, activity notes and project links. |
| Issue trackers | Import projects, issues, priorities, blockers and source links. | External issue IDs, status, owner, priority and dependencies. |
| Content calendars | Import content items, due dates, channels and publication notes. | Editorial state, channel, source links and publication metadata. |
| Support inboxes | Import tickets, conversations, customers and internal notes. | Customer links, message source, ticket status and escalation state. |
Start narrow, then add connectors once the imported records are clean enough for agents to trust.