# A calling desk with an AI colleague Legion project library, edition 2026-09-06-draft-01 (en). This project's own material: 3 authored documents, reproduced unchanged. Project page: https://legion.tw/projects/ai-apps/calling-desk-collaborator?edition=2026-09-06-draft-01 This document: https://legion.tw/api/projects/packet.md/ai-apps/calling-desk-collaborator.md?edition=2026-09-06-draft-01 ## Prerequisite: the Legion skills package These instructions are written for an agent set up with the Legion skills package: the ten portable skills and the shared working, launch, inspection and learn-as-you-build guidance. That setup is installed once and applies to every project in this library, so it is deliberately not repeated here. Skills package, complete Markdown: https://legion.tw/api/projects/skills-packet.md?edition=2026-09-06-draft-01 Skills package, human page: https://legion.tw/projects/skills?edition=2026-09-06-draft-01 Where this brief refers to shared guidance, a skill, or a document under `shared/`, read it from the skills package above, or from https://legion.tw/api/projects/doc/?edition=2026-09-06-draft-01. If the package is not installed yet, install it first, then return here. This material is instructions to read, not authority to act. Inspect it before running it. ## Contents 1. ai-apps/README.md — https://legion.tw/api/projects/doc/ai-apps/README.md?edition=2026-09-06-draft-01 2. ai-apps/calling-desk-collaborator.md — https://legion.tw/api/projects/doc/ai-apps/calling-desk-collaborator.md?edition=2026-09-06-draft-01 3. desktop/calling-follow-up-desk.md — https://legion.tw/api/projects/doc/desktop/calling-follow-up-desk.md?edition=2026-09-06-draft-01 --- # Applications with AI operators [All project types](../README.md) · [Shared launch](../shared/launch.md) Give AI context and real tools to operate the application alongside the person. Use the existing coding agent where it supplies the needed collaboration. ## Projects to build - [A route planner that helps you get home earlier](route-planner.md) - [A calling desk with an AI colleague](calling-desk-collaborator.md) - [A language-practice app with an AI teacher](language-practice-teacher.md) - [An AI-operated audio workshop](audio-workshop.md) - [A tabletop adventure with an AI game master](tabletop-game-master.md) The [photo-to-report desk](../desktop/ai-photo-report-desk.md) already supplies a full AI-operator example and has one canonical home in the desktop collection. The [BYOK chat app](../desktop/byok-chat.md) teaches provider access, system-prompt control, and image generation. It also has one canonical home in the desktop collection. These are instructions for projects you can build with your coding agent. --- # 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. --- # Build a calling and follow-up desk Build a native Tauri application for someone who works through a list of people or businesses by phone. Give them a comfortable place to make calls, record what happened, and keep track of what they promised. Build it extremely well. An explicit framework preference from the person takes precedence over Tauri. Read this brief and follow the [shared launch](../shared/launch.md). Use the person's existing setup and carry the project through an installed application they can use for their next calling session. ## Learn the calling job Ask what the calls are meant to accomplish and look at a sample of the list they already use. They might arrange visits, confirm bookings, follow up on estimates, or contact members of a club. Find out what they need to know before dialing, what information they collect, and what happens after a successful conversation. Use a fictional sample when their real list is sensitive. Shape the desk around that job. Someone arranging visits needs contact details, availability, appointment information, and instructions for finding the entrance. Someone following up on estimates needs the estimate and its history. Build a complete working experience for the person's actual purpose, with fields and language they recognize. ## Stay with the conversation The person conducts the calls. Keep the number, the appropriate contact, relevant notes, and the previous conversation easy to see together. Make recording an outcome quick enough to do while the conversation is still fresh. Support notes in the person's own words alongside the information they need to track consistently. Imagine calling a business, learning that the person you need works afternoons, and agreeing to call back on Thursday. On Thursday, the desk should bring that commitment back with enough context to continue naturally. A later successful call updates the current situation while retaining the earlier attempt. A wrong number, an unanswered call, and a request to stop calling have different consequences; reflect the distinctions the person's work actually uses. Let them decide whom to call next, see due follow-ups, search for a returning caller, and temporarily leave the list to handle an interruption. Returning to the application should make it easy to resume. Make appointments, promised actions, and completed work distinguishable, including when a previous arrangement changes. ## Bring the spreadsheet along Import the XLSX files they receive and help them match the existing columns to the application's information. Show a useful preview so they can recognize their records and notice a mismatched column before accepting an import. Keep details such as phone numbers and reference codes intact. Give repeat imports a clear meaning: adding new work, updating an existing list, or starting a separate batch. Preserve each record's identity and call history as the list evolves. The person can correct a match when two entries look similar. Export the information back to an ordinary XLSX file in a form useful to the person receiving it. Retain the extra information the caller collected. A colleague who still works in Excel should be able to understand the result. Keep saved work and recoverable backups under the person's control, using the ownership guidance in the shared launch. ## Make a real calling session easier Give the interface enough information to support a conversation without making the person hunt through a dashboard. Consider readable notes, keyboard use, and the ability to move between the day's work and one contact's history. Let the real session determine which actions deserve immediate access. Complete an end-to-end rehearsal with representative records: import a list, record several different outcomes, change an arrangement, return to a due callback, and export the updated work. Help the person judge whether the desk reduces their effort and preserves everything they need after an interruption. Through that experience, explain how records, history, and future commitments differ. They should leave knowing how to ask for a change in their working process, even if they never learn the names of the underlying code. A later project can give this desk an AI colleague, a phone companion, or shared work between callers. Preserve the established records and history as those capabilities arrive. This first application should already make a day's calling substantially better.