This guide outlines the end-to-end process for integrating a new CAD (Computer-Aided Dispatch) Call Type into Total Response. To ensure seamless automation, you must first register the code in the Administrator Module and then map it to the appropriate protocol within Script Builder.
Follow these steps to ensure your dispatchers see the correct protocols triggered by your CAD system.
Frequently Asked Questions
Q: How do I add a new call type from my CAD system?
A: To add a new call type, you must first register the CAD code in the Administrator Module (Step 1) and then link it to a protocol in Script Builder (Step 2).
Q: Why isn’t my new CAD code opening a protocol?
A: This is usually due to a "mismatch." Ensure the code entered in Total Response is a 100% exact match (including spaces and symbols) to the string sent by your CAD.
Q: Can I map multiple CAD codes to the same protocol?
A: Yes. Use the Default Incident Types (Collection) feature in Script Builder to link multiple codes (like
MVAandMVA-INJ) to a single script.
Pre-Requisites
Before beginning the mapping process, ensure you have the following:
Administrative Access: You must have permissions for both the Administrator Module and Script Builder.
The Exact CAD String: Obtain the literal code string from your CAD administrator (e.g.,
VEH_FIREvs.Vehicle Fire).Protocol Alignment: Identify which existing protocol (or new script) should be triggered by this code.
🏗️ Step 1: Add the New Code (Administrator Module)
Before Total Response recognizes a new CAD code, it must be registered in the system database.
Navigate to:
CAD AddIn>CAD Lite>Manage Incident Type.Check for existing codes: If an old or "placeholder" code exists for this call type, double-click it to Modify it.
Add a new code: If it’s entirely new, click the Add button.
Fill in the Incident Type Detail:
CAD System: Select the discipline (Fire, Medical, Police).
Incident Type: Enter a clear name (e.g., "Vehicle Fire").
Code: (CRITICAL) Enter the exact code string sent by your CAD. This is case-sensitive and must include any specific symbols or spaces.
Save: Click Save. (Note: You may need to close and re-open the table to see the update).
🔗 Step 2: Link the Code to a Protocol (Script Builder)
Once the code exists in the database, you must tell Total Response which protocol it should launch.
For "One-to-One" Mapping
If you simply modified an existing default code in Step 1, the link is usually automatic.
Verification: Open the protocol in Script Builder, verify the code appears in the attributes, and close it.
For "Multiple Codes" to one Protocol
If you have multiple CAD codes (e.g., MVA, MVA-INJ, MVA-UNK) that should all open the same protocol:
Open the protocol in Script Builder.
Go to Default Incident Types (Collection).
Find your new codes in the list and click Add to move them into the protocol's collection.
Assign Priority Weighting: * Set a Dispatch Priority (1–100) for the new codes.
Rule of Thumb: Higher numbers (e.g., 80) take precedence over lower numbers (e.g., 30). This ensures a high-priority call type isn't accidentally downgraded by a lower-priority update.
Save All: Go to
File>Save All.
🛠️ Troubleshooting & Deletion
Protocol not opening? Double-check that the Code field in the Administrator module matches your CAD output exactly. Even a trailing space will prevent a match.
Retiring an old code? You cannot delete a code if it is currently linked to a protocol. First, remove it from the protocol in Script Builder, then delete it in the Administrator Module. If you still get an error, change the category to Obsolete.