Attio callback workflow: turn requests into owned work

A callback task is an item of work: someone must call, email or otherwise follow up by a stated deadline. A list status is a label about where the record sits. A scheduled automatic call is a provider action that starts at a configured time. They can be related, but they are not interchangeable.

Use the call outcome to record what happened, the list entry to show the campaign state, and the task to show ownership and due work. Do not infer that a stage called Callback will ring the person. Do not mark a task complete just because a call was attempted. Close it when the agreed work is done, or reschedule it with a reason.

This separation also keeps reporting honest. A team can count callback requests, open callback tasks and completed calls as different measures. A single combined field cannot answer all three questions.

Attio task creation reference

Close workflow call tasks

Only create a callback when the conversation gives you a clear request or your team's policy permits a defined follow-up. Capture the agreed date, local time, named timezone, contact, reason and owner. If the person says “next week” without a day, ask a clarifying question or create an unscheduled review task rather than inventing a deadline.

Store an unambiguous instant for the due date, while preserving the person's local wording in the task content. Use an IANA timezone such as America/New_York or Europe/London. A fixed offset can be wrong after a daylight-saving change, so do not write “UTC minus 5” as if it were a permanent New York rule.

Ownership must be explicit. Attio's task API supports assignees and a linked record. If the agreed rep is away, reassign the task to a named cover or record an unassigned review for a manager. An owner field on the Person is not automatically the owner of this callback.

Attio task fields and assignees

Resolve the exact Person before creating the task. Check the record ID, company, email and selected phone. If a call came from an Attio list, also keep the list ID and entry ID so the campaign context remains visible. A name-only search can return a plausible but incorrect contact.

Attio's task payload includes linked_records, and its note model also uses a parent object and parent record. Link the callback to the Person record that was discussed. Put the reason and the next step in plaintext content, then include the exact due date and timezone in a form another rep can read without guessing.

In Redialler, a Callback outcome is saved against the call and a follow-up task is created only when a callback date is set. The task is queued for Attio writeback after the local call state is committed. Treat the visible queued state as evidence of pending work, then verify the Attio task on the record.

Attio task creation reference

Calling with Attio

A callback task should not be hidden inside a general pending list. Give it one owner, one due instant and one source record. If the contact is also in a power or parallel queue, mark the queue context so another rep does not start a competing attempt before the callback owner has acted.

A London rep might agree to call a New York prospect on 12 November 2026 at 10:00 America/New_York = 15:00 UTC = 15:00 Europe/London. The task should preserve that timezone and can show the equivalent London time as a convenience. The important value is the named local agreement, not a guessed fixed offset. Assign the task to the London rep or a named cover. Nothing in this example schedules an automatic call.

If an owner leaves, use a small handoff rule: the team lead reviews open callbacks, assigns each to a named replacement, and keeps the original owner and handoff reason in the note. Do not silently move a callback into a shared queue where two people can claim it.

Attio callback task model

Attio callback outcome mapping

When the callback is completed, close the task and save the resulting outcome against the same record. If the person asks for another date, update the existing task or create one replacement according to your team's policy, and state why the date changed. Avoid leaving an old open task beside a new one that describes the same commitment.

If the person does not answer, record No answer and decide whether the original promise still stands. A missed attempt is not the same as a completed callback. If the request has expired or the number is wrong, close the task with that reason and route the record to the right correction or suppression process.

Attio documents that a rate-limited request returns 429 with Retry-After and was not processed. A normal retry can wait for that reset. An uncertain task create needs a record and marker check first, because a network timeout does not prove that no task exists.

Attio task creation reference

Attio rate-limit guidance

Use one controlled Person to test the complete state path. Create an open callback with a future due date, confirm the owner and linked record, then use an isolated test clock or test fixture to check that the task appears as due; never change a production system clock. Complete it and verify the outcome and note remain on the same record.

Then repeat the same write with the same call or operation ID. The expected result is one task, not two. If the task is already open, update or reuse it according to your marker rule. If two tasks have the same marker, stop and have an admin reconcile them before another retry. Keep the call ID, task ID and record ID in the diagnostic record.

For a wider workflow, pair this guide with the linked guide about Attio call outcome mapping. If your team needs to review callback ownership, discuss the workflow with the relevant owner.

Attio call outcome mapping

Discuss your calling workflow

• attio

Reviewed 2026-09-08. Product details and provider policies can change.

• Create a task (checked 2026-09-08)
• Create a note (checked 2026-09-08)
• List person records (checked 2026-09-08)
• Handling rate limits (checked 2026-09-08)
• Workflow Steps (checked 2026-09-08)
• Track Your Work with Activities and Calendar (checked 2026-09-08)