Free tools and guides
Attio cold calling setup guide and checklist
Set up Attio lists, phone fields, call outcomes, recording disclosures, and follow-up workflows. Save your free checklist in your browser.
Last reviewed: . Free to use. No signup required.
Choose your CRM and calling workflow
Still choosing your CRM? Read the Attio vs HubSpot outbound comparison, then use the dialer picker to compare calling modes.
For recording-enabled calls, review the call recording, transcription, and CRM workflow before testing post-call processing.
Your Attio calling setup checklist
Keep Attio as the shared CRM record. Use your dialer to run calls and queues. Work through these checks before your first campaign.
0 of 8 steps complete
Progress is saved in this browser. It does not connect to Attio or change your workspace.
Use an explicit country code. Resolve duplicate or shared numbers before importing your calling list.
Choose one campaign and one owner. Add a small test group before importing the full list.
Separate shared People fields from list-specific stages. Confirm field types and the exact options your dialer will write.
Check the connected workspace and test record. Keep API tokens on the server and out of browser code.
Check list access, record access, outcome writes, and who owns follow-up tasks.
Review participant locations, disclosures, consent, calling hours, suppression, retention, and access to recordings.
Use a willing colleague. Check the record match, saved outcome, note, playback access, and callback task.
Choose either the dialer or an Attio workflow to create the task. Test retries and check that no duplicate task appears.
1. Build a small calling list
Create a People list for one campaign. Start with a few contacts you can verify. Include a usable phone number, a clear owner, and enough company context for the rep.
Attio lists organize records around a process. They can have their own attributes and filtered views. A list does not create a separate person for each campaign. Source: Attio, Create lists.
Before a full import, normalize your phone column. Check duplicates and shared office numbers. A valid phone format does not establish permission to call.
2. Choose shared fields and campaign fields
People attributes hold shared person data. List attributes hold data for a particular process. Use this distinction to keep one campaign from overwriting another. Source: Attio, Create and manage attributes.
| Example field | Location | Type to check | Setup check |
|---|---|---|---|
| phone_numbers | People | Phone number | Keep the country code. Check which value your dialer selects when a person has several numbers. |
| outreach_status | People | Text, select, or status | Use a shared outcome field only if it exists and is writable. Check mapped option values. |
| call_outcome | Campaign list | Text or select | Keep campaign results on the source list entry. Match exact outcome options. |
| lead_stage | Campaign list | Text or status | Describe the campaign step, such as ready to call or follow-up. Keep stage and call outcome separate. |
| next_follow_up_at | Campaign list | Timestamp | Store a specific callback time. Decide who owns the related task. |
| qualified | Campaign list | Checkbox | Use an agreed qualification rule. Do not infer qualification from a connection alone. |
With Redialler, outcome writes depend on the workspace schema, field mappings, connection path, and sync settings. The installed integration can also write source list-entry values. Check the configured mapping before relying on any example slug.
3. Test connection, access, and call logging
Connect the intended workspace. Use a rep account to check access to the actual list and records. Confirm the owner mapping for follow-up tasks. An admin's successful test does not prove a rep has the same access.
Place a controlled call to a willing colleague. Save an outcome and a short note. Check the right Attio record, the correct campaign entry, and any callback task. Then save an update and check that the note and task do not multiply.
Attio notes attach written context to records. Redialler's call notes can include rep notes, transcripts, and a protected recording link when those sync options are enabled. Source: Attio, Notes. See Redialler's Attio integration for the calling workflow.
4. Review recording before the campaign
Choose a recording policy with qualified counsel. Review the caller's location, each recipient's location, additional participants, recording access, and retention. A phone area code alone does not establish a person's current location.
Sample disclosure for review: “Hi, this is [name] from [company]. I would like to record this call for [purpose]. Is that OK with you?” Use an approved process to obtain consent before recording. If someone declines, follow your approved process to continue without recording or end the call.
This is not legal advice. Read the state recording-law reference and the TCPA and Do Not Call checklist. The checklist does not enforce either policy.
Attio's own recording guide covers its meeting recorder, including admitting and removing it. Keep that workflow separate from phone recording in your dialer. Source: Attio, Recording calls with Attio.
5. Start with one follow-up workflow
Example to configure and test: when a campaign entry moves to your callback stage, check that it has an owner and callback time, then create a task. Choose one system to create that task. Disable duplicate task creation in the other system.
Attio workflows use triggers, conditions, and actions such as updating a record or creating a task. Runs consume workspace credits. Review your plan's limits and inspect the first test runs. Source: Attio, Overview of workflows.
Redialler supports outcome-based follow-up tasks and configurable sync settings. Confirm the connection path and enabled options in your workspace. Test a changed callback time and a completed task before increasing campaign size.
Frequently asked questions
Does this checklist change my Attio workspace?
No. It saves completed steps in your browser only. You make the changes in Attio and your dialer. No Attio account is needed to use the checklist.
Should call outcomes be People fields or list fields?
Use a People field for a status that should follow the person across campaigns. Use a list field for a stage or outcome that belongs to one campaign. Match your dialer's configured field types and options.
Does Attio Call Intelligence place outbound phone calls?
The cited Attio Call Intelligence guide describes a recorder that joins meetings. For this phone-calling setup, use an outbound calling integration and test how it writes activity back to Attio.
Will a recording notice make every call lawful?
No. A sample notice is a starting point for review. Your policy must account for each participant's location, consent requirements, and the calling method. Use the recording-law reference and get qualified legal advice.
Keep your calling work in Attio.
Set up your calling workspace in minutes. Questions about your CRM or team? Talk to us before you start.