# A calling desk with an AI colleague

Extend the [calling and follow-up desk](../desktop/calling-follow-up-desk.md) so the person's existing coding agent can help operate the workload. Build it extremely well. The caller should be able to discuss the work, delegate useful organization, and see the result in the desk they already use. Follow the [shared launch](../shared/launch.md).

Keep the native Tauri application and its accumulated contacts, call history, imports, and exports. If this is the person's first project from the collection, build the underlying calling experience as part of delivering this one.

## Give the colleague enough context to help

Discover what a successful calling session accomplishes for this person. Give the agent access to the actual records, previous attempts, current outcomes, promised actions, and relevant dates. Let it see which list or contact the person is looking at, and provide proper application tools for the work it can perform.

Reuse the existing agent's installation and account through an appropriate supported connection. Preserve useful project understanding across sessions so the caller can return to the job without explaining the entire organization again.

Make requests such as “Who should I call this afternoon?” genuinely useful. The agent can assemble a queue from due callbacks, contact availability, unfinished arrangements, and the person's priorities. Give it room to make judgments and explain the important ones. The caller can adjust that queue directly, and the agent should continue from the changed state.

## Help before and after the call

The person makes the calls. Before one, show the information needed to continue the relationship: who they need, why they are calling, and what was said last time. The agent can prepare a short reminder or identify an unresolved question from the record.

Afterward, let the caller describe what happened in ordinary language. For example: “She can meet Tuesday after two, but wants the sample report first. I said I'd send it today and confirm tomorrow.” The agent should record the conversation, preserve the appointment's tentative status, and arrange the two follow-ups in the desk.

Show those changes where the person normally works. Make correction straightforward when a spoken account was misunderstood or the caller changes a detail. Preserve the sequence of attempts and commitments while updating the current situation.

The agent can notice an approaching callback or requested information still awaiting preparation. Give the person a clear choice about its ongoing responsibility: help during an open session, or an explicitly arranged background follow-up using the shared launch's continuity guidance.

## Keep preparation and action clear

Use the desk's operations to make actual changes, with returned results that tell the agent and person what happened. A prepared message, a sent message, a suggested appointment, and a confirmed appointment have different effects on the job.

Start with the person's chosen authority for organizing records and preparing material. Add communication or calendar actions when they want those connections, with the same clarity about what the agent is authorized to do. Let the caller recover or correct an unintended record change through the application.

## Deliver a working colleague

Use fictional contacts to rehearse a session: prepare the afternoon's queue, describe a call, inspect the resulting commitments, correct a detail manually, and ask the agent what remains. Preserve the desk's existing working and export routines.

Teach the person what changed: the agent can now reason from their ongoing work and act through the software's own capabilities. Their conversation and the application should support each other, including when they resume tomorrow.