Agents You Can Run in Alti

Hand a whole job to a specialist. Alti's agents work your overdue book, recover failed payments, and dig into integration problems, one approved step at a time.

---

Most of the time you ask Alti a question and it answers. An agent is different. An agent takes on a multi-step job and walks you through it from start to finish, stopping for your approval before anything is sent or changed.

Think of it as the difference between asking a teammate "who owes me money?" and asking them "go collect it."

Bringing in an agent

Type @ in the Alti message box and pick the agent you want. It appears as a chip on your message, and Alti hands the job over.

One agent works differently. The Integration Agent is not in the @ menu. Alti brings it in automatically when your question sounds like a sync or import problem, so you just describe what went wrong.

New to an agent? Ask it what it does before you start. Every agent opens by laying out its plan, so you can see the whole flow before the first step runs.

The agents available today

Agent	What it does	How you start it	Who can run it
Collections Agent	Works your overdue book end to end: segment, email, enroll chronic late payers in Auto-Pay, then escalate	@ menu	Administrators and Sub-Admins
Failed Payment Recovery Agent	Finds customers whose payments failed, stops re-charging a broken card, and asks them to update their details	@ menu	Administrators and Sub-Admins
Integration Agent	Diagnoses why an invoice, customer, or payment did not come through from your accounting or PSA system	Just describe the problem	Everyone

---

Collections Agent

Bring it in with @ and pick Collections Agent, or say something like "collect on my overdue invoices."

The agent runs your collections in four stages, and you decide how far to go:

1

Identify

It groups every overdue account into standard aging buckets (0 to 30, 31 to 60, 61 to 90, 91 to 120, and 121 to 365 days), then shows you the count and dollar exposure in each, plus your largest overdue customers. Nothing has been sent at this point. You can narrow to specific buckets, a minimum days-overdue threshold, or individual customers before going further. It can also build a get-ahead list of invoices due soon.

2

Outreach

It drafts the email and shows you the exact subject and wording before anything goes out. You review, edit, and approve each wave. After a wave sends, the agent checks real per-recipient delivery and names anyone it failed to reach, so you can resend to just those.

3

Auto-Pay enrollment

It identifies your chronic late payers, by default customers with at least three invoices paid late in the last 90 days who are currently overdue, and offers to enroll them in Auto-Pay. It tells you which customers it skipped and why, such as no valid payment method on file.

4

Escalate

It surfaces who never responded and whose email bounced, so you can decide what happens next. This stage is read-only. It does not open tickets or send anything.

Nothing sends unattended. Every email wave and every Auto-Pay enrollment stops on a confirmation card first. You approve each one.

Failed Payment Recovery Agent

Bring it in with @ and pick Failed Payment Recovery Agent, or say "recover my failed payments."

Also a four-stage flow:

1

Identify

It finds every customer with a recent failed payment and groups them by why it failed: card declined, insufficient funds, expired card, ACH return, or chargeback.

2

Stop the bleeding

It excludes affected customers from Auto-Pay so the platform stops re-charging a card it already knows is bad.

3

Ask them to fix it

On your approval, it emails those customers asking them to update their payment information.

4

Re-enable

On a later run it surfaces customers you previously excluded whose payments are working again, so you can put them back on Auto-Pay.

Why pausing matters. Repeated declines on a dead card cost you fees and can hurt your standing with the card networks. Pausing first, then asking the customer to update, is the cheaper order of operations.

Integration Agent

You do not pick this one. Just describe the problem and Alti brings it in when your question sounds like a sync or import issue.

It explains what happened to records coming from your connected accounting and PSA systems, including ConnectWise, Autotask, QuickBooks, Xero, and NetSuite. Typical questions:

• "Why wasn't invoice INV-2048 imported from QuickBooks?"
• "Why isn't this customer showing up?"
• "My sync job failed. What happened?"
• "Payments are stuck in Undeposited Funds and deposits aren't being created."
• "Is my ConnectWise invoice matched to its accounting copy?"

The Integration Agent explains, it does not fix. It is read-only. It will not re-trigger a sync, force a match, or retry a job. When the fix has to happen on our side, ask Alti to open a support ticket.

What stays true for every agent

• You approve every change. Agents follow the same confirmation-card pattern as the rest of Alti. See Taking Actions with Alti.
• Your access level still applies. An agent can never do something your dashboard role does not already allow. See Access Levels and What Each Role Can Do.
• You set the pace. Keep a confirmation at every step, or move faster once you have seen the agent's work and trust it.
• You can stop at any stage. The Collections and Failed Payment Recovery agents are built to be useful even if you only run the first stage and read the results.

Want a recurring report instead of a job you drive? See Routine Reports. Want to repeat a job you did yourself in chat? Save it as a Routine Workflow.

Love our platform? Rate us on Channel Program and check out our Referral Program page!