| A permitted Follow Up Boss export shows an assigned lead without a recorded acknowledgment. |
Prepare a handoff review item with the lead identifier, source reference and missing acceptance. Draft an internal Gmail request using the team-approved process; integration or export access must be confirmed during discovery. |
The team lead confirms the intended recipient and approves any routing change. The receiving agent acknowledges the specific handoff. |
The team can distinguish an assigned record from an accepted responsibility. |
| A recorded next step in an approved Real Geeks export is marked overdue or lacks an owner. |
Collect the recorded activity and relevant permitted context into a review queue. Flag absent information and prepare a clarification draft rather than assuming the agent missed an action. |
The agent checks the record and chooses the next action. The team lead approves a proposed reassignment, and a person sends any resulting client message. |
The next step has a verified owner or remains visibly unresolved. |
| A permitted Dotloop checklist extract and the team register name different owners for an administrative request. |
Show both references and their owner labels in a reconciliation task. Keep the records separate until the coordinator confirms the approved checklist and the relevant task. |
The transaction coordinator resolves the administrative ownership question with the agent. The team lead reviews any routing change; the assistant gives no legal interpretation. |
An accountable decision replaces conflicting task labels without changing transaction terms. |
| An agent requests a client follow-up draft after confirming the recorded next step. |
Prepare an unsent Gmail draft from approved facts, with the intended recipient and proposed attachments available for review. List open questions separately so uncertainty cannot disappear into polished wording. |
The agent approves the current content and sends the message. Material edits return it for review; commitments remain with authorized people. |
The agent can inspect the source and message together before communicating externally. |
| A planned team review needs outstanding handoffs from permitted records. |
Assemble unacknowledged assignments, CRM next-step questions and checklist owner conflicts into an administrative brief. A Google Calendar event can provide a review reference only where permitted access is confirmed. |
The team lead reviews priorities and approves ownership changes. Agents and the coordinator accept their next tasks through the agreed process. |
The review ends with named owners and visible unresolved questions instead of a generic status digest. |