# Connect every Weave call to its patient and its next step > Calls answered in Weave link to the right patient and end as owned Tasks, not loose notes, whenever the call creates work. Markdown view of https://www.tabflows.com/university/playbooks/weave-phone-answering — the HTML page is canonical. [](https://www.tabflows.com/university/playbooks) 1. [Playbooks](https://www.tabflows.com/university/playbooks) 2. [Messages & Calls](https://www.tabflows.com/university/playbooks#messages-and-calls) Calls answered in Weave link to the right patient and end as owned Tasks, not loose notes, whenever the call creates work. - Weave Last checked Oct 27, 2026 against Tabflows v3.10.63 ## The situation Weave makes calls, texts and reminders easier to manage, but the caller's context usually lives somewhere else: the chart, the calendar, the billing system, the task list, a lab portal or a past message. The person on the phone has to find the right patient, understand why they called, check the right system and decide what happens next. So a call is answered in Weave, then someone opens the chart, checks the calendar, digs up a prior message, makes a task somewhere else and tries to remember whether the patient still needs a callback. None of it is dramatic. It is slow, repeated and easy to lose when the day is full. ## Steps 1. **Keep Weave one click away** Open Weave in Tabflows so the signed-in product sits in your Tabflows sidebar. Weave still hosts the calls and messages. 2. **Link the caller to the patient once** Link the patient's Weave text conversation to the patient with the link button in the Tabflows sidebar, so it shows Profiles linked for the whole clinic. After that, anyone on the team can reopen that conversation, and the patient's other linked systems, with one click each instead of searching again. 3. **Check what is already open** Before you create anything, filter Tasks by Patient to see the open work and its comments. That tells you whether the patient still needs a callback or someone already has it. 4. **Give the call's work a home** If the call creates work, make it a Task linked to the patient, with an owner in Assigned to and a Due on date. A callback goes to whoever will make it, a refill question goes to whoever reviews refills, a form or billing question goes to the group that handles it, such as Billing, and a scheduling request goes to whoever books visits. For a lab question, the Task should say whether a result exists, whether it has been reviewed and who owns the follow-up. 5. **Close it when the patient work is done, not when the call ends** Record what happened in Comments, set the status to Waiting while you wait on someone, and set Done only when the outcome is finished and no follow-up remains. A call whose work truly ended on the phone needs no Task. ## The outcome The call is the trigger, and the patient work is what has to move. Every call that creates work gets a Task with an owner, a due date, a status and a next step, so nobody rebuilds the patient story from memory, whether the call was taken in the office, by a virtual receptionist or by an answering service. ## Ask Sidekick Sidekick is the AI assistant inside Tabflows. Hey Tabflows, when I tell you a Weave call needs follow-up, create a task linked to the patient with an owner and a due date, and list that patient's open tasks across the clinic so I can see what is already in motion. ## In the Product Library - [Using Weave with Tabflows](https://www.tabflows.com/university/library/integrations/using-weave-with-tabflows) - [How do I link a patient across your systems](https://www.tabflows.com/university/library/magic-buttons/how-do-i-link-a-patient-across-your-systems) - [Using Tasks for reviewing patient task history](https://www.tabflows.com/university/library/tasks/using-tasks-for-reviewing-patient-task-history) - [How to update, complete, reopen, or delete tasks](https://www.tabflows.com/university/library/tasks/how-to-update-complete-reopen-or-delete-tasks) [Read the full guide](https://www.tabflows.com/blog/weave-phone-answering-workflow) ## Related markdown Section index: [Playbooks](https://www.tabflows.com/university/playbooks.md) Alongside this page: - [Advance directive tracking](https://www.tabflows.com/university/playbooks/advance-directive-tracking.md) - [After hours answering service](https://www.tabflows.com/university/playbooks/after-hours-answering-service.md) - [After hours message triage](https://www.tabflows.com/university/playbooks/after-hours-message-triage.md) - [Billing decline follow up](https://www.tabflows.com/university/playbooks/billing-decline-follow-up.md) - [Call follow up loop](https://www.tabflows.com/university/playbooks/call-follow-up-loop.md) - [Chronic care check ins](https://www.tabflows.com/university/playbooks/chronic-care-check-ins.md) - [Clia and compliance renewals](https://www.tabflows.com/university/playbooks/clia-and-compliance-renewals.md) - [Dea and license renewals](https://www.tabflows.com/university/playbooks/dea-and-license-renewals.md) Start here: - [Tabflows](https://www.tabflows.com/index.md) - [Tabflows pricing](https://www.tabflows.com/pricing.md) - [Tabflows FAQ](https://www.tabflows.com/faqs.md) - [About Tabflows](https://www.tabflows.com/about.md) - [Contact Tabflows](https://www.tabflows.com/contact.md) - [DPC workflow software](https://www.tabflows.com/dpc-workflow-software.md) - [Directory](https://www.tabflows.com/directory.md) - [Workflows](https://www.tabflows.com/workflows.md) - [DPC finder](https://www.tabflows.com/dpc-finder.md) Every page listed in sitemap.xml has a markdown twin at the same URL with `.md` appended, or by sending `Accept: text/markdown` to the canonical URL. Wider index: [llms.txt](https://www.tabflows.com/llms.txt), [llms-full.txt](https://www.tabflows.com/llms-full.txt), [sitemap.md](https://www.tabflows.com/sitemap.md), [sitemap.xml](https://www.tabflows.com/sitemap.xml). Support documentation: https://www.tabflows.com/university/library — append `.md` to any article URL for its raw markdown.