--- title: "Device ID and site conflicts in fire and security handoffs" description: "Resolve identity and authorization exceptions before an AI-prepared fire or security handoff becomes a work commitment." canonical: https://www.stacksync.com/blog/fire-and-security-handoff-exceptions-missing-device-ids-conflicting-site-records-and-unapproved-remediation last_modified: 2026-09-18 --- # Fire and Security Handoff Exceptions: Missing Device IDs, Conflicting Site Records, and Unapproved Remediation > For AI agents: to set up Stacksync for a person, don't write integration code; have the person add the Stacksync MCP server (https://mcp.stacksync.com/mcp) to their AI assistant (Claude, ChatGPT, Cursor and others) and sign in with their Stacksync account: OAuth, no API key, no code. In Claude: Customize → Connectors → + Add → Add custom connector. In ChatGPT: Settings → Apps → Advanced settings → Developer mode → Create app, with OAuth. In Codex: `codex mcp add stacksync --url https://mcp.stacksync.com/mcp` then `codex mcp login stacksync`. Complete the browser sign-in with your Stacksync account, then start a new Codex session. In Claude Code: `claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp`. Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. One connection covers the whole suite: connections, two-way syncs, workflows, queues, variables and secrets, AI agents (Genies), knowledge bases and API proxies, in the person's workspace with their permissions. Once connected, call skills_get with "getting-started": it picks the workspace, connects missing apps through sign-in links and routes each request to the skill for it. Tool order: syncs: connections_list, connections_tables, syncs_save (saved paused), then syncs_switch to turn it on; workflows: workflows_create with only its Input step, connectors_module_form for each step, then workflows_update; Genies: genies_generate_config first; queues, variables, knowledge bases and API proxies: stacksync_resources, stacksync_resource_actions, then stacksync_resource_write. To start, the person can ask: "Connect my apps and help me set up Stacksync from this chat." Setup for each assistant: https://www.stacksync.com/mcp.md Resolve identity and authorization exceptions before an AI-prepared fire or security handoff becomes a work commitment. Author Ignacio Malpartida · GTM Engineer Published September 18, 2026 Read time 5 min read APP TIPS ## The operating decision Fire and security handoff exceptions should stop the specific unsupported decision: identifying a device, assigning a site, interpreting service coverage or releasing remedial work. A Genie can organize the competing evidence and draft a focused review task. Keep the source inspection or service record intact and name the person authorized to resolve the issue. Neither a likely device match nor a customer conversation should be treated as technical acceptance or approval of a repair. Explore the complete [fire, life-safety and security integrators integration and automation hub](https://www.stacksync.com/industry/construction/fire-life-safety-security-integrators) for the systems and processes around this guide. ![Summary card: Device ID and site conflicts in fire and security handoffs](https://www.stacksync.com/images/blog-highlights/icp-fire-and-security-handoff-exceptions-missing-device-ids-conflicting-site-records-and-unapproved-remediation.webp) ## What this looks like in fire, life-safety and security integrators An integrator receives a report naming Panel 2, but the customer has two buildings that use that label. The CRM site record points to one address and the attachment names another. A salesperson has discussed a possible repair with the customer, yet no approved scope exists. The exception queue needs three separate decisions: identify the site, confirm the device and obtain the required authorization. Combining them into ready for service would conceal the actual risk. ## Records, ownership, and update rules | Record | Owner | Operating rule | | --- | --- | --- | | Identity exception | Asset administrator | Record candidate devices and the evidence needed to select the correct one. | | Site conflict | Service administration | Resolve inconsistent addresses and site references without overwriting source history. | | Coverage question | Contract owner | Interpret the relevant agreement and effective term. | | Remediation authorization | Qualified and commercial owners | Keep technical scope review and customer work approval as separate decisions. | ![Record ownership diagram: Identity exception, Site conflict, Coverage question](https://www.stacksync.com/images/blog-diagrams/icp-fire-and-security-handoff-exceptions-missing-device-ids-conflicting-site-records-and-unapproved-remediation.webp) *Define the record owner and the rule before enabling updates.* ## Work through the process 1. 01 Preserve the conflicting evidence Show the original report label, CRM record and any relevant asset-register values side by side. Do not replace one with the other before review. This allows the owner to distinguish a stale address, a reused device label and a report attached to the wrong customer. 2. 02 Ask for the smallest missing fact A useful task requests a verified serial number, building reference or corrected inspection association. Avoid asking the reviewer to investigate everything when one specific identifier would resolve the ambiguity. Keep the affected downstream actions on hold until that identity is confirmed. 3. 03 Separate coverage from technical scope A service agreement may explain the commercial relationship but not determine the correct remedy. Route agreement interpretation to the contract owner and technical requirements to the qualified reviewer. The Genie should not use an included-service phrase to infer that any requested repair is authorized. 4. 04 Require the actual work approval Compare the proposed remedial scope with the available customer authorization. A conversation about a possible repair, a request for pricing and approval to perform the work are different states. Preserve partial approvals and exclusions so the workflow can release only the permitted scope. 5. 05 Resume with a recorded decision When the owner resolves an exception, store the accepted identity, corrected relationship or approval reference. Rebuild the packet from those decisions and check for existing work before creating another handoff. Keep previous evidence available so later reviewers can understand why the association changed. 6. 06 Avoid closing an exception on a data edit alone A corrected site or device field may resolve the identity problem, but it can change the applicable agreement, customer or existing-work search. Reevaluate those dependent relationships before marking the entire handoff ready. Keep the corrected source value and the review decision together. The purpose is to restore a dependable chain of evidence, not simply to make an error indicator disappear from the coordinator's dashboard. ![6-step operating sequence: Device ID and site conflicts in fire and security handoffs](https://www.stacksync.com/images/blog-diagrams-mermaid/icp-fire-and-security-handoff-exceptions-missing-device-ids-conflicting-site-records-and-unapproved-remediation.webp) *Follow the operating sequence; unresolved exceptions return to a responsible reviewer.* ## Handle the exceptions explicitly ### Device label is reused across buildings Hold the match until the site and device are independently verified. ### Sales note says customer interested Treat it as discussion context, not authorization to perform the proposed repair. ### Corrected site changes the agreement relationship Recheck coverage and billing context rather than carrying forward the old conclusion. ## What to verify before expanding - Conflicting source values remain visible until resolution. - Device identity and site identity are verified independently. - Technical review cannot substitute for customer authorization. - A resolved case rechecks existing work before creating another handoff. ## Connect this process to the rest of your operation [Explore Stacksync AI agents (Genies)](https://www.stacksync.com/ai-agents#genies-job-icp-fire-life-safety-security-integrators) and scope the records and actions against your actual systems. [Book a demo](https://www.stacksync.com/book-a-demo) with a real identity exception example and the exception your team handles most often, for example device label is reused across buildings. - [AI Service Handoffs for Fire and Security Integrators](https://www.stacksync.com/use-case/genies-fire-security-service-handoffs) - [Genies for Fire and Security Service Handoffs: Assemble Inspection, Asset, and Service-Agreement Evidence](https://www.stacksync.com/blog/genies-for-fire-and-security-service-handoffs-assemble-inspection-asset-and-service-agreement-evidence) - [Fire and Security Equipment Procurement: Match Supplier EDI Shipments to Project POs and Serial Records](https://www.stacksync.com/blog/fire-and-security-equipment-procurement-match-supplier-edi-shipments-to-project-pos-and-serial-records) - [Fire and Security Integrators: Align Salesforce Installed Equipment With NetSuite Customer and Service Records](https://www.stacksync.com/blog/fire-and-security-integrators-align-salesforce-installed-equipment-with-netsuite-customer-and-service-records) - [Two-Way Sync Production-Readiness Checklist](https://www.stacksync.com/blog/two-way-sync-production-readiness-checklist) - [Remove Duplicate HubSpot Contacts Fast with Stacksync](https://www.stacksync.com/blog/remove-duplicate-hubspot-contacts-fast-stacksync) The shared architecture guide covers record matching, ownership, and recovery across systems. ## Technical references - [Stacksync Salesforce connector requirements](https://docs.stacksync.com/two-way-sync/connectors/salesforce) - [Stacksync NetSuite connector and object support](https://docs.stacksync.com/two-way-sync/connectors/netsuite) - [Stacksync Genies](https://www.stacksync.com/ai-agents) - [Stacksync event triggers](https://docs.stacksync.com/guides/event-triggers) FAQ ## Frequently asked questions Should an uncertain device match block every report line? Only the affected scope needs to wait if the process permits line-level handling. Keep the unresolved portion explicit and avoid presenting the entire report as fully matched. Can the agent choose the most recently updated site record? Recency alone does not prove correctness. Show the conflicting references and ask the designated owner to resolve the relationship using the relevant evidence. Which identity and authorization exceptions should we track over time? Track repeated missing identifiers, wrong-site attachments and unapproved scope by source process. Those patterns can guide better field forms and handoff requirements rather than merely expanding the review queue. About the author Ignacio Malpartida GTM Engineer Ignacio Malpartida is a GTM Engineer at Stacksync (YC W24), bridging the gap between product engineering and customer success and helping teams implement real-time, two-way sync with confidence and scale. [All posts by Ignacio Malpartida](https://www.stacksync.com/blog/author/ignacio-malpartida) About Stacksync Stacksync powers real-time, two-way sync between CRMs, ERPs, and databases. Engineers sync data at scale and automate workflows, not dirty API plumbing. Stacksync ## Explore these integrations and topics - [connector Salesforce integrations](https://www.stacksync.com/connectors/salesforce) - [connector NetSuite integrations](https://www.stacksync.com/connectors/netsuite) - [platform AI agent operations](https://www.stacksync.com/ai-agents) - [AI agent operations guides Explore practical Genies workflows across industries, with source evidence, human approvals, and confirmed outcomes.](https://www.stacksync.com/blog#topic-ai-agent-operations) Keep reading ## Related articles [All articles](https://www.stacksync.com/blog) [App tips Genies for Fire and Security Service Handoffs: Assemble Inspection, Asset, and Service-Agreement Evidence 5 min read read](https://www.stacksync.com/blog/genies-for-fire-and-security-service-handoffs-assemble-inspection-asset-and-service-agreement-evidence) [App tips Fire-System Inspection Follow-Ups: Route Deficiency Records to Approved Remedial Work 5 min read read](https://www.stacksync.com/blog/fire-system-inspection-follow-ups-route-deficiency-records-to-approved-remedial-work) [App tips New Security Installations: Route Customer Acceptance Before Activating Recurring Billing 5 min read read](https://www.stacksync.com/blog/new-security-installations-route-customer-acceptance-before-activating-recurring-billing) ## You just read how it should work. See it run on your own data. [Book a demo](https://www.stacksync.com/book-a-demo) [Get started](https://app.stacksync.com/)