Skip to main content
Questions are the safe half. This page covers the other half: letting your agent change things in AI Sync.
Your agent acts as you. It has your permissions and its changes are real. A request to “clean up the old lists” can delete lists. Be specific, and ask it to confirm before anything destructive.

​
🚦 What to let an agent do

✅ Safe to delegate

Creating lists, tagging contacts, drafting SMS templates, building agents, searching numbers, pulling reports.

⚠️ Confirm first

Deleting anything, bulk contact edits, buying numbers, starting a live campaign, changing dispositions your pipeline depends on.

​
🛠️ Things worth asking for

  • “Create a power list called Q4 Solar Follow-up.”
  • “Tag every contact dispositioned Interested in the last 30 days as hot.”
  • “How many contacts in this list have no phone number?”
Ask for a count before a bulk change: “How many contacts would that affect?” A number you did not expect is your signal to stop.
  • “Search for numbers in the 312 area code.”
  • “Which of my numbers are flagged for spam?”
  • “List every number and what it is used for.”
See Caller ID and numbers for how many you need.
  • “List my dispositions and the pipeline stage each maps to.”
  • “Which dispositions have no pipeline stage?”
Dispositions drive your pipeline and your reporting. Have your agent show you the current mapping before changing any of it. See Dispositions and pipeline.
  • “Create a voice campaign for the Q4 Solar Follow-up list.”
  • “What’s the status of my running campaigns?”
  • “Pause the campaign called Aged Leads.”
Creating a campaign never starts calls. Going live is always separate — see Predictive pacing.
  • “Export last week’s call report as CSV.”
  • “Summarise yesterday’s calls by disposition.”

​
✍️ How to phrase a change

1

Name the exact thing

“The power list called Q4 Solar Follow-up” beats “the solar list”. Names are unambiguous; descriptions are not.
2

Say the scope out loud

“Contacts dispositioned Not Interested in the last 90 days” beats “the dead ones”.
3

Ask for a dry run

“Tell me what that would change before you do it.”
4

Then approve

“Yes, go ahead.” Now it acts, and you know what you approved.
The dry-run step costs one message and prevents the expensive mistakes. Use it for anything touching more than a handful of records.

​
🧯 If something goes wrong

Ask immediately: “What exactly did you just change? List every record.” Then check Activity logs, which record what happened regardless of what the agent reports.
Usually a naming mismatch. Ask it to list what it can see: “List all my power lists”, then use the exact name it returns.
Ask it to look the ID up in your account rather than guess. If it is not recognised, it is not in your account.
Check the window and scope first, then see Asking about your data.

​
➡️ Where to go next

Ask about your data

The read-only half, and how to trust an answer.

Connect MCP

Set up or reconnect the account link.

Connect the docs

Read-only access to these pages, safe for anyone.

Activity logs

What actually changed, independent of the agent.

Troubleshooting

When the product itself is misbehaving.