> ## Documentation Index > Fetch the complete documentation index at: https://vida.io/docs/llms.txt > Use this file to discover all available pages before exploring further. # Tasks and Outbound Automation > Schedule calls, texts, emails, Computer work, and repeating automation while keeping outcomes and retries visible. Vida Tasks turn a defined piece of work into something your team can schedule, monitor, retry, and review. Use them for outbound communication, one-time Computer Agent assignments, and recurring operational work. ## Choose the right work type | Work | Use it for | | ----------------------------- | -------------------------------------------------------------------- | | Outbound call, text, or email | One communication attempt or one retry-managed communication goal. | | Computer Task | One bounded assignment for a Computer Agent now or at a future time. | | Repeating Task | Computer Agent work on a predictable recurring schedule. | | One-off scheduled Task | Computer Agent work once at a specified time. | Availability depends on the selected Agent and account capabilities. ## Create one Task for one goal Give the Task enough context to act without guessing: * the intended recipient or source record * the outcome you need * the information the Agent may use * timing and timezone * completion criteria * escalation and approval boundaries * a stable external reference when another system owns the workflow For retry-enabled communication, one Task represents the complete goal and all attempts toward it. Do not create a separate Task for each retry. ## Use retries intentionally Define which unresolved outcomes should retry, the delay between attempts, business-hour rules, and the maximum number of attempts. A retry should have a realistic chance of producing a different result. Review the Task's attempt history to see each outcome, evaluation, experiment assignment, and linked conversation. Cancel the Task when the goal is no longer valid. ## Schedule Computer Agent work safely For repeating work, write instructions that define the source, time window, qualification rules, maximum work per run, deduplication behavior, and proof of completion. Create the Task paused when possible, run one controlled test, inspect its linked chat and destination effects, then activate the schedule. A heartbeat is better when the Agent should periodically look for material developments and remain quiet otherwise. See [Design useful heartbeats](/docs/computer-agents/heartbeats). ## Use batches for prepared lists CSV uploads are useful when you have a reviewed list of eligible recipients. Validate phone numbers, email addresses, required fields, consent, and duplicates before starting the batch. Save the batch reference and review both accepted and rejected rows. Do not re-upload an uncertain batch without checking whether earlier rows were already created. ## Review results The Tasks screen can filter by status and outcome and open the details for one Task. Depending on the Task, review: * current and terminal status * scheduled, last-run, and next-run timing * attempt or run history * structured result and error details * the linked log or conversation * the actual effect in the destination system A queued, accepted, or started Task is not proof of completion. ## Optional outbound number pools Vida can enable a managed pool of assigned numbers for approved high-volume call or text workflows. This is not a self-service pool-management feature. Contact Vida to review the use case, then test representative Tasks before increasing volume. Building automation through the API? See [Tasks and automation](/docs/api-reference/platform-guides/tasks-and-automation).