--- name: quo-missed-call-follow-up description: Work through missed calls to a Quo number and their voicemail transcripts to decide which callers need a reply, match each caller to a contact, and draft follow-up texts for the user to approve before anything is sent. Use when the user asks about missed calls, who called back, which voicemails need an answer, or wants to catch up on calls they could not take. --- # Follow up on missed calls The job is to turn a list of unanswered calls into a short, prioritised set of people who need a reply, each with a draft the user can approve in seconds. It is not a call log dump. A good result tells the user who to call back first, why, and what to say. Keep this separate from general inbox summarising: here the unit of work is the caller who rang and was not reached, and the output ends in drafts, not a recap. ## 1. Confirm the number and the window Missed calls belong to a specific Quo number. Before pulling anything, establish which number (from `list-inboxes`, if the user has not named one) and what period matters: today, since yesterday, or the last few days. If the user does not say, default to the last 24 hours and state that assumption in your output. Call transcripts only exist on numbers where transcripts are enabled, so if voicemails come back without transcripts, say so rather than inferring what the caller wanted. ## 2. Pull the missed calls and their transcripts Use `fetch-call-transcripts` for the chosen number and window. Keep only calls that were not answered. Voicemail transcripts are the richest signal, so read them first: they tell you whether the caller wants something, how urgent it sounds, and whether they already said they would call again. If the list is long, work in the time window the user asked for and say how many calls you left out. Do not try to triage 200 calls at once; take the most recent or the most relevant and offer to continue. ## 3. Triage by urgency, not by time Sort each caller into one of three bands using what the transcript or the call context actually says: | Band | Signal | Action | |---|---|---| | **Respond now** | Stated urgency, a problem with an existing job or order, a deadline, a repeat call from the same number | Draft a reply first | | **Respond today** | A clear question or request, a new enquiry, a booking | Draft a reply | | **Low / no reply needed** | Wrong number, spam or robocall pattern, silence, "just checking in" with nothing to answer, already resolved | Mention briefly, no draft | A caller who rang three times in an hour is a stronger signal than one who rang once at lunch, even if the single call sounded more polite. Repeat attempts usually mean the matter is pressing. ## 4. Match each caller to a contact For every caller who needs a reply, use `get-contact` or `list-contacts` to find out whether the number is already a contact and what their name and context are. A known contact changes the tone of the draft and tells you the history. An unknown number is a new enquiry: say so, and do not invent a name. If several contacts could match, list the candidates and ask the user which one is right rather than picking. Do not create or update contacts as part of this job. If a caller is unknown and the user wants them saved, that is a separate step that needs approval, handled with `create-contact`. ## 5. Draft the follow-up texts For each caller in the first two bands, write one short draft: - Open with the caller's name if known, otherwise a neutral greeting. Do not guess a name from the voicemail. - Address the specific thing they asked about, in the first sentence. - Give one concrete next step (a time you will call, a question to answer, a link or attachment the user must supply themselves). - Keep it under about 300 characters where possible, so it reads as a text, not an email. - Never promise a price, a date or a commitment the user has not stated. Use placeholders such as [time] and mark them clearly. Drafts are not sent. Show them to the user and wait for the user's explicit yes before using `send-message`, and then send only the drafts the user approved, one recipient at a time, with any edits they asked for. ## Common patterns and traps - **Transcript is garbled or cut off.** Say the transcript is unclear and quote only what is readable. Do not fill gaps with a guess about what they wanted. - **The caller is the user's own team member or a known vendor.** Flag it as internal or vendor traffic and suggest handling it outside the customer queue. - **Voicemail says "call me back" with no detail.** This is still a reply, but the draft should ask what they need rather than assume. - **Same person, several numbers.** Group them under one contact so the user is not sent three texts. - **Missed call that was answered by another team member.** Check whether a later call from the same number was picked up before drafting, otherwise you will chase a resolved call. - **Silence or a hang-up with no voicemail.** Do not draft a reply. Mention it as a low-signal call only if the user asked for every call. - **Quiet hours and credits.** Texts consume pre-paid API message credits. If the user is short of credits, say so before drafting a long batch, and keep the batch small. - **Transcripts absent because transcription is off.** You can still list the missed calls and their times, but you cannot say what the caller wanted. Make that gap explicit. ## Output ``` Number: | Window: Missed calls found: , reviewed: , left out: and why Respond now 1. |