Atlas voice
An AI voice agent that knows the account before it says hello.
Every call Atlas places or answers starts from the customer's full record: what is open, what was promised, what was said last time and how they pay. The conversation is spoken; the decisions behind it come from your rules and your data. When a call needs a person, it goes to one.
Outbound
Each call script is filled in from the account, right before the call.
Your agents carry call scripts with placeholders. Atlas fills them from the account's live record the moment a call is placed, so nothing on the call is stale.
- 01
Context
The balance, the open invoices, the oldest one, any promise on file, the last contact, the history so far and the AI Credit Rating are read from the account.
- 02
Opening
The agent says who it is calling for, that it is an AI assistant, and asks for the right person before sharing anything.
- 03
Verify
The customer is verified on the call before any invoice number, amount, date or status is disclosed.
- 04
Outcome
A payment date, a promise, a plan within your terms, a dispute or a hand-off is recorded on the account, and the account moves to the agent that owns what comes next.
Inbound
When a customer calls in, the account comes with them.
Atlas identifies the caller from the number, pulls in the account and its agent's context, and routes the call as it unfolds. One call can carry several things: a balance question, a new payment date, a disputed invoice and a request for someone in finance.
- Caller identified
- Matched to a contact and a customer from the calling number, then verified before any detail is shared.
- Context layered in
- Open invoices, promises, disputes, history and the company's own rules, assembled for this caller.
- Routed by intent
- A promise goes to Promise to pay, a dispute to Dispute & deductions, a request for a person to the right teammate.
- Actions recorded
- Every outcome lands on the account and in its timeline, with who said what.
- Caller identifiedNumber matched to the account and contact
- VerifiedNo invoice detail until the customer is verified
- Context loadedBalance, invoices, promises, disputes, rating, history
- A date to payPromise to pay confirms it in writing
- Pay nowA secure payment link by text
- Something is wrongDispute & deductions opens it with the evidence
- Wants a personHanded to your team with a summary
Rules on every call
Rules that are not settings.
These hold on every call, inbound or outbound, whatever an agent's own configuration says.
- AI identified
- Every call says it comes from an AI assistant, at the start.
- Recording
- Calls are recorded only where the customer has consented. In two-party consent states the call asks first.
- Hours
- Calls go out only between 8am and 9pm in the customer's own time zone.
- Consent
- A call goes only to a number with consent on file. Asking not to be called ends that channel at once.
- One touch a day
- At most one touch per customer per day, across every agent and channel.
- Hand-off
- If the customer asks for a person, mentions legal action or disputes the debt, the agent stops and hands off.
Outbound
When Atlas calls out, the context is loaded before it dials.
An outbound call starts from the agent's sequence. Before the number is dialed, Atlas has the account's invoices, payment history, email thread, promises, consent and the customer's local time in front of it, so the call can follow wherever the customer takes it.
Prepared
The account, its open invoices and the last conversation are assembled before the call, and the call goes out only inside 8am to 9pm local time with consent on file.
Routed as it unfolds
Stay with the agent, bring in a payment plan or a dispute, or transfer to a person, decided from what the customer says and your rules.
Several outcomes, one call
A disputed invoice and a promise for the rest are both recorded, each with the agent that owns it.
What runs without anyone
Atlas does the work. You decide what waits.
The voice agent places and answers calls on its own, inside the rules above. Your review flags decide which outcomes 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
- Places scheduled calls in the agent's sequence
- Answers inbound calls and identifies the caller
- Verifies the customer before disclosing details
- Records promises and payment dates on the account
- Routes the account to the agent that owns what comes next
Waits for a person
- A customer who asks for a person
- Any mention of legal action, or a disputed debt
- Payment plans over your review threshold ($25,000 by default)
FAQ
AI voice agent, run end to end.
Can Atlas call customers about overdue invoices on its own?
Yes. Calls are steps in an agent's sequence, such as Collections calling the AP lead at 15 days past due. Atlas fills the call script from the account's live record, places the call inside contact hours, verifies the customer, and records the outcome. You choose which outcomes wait for review.
What does Atlas know when a customer calls in?
Atlas identifies the caller from the number and pulls in the account: open invoices, the oldest balance, promises on file, disputes, past conversations and your own rules for that agent. Nothing about an invoice is shared until the caller is verified.
Can one call handle more than one thing?
Yes. A caller can ask about a balance, commit to a new date and dispute a different invoice on the same call. Atlas records each one and routes it: the promise to Promise to pay, the dispute to Dispute & deductions, and a request for a person to the right teammate.
What rules does Atlas follow on every call?
Every call identifies itself as an AI assistant, records only with consent, asks first in two-party consent states, calls only between 8am and 9pm in the customer's time zone, and calls only numbers with consent on file. Asking not to be called ends the channel at once. These are rules in code, not settings.
When does the voice agent hand a call to a person?
When the customer asks for a person, mentions legal action or disputes the debt, the agent stops and hands off with the account and what was said attached. You can add your own hand-off rules per agent.
Does the voice agent follow our scripts?
Yes. Each agent carries your call script with placeholders for the company, customer, contact, balance, invoices, oldest invoice, promise, last contact, history and rating. Atlas fills them from the account before every call, and you edit the script on the agent's page.
Related in Atlas
- CollectionsEvery overdue balance worked by the right agent, by email, text and phone, until it is paid.View
- Promise to payPromises and payment plans captured, confirmed and held to the date.View
- Payment remindersReminders by email, text and voice, timed to each contact and written from the account's own record.View
- Disputes and deductionsDisputes and short payments answered with the evidence attached.View
- Atlas agentsEvery Atlas agent: what brings an account in, its sequence, its channels and what waits for a person.View
See the voice agent 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.