Connections to configure

• Clinical systems. Keep clinical care records in the customer’s clinical system. If relationship staff need an external reference for nonclinical follow-through, agree the permitted information and the people allowed to inspect it.
• Email systems. Configure a connection if the team wants to bring correspondence into relationship activity. Match each interaction to the correct opportunity and agree what outcome evidence the owner must check.
• Finance systems. Connect the chosen finance system separately when commercial outcomes need downstream follow-through. Preserve the difference between expected opportunity value in USD and financial postings in that system.
• Downstream action systems. If a correction depends on an external effect, agree the confirmation reference and the evidence that establishes completion before clearing a pending compensation.

App Administrator establishes organization and membership scope with the team responsible for each connection. Relationship Owner checks that imported context belongs to the intended opportunity. Sales Manager agrees how downstream confirmation is reviewed when it affects a business action.

Use stable operation keys for guarded requests, compare the current revision before writing and preserve the original action receipt. Equivalent retries should reuse the result; conflicting input requires investigation. A stored external reference must point to evidence the authorized reviewer can evaluate.

Rehearse a wrong organization, a stale revision and a delayed downstream confirmation during implementation. Decide who investigates each exception before the connection joins the operating process.