Integrations
CAD Integrations and CFS Workflows
Overview: What CAD Integration Enables
When CAD integration is enabled, ANET can create a CFS from an ANET-handled call. CAD integration can provide: Field mapping from ANET → CAD Automated...
Integration Concepts You Need to Know
Field mapping defines where ANET data is written in CAD. Common mapped fields include: Caller name Caller phone number Location Remarks/narrative (oft...
Required Field Enforcement
CAD workflows typically require specific fields (agency-defined). If a required field is missing or invalid: Automated creation may be blocked Submiss...
Two CFS Workflows: Automated vs Suggested
Automated CFS Behavior: ANET sends a CFS directly to CAD No human approval required Only occurs when required fields are present and valid Best used w...
Configure CAD Integration
Note: The exact UI labels may vary by deployment. The steps below describe the required configuration sequence and validation checks. Navigate to Admi...
Test CAD Integration Safely
Place test call. Trigger an intent configured to create a CFS. Provide: Full caller contact information Clear location Clear incident details In CAD, ...
Draft Fallback Behavior
Draft fallback is designed to protect data quality. When triggered (commonly by missing required fields or validation issues): ANET does not submit a ...
Common CAD Integration Risks
Cause: ANET did not capture a required CAD field. Fix: Switch to Suggested mode or adjust intent questions to capture the field. Cause: ANET fields...
Troubleshoot a Failed CAD Submission
Open the call in Triage. Check CFS status = Failed (or equivalent). Open the submission/audit details. Identify: Which field failed validation Whether...
Operational Best Practices
Start with the suggested mode during early deployment. Validate mapping with real call patterns, not only test calls. Track failures by category (miss...
Key Takeaways
CAD integration is optional and agency-specific. Field mapping determines data correctness. Required fields determine whether submissions succeed. Aut...
Integrations Framework for Future Systems
Overview: How Future Integrations Should Be Added
Future systems may include: RMS / records systems Reporting exports Data warehouse connections GIS or address validation services Notification tools E...
Required Integration Definition (What to Document)
For every integration, document: Integration purpose and scope Data elements exchanged Required fields and validation rules Authentication/authorizati...
Key Takeaways
Each integration must define success, failure, and fallback behavior. Status visibility in Triage is required for supportability. Testing must include...