# Technolutions Slate + Agentic OS Integration > Source: https://ibl.ai/resources/integrations/slate-agentic-os *Deploy purpose-built AI agents on top of your Slate CRM to automate enrollment, personalize outreach, and accelerate student success — on your infrastructure.* Technolutions Slate is the leading CRM platform for higher education enrollment management, powering admissions, financial aid, advising, and alumni engagement for hundreds of institutions worldwide. ibl.ai Agentic OS extends Slate's capabilities by deploying intelligent AI agents that act on CRM data in real time. These agents automate repetitive workflows, surface actionable insights, and personalize every student touchpoint — without replacing your existing Slate investment. Because Agentic OS runs on your own infrastructure, your institution retains full ownership of every agent, every data flow, and every model. There is zero vendor lock-in, and all operations remain FERPA-compliant by design. ## Capabilities ### Real-Time Enrollment Outreach Automation AI agents monitor Slate for new inquiries and application events, then automatically generate and send personalized outreach messages — reducing counselor workload while improving prospect response rates. ### Predictive Yield Scoring Agents analyze historical Slate enrollment data and real-time engagement signals to score each applicant's likelihood to enroll, enabling counselors to prioritize high-impact interventions. ### Intelligent Task Routing The Agentic OS orchestration layer routes Slate events to the right agent or human staff member based on applicant profile, stage, and urgency — eliminating manual triage. ### AI-Assisted Communication Drafting Agents draft personalized emails, SMS messages, and chat responses grounded in each prospect's Slate record, which staff can review, edit, and send — keeping humans in control. ### Compliance-First Audit Logging Every agent action, data access event, and model recommendation is logged in the Agentic OS audit module, providing a complete, FERPA-compliant record for institutional governance. ### Institution-Owned Agent Infrastructure All agents run on your infrastructure. Your institution owns the code, the data, and the models — with zero dependency on ibl.ai cloud services after deployment. ## Setup ### Step 1: Provision ibl.ai Agentic OS on Your Infrastructure (~2–4 hours) Deploy the Agentic OS platform on your institution's cloud environment or on-premises servers. ibl.ai provides infrastructure-as-code templates for AWS, Azure, and GCP to accelerate provisioning. Requirements: - Cloud account (AWS, Azure, or GCP) or on-premises Kubernetes cluster - Minimum 8 vCPU, 32 GB RAM for production deployment - ibl.ai Agentic OS license and deployment package ### Step 2: Generate Slate API Credentials (~30 minutes) In Technolutions Slate, create a dedicated API user with appropriate scopes for the data objects your agents will access — typically prospects, applications, communications, and events. Requirements: - Slate administrator access - API user creation permissions - Defined data access scope per institutional policy ### Step 3: Configure the Slate API Connector in Agentic OS (~1 hour) Enter your Slate API credentials into the Agentic OS Slate Connector configuration panel. Map Slate data objects to Agentic OS entity schemas and validate the bidirectional connection. Requirements: - Slate API base URL and credentials from Step 2 - Agentic OS admin access - Network connectivity between Agentic OS host and Slate instance ### Step 4: Register Slate Webhooks for Real-Time Events (~45 minutes) Configure Slate to push real-time webhook events — such as new inquiries, application submissions, and status changes — to the Agentic OS event ingestion endpoint. Requirements: - Agentic OS public or VPN-accessible webhook endpoint URL - Slate webhook configuration access - TLS certificate on Agentic OS endpoint ### Step 5: Deploy and Configure AI Agents (~2–6 hours depending on agent count) Select and configure purpose-built agents from the ibl.ai agent library — such as the Enrollment Outreach Agent or Yield Prediction Agent — and assign them to relevant Slate event triggers. Requirements: - Defined agent roles and workflow objectives - Institutional communication templates and tone guidelines - Approval from enrollment and compliance stakeholders ### Step 6: Test, Audit, and Go Live (~1–2 days) Run end-to-end integration tests using sandbox Slate records. Review agent action logs in the Agentic OS audit dashboard, confirm FERPA compliance posture, and promote to production. Requirements: - Slate sandbox or test environment - Compliance officer sign-off - Staff training on agent monitoring and override procedures ## Technical Requirements **Technolutions Slate Requirements:** - Technolutions Slate instance (cloud or on-premises) - Slate API access enabled with appropriate user and scope configuration - Webhook configuration capability in Slate admin panel - Slate version compatible with current REST API specification **ibl.ai Agentic OS Infrastructure:** - Kubernetes cluster (cloud-managed or self-hosted) or Docker Compose for smaller deployments - Minimum 8 vCPU and 32 GB RAM for production; 16 vCPU and 64 GB RAM recommended for multi-agent deployments - TLS-enabled HTTPS endpoint for Slate webhook ingestion - Outbound internet access to Slate API endpoint (or VPN tunnel for on-premises Slate) - Object storage (S3-compatible) for agent logs and batch data **Security & Compliance:** - FERPA data handling agreement with ibl.ai (if any data transits ibl.ai services during setup) - Role-based access control configured for Agentic OS admin and agent monitoring roles - SSO/SAML integration with institutional identity provider for staff access - Audit log retention policy aligned with institutional records management requirements - Network security group or firewall rules restricting Agentic OS data plane access ## FAQ **Q: Does the Slate and Agentic OS integration require moving student data to ibl.ai's cloud?** No. Agentic OS is deployed entirely on your institution's own infrastructure. Student data from Slate never leaves your environment. ibl.ai does not have access to your Slate records or agent outputs after deployment. **Q: Is this integration FERPA compliant?** Yes. Because Agentic OS runs on institution-owned infrastructure and all data remains within your environment, the integration is FERPA-compliant by design. Every agent action is logged in the built-in audit module for governance and review. **Q: What Slate data objects can AI agents access and act on?** Agents can be configured to access any Slate data object exposed via the Slate REST API, including prospects, applicants, applications, communications, events, and custom fields. Access is scoped per institutional policy during setup. **Q: Can AI agents send communications directly from Slate, or do they require staff approval?** Both modes are supported. Agents can be configured to draft communications for staff review and approval before sending, or to send autonomously for defined low-risk communication types. Institutions control the approval workflow per agent. **Q: How long does it take to deploy the Slate and Agentic OS integration?** A standard deployment with two to three agents typically takes three to five business days, including infrastructure provisioning, connector configuration, agent setup, testing, and staff training. Complex multi-agent deployments may take two to four weeks. **Q: Does ibl.ai Agentic OS replace Technolutions Slate?** No. Agentic OS extends Slate by adding AI agent capabilities on top of your existing CRM investment. Slate remains the system of record for all enrollment and CRM data. Agents read from and write back to Slate without disrupting existing workflows. **Q: Can we build custom AI agents for our institution's specific Slate workflows?** Yes. Agentic OS is a platform for building and deploying custom AI agents. In addition to the pre-built agent library, your team or ibl.ai's professional services team can develop agents tailored to your institution's unique Slate configurations and enrollment processes. **Q: What happens to our agents if we stop using ibl.ai?** Because your institution owns the agent code, data, and infrastructure, you retain full access to everything after any contract ends. There is zero vendor lock-in. Your agents continue running on your infrastructure independently of ibl.ai.