Start with the work
Sketch the event that starts the handoff and identify the minimum fields the next operator needs. Include source context and ownership. Avoid copying complete conversations when a small reviewed summary is enough.
Build the working checklist
- Name the trigger and destination.
- Map identifiers, required fields and authoritative values.
- Set deduplication, retry and failure notification rules.
- Define who can recover a failed or partial handoff.
Check it against a real task
Test a normal item, a missing field, a duplicate and a disconnected destination. Compare the final record with the intended outcome rather than a connector’s success badge.
What to take away
Start with manual entry or a reviewed CSV if integration support is uncertain. A slower visible transfer can be a useful baseline for the later automated version.
Map the event to a useful destination record
Scroll horizontally to read all columns.
| Element | Example | Verification |
|---|---|---|
| Trigger | A reviewed enquiry is ready for follow-up | The same item cannot be processed twice unnoticed |
| Identifier | The agreed enquiry or account key | A retry updates the intended record |
| Required payload | Source, short context, status and owner | A destination operator can take the next action |
| Failure route | A visible queue with a recovery owner | Missing fields and unavailable destinations are visible |
| Completion | The correct record exists and is assigned | A successful connector run is not the only evidence |
A worked handoff
An enquiry qualifies for a consultant. The operator transfers its source, request summary, qualification decision and owner to the shared record. A notification may accompany the transfer, but the notification is not the record. If the destination is unavailable, the enquiry remains in a recoverable queue instead of disappearing into an email that nobody owns.
Test before increasing the flow
- Move one normal item and inspect every required field at the destination.
- Repeat the event and confirm that the duplicate rule works.
- Remove a required field and confirm the failure is visible.
- Interrupt the destination, recover the item and check that the retry does not create a second customer action.
Working files
Blank templates for your own planning. These contain no customer records and are not submitted to Sales Fit Lab.
A source-to-destination mapping sheet including identifiers, conflicts and recovery.