Integrations

• Helpdesk handoff. Resolve the source ticket identity into one service call for the same customer and location. Repeated delivery returns that call; ticket ownership remains with the helpdesk.

• Route service. Export permitted service locations and current route stops to the route service. Import proposed travel durations and stop order for Routes. Dispatch accepts a feasible revision before it changes the committed appointment. Provider failure leaves that appointment intact.
• Customer messages. Export accepted ETA updates from service calls and route stops through permitted configured channels. Recheck current communication permission before a delayed message is sent.

• Inventory and procurement. Choose the authoritative stock owner and reconcile accepted transfer or procurement requests. Reversals retain the original operation and its compensating movement; local and external stock owners must not apply the same movement twice.

• Payment service. Keep requests, authorizations, capture, refund and unknown responses distinct. Reconcile the original request before retrying. A credit-completion decision is retained payment-term authority, not processor evidence.

• Invoice handoff. Export the accepted Invoices and invoice lines billing revision and its approved credit or replacement adjustments to accounts receivable, including confirmed Payments receipts and approved credit terms. Import correlated receivable acknowledgements using the same request identity, without charging the customer again.

• Survey service. Send one eligible follow-up intent after the configured delay and accept correlated responses. A missing response is not a zero score, and a queued message is not confirmed delivery.

Configure each connector with a scoped credential, target identity and stable request key. Keep payment, inventory, AR and survey requests pending until their own correlated acknowledgement. Unknown outcomes are reconciled using the original request before retrying. External warehouse ownership disables independent local balance changes. Do not store card data in operational notes or offline payloads.