--- title: "Emergency MEP Service-to-Billing Workflows | Stacksync" description: "Carry emergency callout authorization and performed-work evidence into a clear billing handoff." canonical: https://www.stacksync.com/use-case/emergency-mep-service-billing-workflow last_modified: 2026-09-21 --- Commercial HVAC, plumbing and electrical contractors # Emergency MEP Service-to-Billing Workflows > 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 ![Commercial HVAC, plumbing and electrical contractors systems connected through Stacksync two-way sync: Salesforce, NetSuite, HubSpot, Acumatica, Supabase](https://www.stacksync.com/images/industry-heroes/icp-commercial-mep-contractors-800.webp) Coordinate emergency HVAC, electrical and plumbing calls from intake through closeout. The workflow connects site identity, dispatch decisions, rate authorization and actual work, then prepares the finance handoff. It keeps access permission, purchasing authority and additional repair approval distinct. Urgent work gets done while the evidence needed to explain and bill it arrives later. [Book a demo](https://www.stacksync.com/book-a-demo) Explore your process in a demo, or get our shared two-way sync architecture guide. When this fits ## Built for this operating problem US commercial HVAC, plumbing, electrical and multi-trade service groups with 100–1,000 employees. ### Capture the commercial boundary Record who requested the visit, who authorized charges and which rate or spending limit applies. ### Separate response from extra work Keep the initial callout and later recommended or approved repairs linked without treating all activity as one authorization. ### Give missing evidence an owner Route rate, site and acceptance questions to the person able to resolve them before the packet reaches finance. The process, end to end ## Follow the work across systems a tenant calls about a plumbing issue after hours, while the building owner controls purchasing. Dispatch follows the contractor's policy; the workflow preserves that decision and routes the separate commercial approval instead of leaving billing to reconstruct it later. [Salesforce connector](https://www.stacksync.com/connectors/salesforce) [NetSuite connector](https://www.stacksync.com/connectors/netsuite) Scope your implementation ## Bring these details to the demo - Emergency dispatch policy - Rate and authorization rules - Visit and additional-scope records - Finance handoff destination Review [current platform pricing](https://www.stacksync.com/pricing) alongside the records, volume, and actions in your process. Use your own operating baseline to evaluate the economics. [Book a demo](https://www.stacksync.com/book-a-demo) Explore your process in a demo, or get our shared two-way sync architecture guide. From foundation to action ## One connected operating process 01 ### [Two-way sync](https://www.stacksync.com/two-way-sync) Keep shared customer, order, and operational records aligned, with clear field ownership. Explore two-way sync 02 ### [Workflows](https://www.stacksync.com/workflow-automation) Move approved work between systems, assign exceptions, and confirm the result. Explore workflows 03 ### [AI agents (Genies)](https://www.stacksync.com/ai-agents) Investigate cross-system questions, assemble the evidence, and prepare the next action. Explore ai agents (genies) 04 ### [EDI](https://www.stacksync.com/edi) Connect trading-partner documents to operational records and exception handling. Explore edi Go deeper ## Implementation guides for your team - [Emergency MEP Service Calls: Route Dispatch, Rate Approval, and Billable Work](https://www.stacksync.com/blog/emergency-mep-service-calls-route-dispatch-rate-approval-and-billable-work) Coordinate emergency HVAC, electrical and plumbing callouts without losing authorization, rate and visit evidence. - [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) Route multi-trade service renewals through scope, pricing and customer approval before activating the next contract term. [Explore all commercial HVAC, plumbing and electrical contractors integration and automation guides ↗](https://www.stacksync.com/industry/construction/commercial-mep-contractors) ## Common evaluation questions ### Does this make site-safety decisions? No. Qualified personnel and operating procedures control the physical response. The workflow coordinates administrative evidence. ### Can we retain manual invoice approval? Yes. A complete, owned billing packet is a useful first automation scope. ### What should we measure? Track missing-authorization cases, evidence-chasing time and duplicate handoffs for comparable call types. ### Does two-way sync need to be in place before the emergency workflow? Start with two-way sync. The workflow can mark a caller's billing identity unresolved, but it runs more cleanly when Salesforce and NetSuite already agree on the site, the billing customer and the job reference, so a callout lands on a known record. Then add workflows to carry the dispatch decision, rate authorization and performed work into the finance handoff. Genies follow when supervisors want the technician's notes, parts and acceptance evidence assembled into a packet with open questions marked. EDI applies later to equipment purchase orders from HVAC distributors, not to service billing.