Confirm what each interface allows
Review vendor documentation, available access and example records. Determine what can be read or written and what restrictions apply. One enquiry becoming a customer record is a possible flow to assess, not a claim of a delivered integration. Unsupported operations remain outside the agreed connection.
Make the transfer checkable
Define required fields, validation, identifiers and duplicate handling before information moves. Agree how completion is confirmed and how incomplete work is recovered when the destination is unavailable. Permissions must match the task, and a failed transfer should remain visible rather than silently leave inconsistent records.
Bring one concrete exchange
Share the source, destination, documentation and a safe sample record. Explain the current manual steps and who resolves exceptions. We scope the connection and verify agreed success and failure cases. Additional systems, broader data access and actions beyond the named exchange require separate assessment.