--- title: "Emergency MEP callout workflow from dispatch to billing" description: "Coordinate emergency HVAC, electrical and plumbing callouts without losing authorization, rate and visit evidence." canonical: https://www.stacksync.com/blog/emergency-mep-service-calls-route-dispatch-rate-approval-and-billable-work last_modified: 2026-09-18 --- # Emergency MEP Service Calls: Route Dispatch, Rate Approval, and Billable Work > 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 Coordinate emergency HVAC, electrical and plumbing callouts without losing authorization, rate and visit evidence. Author Ignacio Malpartida · GTM Engineer Published September 18, 2026 Read time 5 min read APP TIPS ## The operating decision An emergency MEP service workflow should connect the request, dispatch decision, commercial authorization and performed work while keeping each state explicit. Capture who requested help, the affected site, the approved rate or spending limit, and the person responsible for resolving exceptions. Dispatch may need to act before every commercial detail is available, but the workflow should preserve that decision and route missing evidence promptly rather than treating urgency as blanket billing approval. Explore the complete [commercial HVAC, plumbing and electrical contractors integration and automation hub](https://www.stacksync.com/industry/construction/commercial-mep-contractors) for the systems and processes around this guide. ![Summary card: Emergency MEP callout workflow from dispatch to billing](https://www.stacksync.com/images/blog-highlights/icp-emergency-mep-service-calls-route-dispatch-rate-approval-and-billable-work.webp) ## What this looks like in commercial HVAC, plumbing and electrical contractors A plumbing contractor receives a late-night call from a commercial tenant. The tenant can grant site access but is not the building owner's authorized purchaser. Dispatch sends a technician under the company's emergency policy, while the account manager seeks approval for additional work. The technician completes stabilization and recommends a larger repair. The workflow must distinguish the first authorized response from the later repair scope so finance does not bill both under an assumed approval. ## Records, ownership, and update rules | Record | Owner | Operating rule | | --- | --- | --- | | Emergency request | Customer service | Capture caller, site, issue and time without assuming purchasing authority. | | Dispatch decision | Duty dispatcher | Record assigned visit and the operating policy used for release. | | Rate and spending authorization | Authorized commercial approver | Identify covered work, rate basis and any limit. | | Performed work | Technician and supervisor | Separate initial response, added work and follow-up recommendations. | ![Record ownership diagram: Emergency request, Dispatch decision, Rate and spending authorization](https://www.stacksync.com/images/blog-diagrams/icp-emergency-mep-service-calls-route-dispatch-rate-approval-and-billable-work.webp) *Define the record owner and the rule before enabling updates.* ## Work through the process 1. 01 Capture enough context to identify the job Require a site reference, contact method and description of the immediate issue. Link the request to an existing customer when verified; otherwise mark the billing identity unresolved. A rapid intake form should reduce missing essentials without requiring dispatch to invent a payer. 2. 02 Record the emergency release decision Use the contractor's approved policy for when dispatch may proceed while commercial questions remain open. Preserve who made that decision and its scope. This is an operational design choice, not a claim that every emergency permits work without customer authorization. 3. 03 Resolve rate and authority Route the applicable rate schedule, after-hours terms and spending limit to the account or commercial owner. Confirm who may approve additional work. If the caller only controls access, keep that role separate from the purchasing approver so a signed arrival record is not mistaken for financial authority. 4. 04 Split response from additional scope Have the technician report what was performed under the initial authorization and what requires a separate decision. Link photos, time and materials to the relevant visit or scope line. A recommended equipment replacement should remain a proposal until the necessary review and approval are complete. 5. 05 Prepare the billable packet Assemble the authorized rate basis, performed work and customer evidence for finance. Route any missing approval or excess amount as a specific exception. Confirm the resulting billing handoff once, using the visit reference to prevent duplicate tasks when dispatch or technician status changes repeatedly. 6. 06 Preserve the customer's original request Keep the caller's description separate from the technician's eventual diagnosis and performed work. The request explains why the crew was dispatched, while the closeout explains what actually happened. Neither should replace the other in the record. This distinction helps the account owner review a disputed emergency charge without assuming the caller accurately identified the fault or that every requested task was performed during the first visit. ![6-step operating sequence: Emergency MEP callout workflow from dispatch to billing](https://www.stacksync.com/images/blog-diagrams-mermaid/icp-emergency-mep-service-calls-route-dispatch-rate-approval-and-billable-work.webp) *Follow the operating sequence; unresolved exceptions return to a responsible reviewer.* ## Handle the exceptions explicitly ### Caller cannot authorize charges Continue only under the applicable operating policy and route the commercial decision to the proper owner. ### Work exceeds the spending limit Separate the excess scope and request the required approval before treating it as billable. ### Technician returns the next day Create a linked follow-up visit so hours and authorization do not blend with the original callout. ## What to verify before expanding - Site-access permission is distinct from purchasing authority. - The emergency-release decision has an owner and scope. - Additional work retains its own approval reference. - Repeated closeout updates do not duplicate the billing handoff. ## Connect this process to the rest of your operation [Explore Stacksync workflows](https://www.stacksync.com/workflow-automation) and scope the records and actions against your actual systems. [Book a demo](https://www.stacksync.com/book-a-demo) with a real emergency request example and the exception your team handles most often, for example caller cannot authorize charges. - [Emergency MEP Service-to-Billing Workflows](https://www.stacksync.com/use-case/emergency-mep-service-billing-workflow) - [Service Agreement Renewals for MEP Contractors: Coordinate Price Review and Customer Approval](https://www.stacksync.com/blog/service-agreement-renewals-for-mep-contractors-coordinate-price-review-and-customer-approval) - [Genies for Commercial MEP Service Closeout: Turn Technician Notes Into an Invoice-Ready Packet](https://www.stacksync.com/blog/genies-for-commercial-mep-service-closeout-turn-technician-notes-into-an-invoice-ready-packet) - [MEP Service Closeout Exceptions: Warranty Work, Callbacks, Missing Parts, and Customer Sign-Off](https://www.stacksync.com/blog/mep-service-closeout-exceptions-warranty-work-callbacks-missing-parts-and-customer-sign-off) - [Workflow Automation Tools: The Complete 2026 Guide](https://www.stacksync.com/blog/workflow-automation-tools-guide) - [Coordinate Equipment Repairs Across Service, Inventory, and Scheduling](https://www.stacksync.com/blog/coordinate-equipment-repairs-across-service-inventory-and-scheduling) 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 event triggers](https://docs.stacksync.com/guides/event-triggers) FAQ ## Frequently asked questions Can this decide whether a technician should enter an unsafe site? No. Site safety and technical response decisions belong to qualified personnel and the contractor's operating procedures. The workflow coordinates records and commercial handoffs. Should every emergency call use the same approval path? No. Existing service contracts, new customers and spending limits can require different paths. Make those conditions explicit and give dispatch a visible escalation owner. What is a useful first pilot? Choose one branch and one emergency-service category. Compare how often finance needs to chase rate approval, caller authority or visit evidence after the work is complete. 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 Integration architecture](https://www.stacksync.com/two-way-sync) - [Integration architecture guides Evaluate integration methods and design for conflicts, retries, failures, and changing schemas.](https://www.stacksync.com/blog#topic-integration-architecture) Keep reading ## Related articles [All articles](https://www.stacksync.com/blog) [App tips Coordinate Equipment Repairs Across Service, Inventory, and Scheduling 8 min read read](https://www.stacksync.com/blog/coordinate-equipment-repairs-across-service-inventory-and-scheduling) [App tips Genies for Commercial MEP Service Closeout: Turn Technician Notes Into an Invoice-Ready Packet 5 min read read](https://www.stacksync.com/blog/genies-for-commercial-mep-service-closeout-turn-technician-notes-into-an-invoice-ready-packet) [App tips MEP Service Closeout Exceptions: Warranty Work, Callbacks, Missing Parts, and Customer Sign-Off 5 min read read](https://www.stacksync.com/blog/mep-service-closeout-exceptions-warranty-work-callbacks-missing-parts-and-customer-sign-off) ## 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/)