How to call contacts in Attio: a record-to-outcome workflow
Published
Ryan Erkal
Founder, Redialler
To call a contact in Attio, open or identify the correct Person, confirm a usable phone number and calling permission, place the call through your approved phone tool, then save the outcome against that same record. Treat the voice connection, CRM activity, recording and callback task as separate checks. This prevents a call that happened from being mistaken for a call that was logged.
1. Confirm the right Person and phone field
Start with the exact Attio Person record. A name search is useful for finding candidates, but it is weak proof when two people share a name. Compare the company, email, record URL or record ID, and the phone value you intend to dial. If the number appears on more than one Person, pause and resolve the duplicate before making a call.
Attio documents phone numbers as a writable phone-number multiselect on People. A value can have a displayed format and a normalised value, so agree on one comparison format before deduplication. For US calling, Redialler accepts ten digits or an eleven-digit value beginning with 1 and uses the resulting +1 form as the E.164 number. It currently supports US numbers only.
Check the country as part of identity. A valid-looking local number can belong to another country, and an area code does not prove where a person is now. If the record has several numbers, record which one was selected in your call note. That small detail makes later review much easier.
2. Check calling prerequisites
Before you dial, confirm that the calling workspace is connected, the selected caller ID is permitted for the workspace, and the browser has microphone access. Also check that the destination is eligible for your policy. Redialler's current outbound path is a browser call through Twilio and is limited to US numbers. Customer provider installation and some live call paths still need separate acceptance, so do not treat a configured screen as proof that a live call will work.
Calling time and suppression are separate gates. A calling tool can show local-time context, but you still need a process for the call type and jurisdiction. The FTC says covered telemarketing calls to a person's home should not be made outside 8 a.m. to 9 p.m. local time without prior consent, and entity-specific do-not-call requests must be honoured. State and FCC rules can add requirements.
If your next step is a list, run these checks on one record first. A queue can preserve CRM context, but it cannot repair a wrong record, a stale opt-out or an unverified timezone. The section links include a guide to the broader trade-offs of one-at-a-time and first-answer-wins calling.
3. Make one call and record the outcome
Place the call only after the record and number checks pass. Keep three questions separate: did the provider call complete, did a person answer, and did the CRM receive an activity? A provider status is a transport result. A disposition is your business interpretation. A note or activity is the durable record of what you want the team to remember.
After the call ends, save one outcome and enough context to explain it. Redialler requires the call to be ended before its outcome is saved, and a Callback outcome requires a callback date. Use a short note that says what happened, what was agreed, and what should happen next. Do not label an unanswered call as connected because the dial attempt exists.
A useful hypothetical example is a rep who reaches no one at an existing Person record. The rep selects No answer, adds “No answer; try the main line next time”, and sets a callback date only if the contact actually requested one. The wording is illustrative. It is not a claim about a measured response rate.
4. Find the note and next action
Return to the same Person record and verify the activity or note is attached to it. Attio's note API uses a parent object and parent record, so the record identity matters more than a contact name typed into a search box. Read the title, timestamp, selected number and outcome together. If they disagree, stop before creating another entry.
A callback is a task with a due date and an owner. Attio's task model supports plaintext content, a deadline, an explicit open or completed state, assignees and linked records. A task is a piece of owned work. It is not proof that a new call will start automatically at the due time. If your workspace has no valid assignee, record that gap rather than inventing ownership.
Recordings and transcripts may follow a different path. In Redialler, a recording callback starts durable background processing. The recording can be downloaded, transcribed and attached after the outcome writeback. Check the recording permission and sign-in boundary before sharing a link, and never paste private audio URLs into a public note.
5. Resolve a missing activity safely
If the call happened but the note is missing, first check whether you are looking at the same workspace and exact Person record. Then separate an activity writeback problem from delayed recording work. In Redialler, saving an outcome commits local call state and queues Attio work. Recording and transcript processing can still be running after the outcome is visible.
Look for the call ID, CRM record ID, sync job state and last error. A queued or retrying job calls for observation or a safe retry after its next run time. A blocked job usually needs a credential, permission or field-mapping correction first. Do not create a second note from memory while the original write is uncertain. Stable operation markers allow a retry to find an existing write instead of blindly duplicating it.
Attio documents 429 responses with a Retry-After header. A rate-limited request was not processed and can be retried after the stated reset, but an unknown create response is a different case. Check the record or operation marker before sending a new create request.
6. Run a one-contact acceptance check
Before importing a list, use one controlled Person and write down the expected result. Confirm the selected record and number, pass the calling eligibility checks, complete a short authorised call, save a known outcome, and verify the note or task against the same record. If you expect a recording, verify its permission and wait for the processing state to settle before judging the result.
Use a simple stop checklist: the record identity is unique; the number is a valid US E.164 value; the caller ID is active; the browser can use the microphone; the call has a provider ID; the outcome is saved once; and the CRM entry is linked to the expected record. For a callback, check the exact local date, timezone and owner. For No answer, check that no callback task was created by assumption.
This workflow keeps Attio as the durable CRM while the calling tool handles the voice session. If your record-to-call path has an unusual ownership, field or permission rule, discuss it before moving from one record to a list.
Explore Redialler
Sources and review
Reviewed 2026-09-08. Product details and provider policies can change.
- People (checked 2026-09-08)
- Querying Attio data (checked 2026-09-08)
- List person records (checked 2026-09-08)
- Create a task (checked 2026-09-08)
- Create a note (checked 2026-09-08)
- Handling rate limits (checked 2026-09-08)
- Complying with the Telemarketing Sales Rule (checked 2026-09-08)