Custom agents
Agents built to the way your company collects.
Every company's credit policy, terms and escalation rules are different. In Atlas you build an agent by picking options, preview it on every channel, and activate it: the next matching account moves in from wherever it is.
- Name
- Promise to pay
- Comes in on
- Card declined · ACH return · Promise broken
- Channels
- SMS · Email · Voice
- Tone
- Direct
- Waits for a person
- A second broken promise
Ten questions
An agent is built by answering ten questions, not by writing a prompt.
Every choice is an option you can see, change and version. There is no chat and no code.
- 01 Template
- Start from one of Atlas's agents.
- 02 Name
- What your team and the audit trail call it.
- 03 Triggers
- The events that move an account in: a declined card, a returned ACH, a broken promise, a short payment, a falling rating.
- 04 Channels
- Email, SMS and voice, in the order you choose.
- 05 Tone
- Friendly, direct, firm or formal, in your company's own words.
- 06 Cadence
- How often it touches an account, at most, and from which day.
- 07 Contact hours
- Its own hours, always inside 8am–9pm in the customer's time zone.
- 08 Hand-off
- When it stops and passes the account to a person: asks for a person, mentions legal action, a second broken promise.
- 09 Review
- Which steps wait in the Approval Queue before they run.
- 10 Priority
- Which agent wins when two triggers fire at once.
From draft to live
Previewed on every channel before it touches an account.
- 01
Build
Answer the ten questions. Atlas generates the sequence from the cadence, one touch a day at most, and you edit any step.
- 02
Test drive
Preview the email, the text and the call it would send, on a real account's context, before Activate unlocks.
- 03
See who moves
Atlas lists every account that matches the triggers and that the new agent outranks, before you activate it.
- 04
Activate
Those accounts move in at once and start at the right step. Every later edit is a new version with a field-level history.
Built with you
Yours to build, or built for you at deployment.
Your own agents
A company builds and edits its own agents in Atlas. A custom agent lives only in that company's own database.
Built by Ferrata
Ferrata builds agents for a company at deployment, shaped to its credit policy, terms and escalation rules.
Built alongside your team
The AI Velocity POD, two forward-deployed engineers, keeps building agents with your people until your own team builds the next ones.
What runs without anyone
Atlas does the work. You decide what waits.
A custom agent runs on its own once it is active, inside the rules every agent follows. You decide which of its steps wait.
Atlas runs on its own. You flag any step for review, and flagged work waits in the Approval Queue for an Approver, Admin or Owner. Charge-off and legal waits for a person on every step.
On its own
- Sends, calls and texts on its sequence
- Moves accounts in and out on its triggers
- Hands off on the rules you set
Waits for a person
- Any step you flag for review
- Anything over the limits you give it
FAQ
Custom agents, run end to end.
How do we build a custom agent in Atlas?
In Atlas you answer ten questions: the template to start from, the agent's name, the triggers that bring an account in, the channels, the tone, the cadence, contact hours, when to hand off to a person, which steps wait for review, and its priority against the other agents. There is no chat and no code: every choice is an option you can see and change.
What happens when we activate a new Atlas agent?
Before Activate unlocks, a test drive previews the email, the text and the call the agent would send, and lists every account that would move into it. Once activated, the agent takes, at once, every account that matches its triggers and that it outranks, and starts each one at the right step of its sequence.
Can Ferrata build an agent for us instead?
Yes. Ferrata builds agents for a company at deployment, shaped to its own credit policy, terms and escalation rules, and the AI Velocity POD (two forward-deployed engineers) can keep building them with your team after that. A custom agent lives only in your company's own database.
Do custom Atlas agents follow the same rules as Atlas's own?
Yes. The rules no agent can change apply to every agent, custom ones included: calls and texts only between 8am and 9pm in the customer's local time, consent on file for each channel, STOP ends that channel at once, one touch per customer per day across every agent, an AI disclosure on every call and text, and customer verification before any invoice detail is shared.
Can a custom Atlas agent use a voice channel?
Yes. Choosing voice adds the call procedures that cannot be turned off: the AI identifies itself, asks for recording consent where the state requires it, confirms it is speaking to the right person before sharing any detail, and hands off when the customer asks for a person, disputes the debt or mentions legal action.
Related in Atlas
- Atlas agentsEvery Atlas agent: what brings an account in, its sequence, its channels and what waits for a person.View
- Modeling your operationsYour receivables operation, modeled as agents, rules and context you can see.View
- CollectionsEvery overdue balance worked by the right agent, by email, text and phone, until it is paid.View
- AI voice agentCalls out and answers calls in, with the whole account in front of it.View
See Atlas work on your own receivables.
Thirty minutes on your own aging report. You leave with a view of how Atlas would work it, and an honest answer if the sequencing is wrong and you should fix something else first.
Your credit policy, terms, tone and escalation rules are your advantage, and they stay yours. Atlas is configured to the way you run receivables. You are not handing over a playbook or fitting into a template.