One team needs clear ownership for every conversation.
A team assistant should preserve who owns the inquiry and how that officer works. A shared pipeline is not a reason to send every borrower the same introduction or booking instructions.
Separate shared standards from officer choices
Company rules define the boundaries. Officer settings supply the relevant name, conversation style, working hours and booking information within those boundaries. Verify the mapping between the connected Bonzo account, officer and actual lead ownership before enabling outreach.
LoanWick supports officer-specific setup and company controls. Treat a successful API connection and a correctly matched officer as different checks. Team access, notification recipients and permitted stages should be reviewed in the actual workspace rather than inferred from an account label.
Create an ownership checklist
| Area | Expected outcome | Exception to test |
|---|---|---|
| Lead assignment | The correct officer owns the conversation | Shared-stage records assigned elsewhere |
| Assistant instructions | The officer’s context is used | Another officer’s name or booking details |
| Human takeover | Active human work remains protected | Overlapping replies to the same thread |
| Notices | The enabled recipient is correct | A former teammate’s notification address |
Roll out a team without hiding differences
A team with different lead sources and coverage cannot be compared by appointments alone. Use the same period and outcome definitions, and keep paused, excluded and opted-out records out of the unanswered eligible denominator. Expansion should follow verified configuration and reviewed conversation quality, not merely a connected status.
Pilot one defined scope
Select permitted stages and a small set of synthetic scenarios before wider activation.
Check each officer
Review assignment, instructions, contact windows and the intended notice channel.
Inspect shared stages
Confirm that available ownership evidence supports the planned behavior.
Compare fairly
Report eligible volume and exceptions by officer; do not rank them on raw message totals.
A fictional shared-stage review
SituationTwo officers use the same stage name but different consultation instructions.
Useful testGive each synthetic record a known owner and check the resulting next step.
BoundaryAn ambiguous owner should trigger review, not a guess about which officer to represent.