{
  "edition": {
    "edition": "2026-09-06-draft-01",
    "language": "en",
    "publicationState": "published",
    "sourceRevision": "a7e788eb4b151fd92c1f58153e015773e3a829af",
    "projectCount": 67,
    "documentCount": 94,
    "skillCount": 10,
    "archivePath": "library.zip",
    "archiveBytes": 181812,
    "releasedAt": "2026-09-08T05:03:11.129+00:00"
  },
  "access": {
    "released": true,
    "rehearsal": false
  },
  "project": "desktop/calling-follow-up-desk.md",
  "markdown": "https://legion.tw/api/projects/packet.md/desktop/calling-follow-up-desk.md?edition=2026-09-06-draft-01",
  "documents": [
    {
      "path": "desktop/README.md",
      "text": "# Native desktop applications\n\n[All project types](../README.md) · [Shared launch](../shared/launch.md)\n\nBuild a native Tauri application around the person's work or interests. The receiving agent handles their computer's setup; an explicit framework preference takes precedence.\n\n## Projects to build\n\n- [Calling and follow-up desk](calling-follow-up-desk.md)\n- [Quote and estimate builder](quote-estimate-builder.md)\n- [Photo-to-report desk with an AI colleague](ai-photo-report-desk.md)\n- [Orders and production board](orders-production-board.md)\n- [Equipment checkout and maintenance book](equipment-checkout-book.md)\n- [Booking and session desk](booking-session-desk.md)\n- [Meme and GIF studio](meme-gif-studio.md)\n- [Soundboard](soundboard.md)\n- [Game-show host](game-show-host.md)\n- [Music playground](music-playground.md)\n- [Animated desktop pet](desktop-pet.md)\n- [Tabletop atmosphere controller](tabletop-atmosphere.md)\n- [Ridiculous tournament simulator](ridiculous-tournament.md)\n- [Personal AI chat app with bring-your-own-key access](byok-chat.md)\n\nThese are instructions for projects you can build with your coding agent.\n"
    },
    {
      "path": "desktop/calling-follow-up-desk.md",
      "text": "# Build a calling and follow-up desk\n\nBuild 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.\n\nRead 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.\n\n## Learn the calling job\n\nAsk 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.\n\nShape 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.\n\n## Stay with the conversation\n\nThe 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.\n\nImagine 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.\n\nLet 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.\n\n## Bring the spreadsheet along\n\nImport 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.\n\nGive 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.\n\nExport 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.\n\n## Make a real calling session easier\n\nGive 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.\n\nComplete 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.\n\nThrough 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.\n\nA 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.\n"
    }
  ]
}