Connected is the first check, not the final approval.
A Bonzo connection can work while officer assignment, stage behavior or appointment instructions still need review. Use a full checklist before letting an assistant handle real conversations.
Verify the identity behind the connection
Connect through the authorized account setup and confirm the expected officer is present. Then inspect the available ownership evidence and pipeline scope. Do not infer that the assistant can inspect every team record just because the API connection reports success.
Keep API keys and account credentials out of public demos, screenshots and ordinary chat messages. If the correct officer cannot be verified, resolve the account or permission issue rather than granting broader outreach scope to bypass the warning.
Review every relevant stage
Inventory the pipeline
Confirm that all relevant stages are visible, not just algorithmically flagged stages.
Choose explicit behavior
Distinguish proactive contact, inbound replies, pipeline-only work and exclusions.
Check record ownership
Review shared-stage assignment and ambiguous records before activation.
Preserve the decision
Record why each stage has its mode so later changes can be reviewed.
Configure the whole conversation
| Setup area | Review | Boundary |
|---|---|---|
| Officer and assistant details | Correct names, relevant context and honest representation | Do not copy another officer’s instructions |
| Contact and follow-up settings | Hours, timezone, cadence and holds within company rules | Do not confuse style with contact permission |
| Appointment instructions | Booking details and the correct officer recipient | Outside calendar conflicts need separate verification |
| Human handoff | What requires the officer and how takeover works | A notice must have a recipient and completion check |
Test before widening activation
Use fictional cases that exercise prior answers, changed goals, a pricing question, a stop request and an appointment. Inspect the generated conversation and the intended next action. The public browser demo does not send real SMS; a production integration test is a separate controlled workflow.
After any approved activation, verify actual delivery and stored records using a narrow scope. Keep paused and excluded records separate from failures. If a stage, officer or recipient changes, rerun the affected checks instead of assuming the original setup still proves the new configuration.