$18,640
Recovered this month
Verified Win
AUTOPILOT
AUTOMATE.
ACCELERATE.
AutoPilot is an autonomous revenue-recovery and cash-flow operating system powered by Echelon ID. It identifies eligible opportunities, advances approved actions, pauses where human judgment is required, and makes the resulting work and outcomes visible.
Actual live capabilities depend on connected providers, granted permissions, available integrations, data quality, merchant configuration, and applicable law.
Illustrative browser-only AutoPilot simulation. No message, lead, or merchant action leaves this page.
Step 1 of 9
AutoPilot is live
Systems Active means approved playbooks can run inside the merchant’s configured boundaries.
AutoPilot
Powered by Echelon ID
An Echelon Direct System
Live Systems Active
MerchantLocal demo
Welcome, Merchant.
$41,200
Moving through the pipeline
UP 24% vs last month
9appointments
27conversations
3Items need your review.
| Customer | Source | Outcome | Value | Verification |
|---|---|---|---|---|
| PowerDialer | Payment Plan Reinstated | $2,850 | Verified | |
| AI Messenger | Settlement Reached | $1,975 | Verified | |
| SMS Outreach | Past Due Paid | $1,450 | Verified |
ILLUSTRATIVE PRODUCT DETAIL
Recovered Revenue
Every record below reconciles to the approved $18,640 recovered total. Values are illustrative.
$18,640 verified across 9 outcomesOpen opportunity values are estimates, remain visibly separate from recovered revenue, and reconcile to $41,200.
$41,200 open across 6 opportunitiesMaya PatelApproval Ready
LAST ACTIONAutoPilot prepared a revised payment schedule
NEXT ACTIONApprove the proposed schedule
Carter WilsonConversation Active
LAST ACTIONEligibility and consent confirmed
NEXT ACTIONAnswer the customer’s timing question
Nina GomezOffer Reviewed
LAST ACTIONCustomer opened the approved proposal
NEXT ACTIONSend the scheduled follow-up
Owen BrooksAppointment Set
LAST ACTIONVirtual review confirmed for May 31
NEXT ACTIONComplete the human review
Grace KimNeeds Judgment
LAST ACTIONAutoPilot paused after a contract exception request
NEXT ACTIONSend the exception to the team
Isaac MooreIdentity Check
LAST ACTIONSensitive billing-change request detected
NEXT ACTIONVerify identity before resuming
Camila ReyesApproved Follow-up
LAST ACTIONMerchant approved the prepared follow-up in Needs You
NEXT ACTIONAutoPilot resumes the approved recovery sequence
The illustrative bookings below show the customer, appointment type, timing, location, source, and confirmation state.
9 scheduledOwen BrooksAccount Review
May 31 · 10:00 AMVirtual
ConfirmedAI Messenger
Sofia RamirezPayment Plan Review
May 31 · 1:30 PMVirtual
ConfirmedPowerDialer
Harper EvansService Rebooking
June 1 · 9:00 AMPhoenix
ConfirmedSMS Outreach
Leo MartinezRenewal Consultation
June 1 · 2:00 PMVirtual
ConfirmedEmail Follow-up
Amelia ClarkMembership Review
June 2 · 11:30 AMScottsdale
ConfirmedAI Messenger
Elijah YoungInvoice Resolution
June 2 · 3:00 PMVirtual
ConfirmedTeam Assist
Mia AndersonMaintenance Booking
June 3 · 8:30 AMPhoenix
ConfirmedService Reminder
Lucas ThompsonAccount Recovery
June 3 · 4:15 PMVirtual
ConfirmedPowerDialer
Evelyn WhitePackage Renewal
June 4 · 12:00 PMTempe
ConfirmedRebooking
Twenty-seven active conversations remain connected to consent, an objective, a stage, and a visible human boundary.
27 activeCamila ReyesAutoPilot active · monitored
Eligible service relationship
CUSTOMER
Can we restart the follow-up this week?
AUTOPILOT
I verified the eligible account and prepared the approved follow-up. Your approval is required before it moves.
- Current objective
- Resume approved recovery
- Human boundary
- Human approval
AutoPilot completed the safe work, then stopped at the human judgment boundary.
3 decisionsCamila Reyes$4,600 potential value · illustrative
Needs decision
- Why human judgment is required
- The prepared recovery follow-up requires merchant approval before AutoPilot can resume it.
- What AutoPilot already did
- Confirmed eligibility and consent, reconciled the open account context, and prepared the approved follow-up.
- Customer context
- Existing customer with a verified account relationship and a direct request to restart the follow-up.
- Recommended next action
- Approve the prepared follow-up and return the opportunity to Revenue in Motion.
Grace Kim$6,700 potential value · illustrative
Needs decision
- Why human judgment is required
- The customer requested a contract exception AutoPilot cannot authorize.
- What AutoPilot already did
- Paused the playbook, preserved the conversation, and summarized the requested exception.
- Customer context
- Proposal reviewed; the remaining question requires commercial judgment.
- Recommended next action
- Send the exception package to the team.
Isaac Moore$8,700 potential value · illustrative
Needs decision
- Why human judgment is required
- A sensitive billing-owner and banking change requires identity verification.
- What AutoPilot already did
- Stopped the workflow before any account detail changed and preserved the request.
- Customer context
- Active customer with an open recovery opportunity and an unverified administrative change.
- Recommended next action
- Route identity verification to an authorized team member.
ECHELON ID CONTEXT
Marcus Reed
Eligible service relationshipTransaction history
Two prior installments completed; one missed payment
Conversation history
Customer asked to restart the original schedule after a temporary interruption.
Behavior signal
Missed installment followed by a direct reply
Opportunity reason
Existing balance and an explicit request to resume
Playbook used
Payment-plan recovery
Outcome
Payment Plan Reinstated · $2,850
Attribution proof
The approved payment-plan playbook produced a completed payment event that matched the open recovery record.
Processor settlement · May 29ECHELON ID CONTEXT
Jessica Lee
Active account messaging permittedTransaction history
Open balance with two previous service payments
Conversation history
Customer requested one final amount and confirmed the payment window.
Behavior signal
Reply after a balance reminder
Opportunity reason
Open balance with a stated intent to resolve
Playbook used
Approved settlement follow-up
Outcome
Settlement Reached · $1,975
Attribution proof
The settlement was recorded after the customer completed the approved payment link supplied in the conversation.
Settlement receipt · May 27ECHELON ID CONTEXT
Daniel Park
Transactional messaging permittedTransaction history
Past-due service invoice
Conversation history
Customer confirmed receipt of the invoice and requested the secure payment link.
Behavior signal
Invoice opened without payment, then customer replied
Opportunity reason
Past-due invoice with direct customer engagement
Playbook used
Past-due payment recovery
Outcome
Past Due Paid · $1,450
Attribution proof
A completed payment matched the past-due record and the approved outreach window.
Matched payment event · May 25ECHELON ID CONTEXT
Olivia Chen
Rebooking messages permittedTransaction history
Three prior service packages
Conversation history
Customer selected the same package and moved the appointment by one week.
Behavior signal
Normal renewal window opened
Opportunity reason
Repeat-customer cadence reached the approved threshold
Playbook used
Service renewal
Outcome
Service Package Renewed · $2,250
Attribution proof
The renewal booking and associated payment were confirmed inside the defined observation window.
Booking and payment match · May 23ECHELON ID CONTEXT
Ethan Brooks
Customer-requested payment linkTransaction history
Open estimate with required deposit
Conversation history
Customer confirmed scope and asked to secure the work date.
Behavior signal
Estimate accepted without deposit
Opportunity reason
Approved estimate awaiting the required deposit
Playbook used
Estimate-to-deposit
Outcome
Deposit Completed · $1,800
Attribution proof
The deposit was completed through the approved link tied to the open appointment.
Deposit receipt · May 20ECHELON ID CONTEXT
Sophia Ramirez
Existing membership relationshipTransaction history
Long-term membership with one failed renewal
Conversation history
Customer updated the payment method and kept the existing membership level.
Behavior signal
Failed renewal on a previously healthy account
Opportunity reason
Recoverable payment issue without a cancellation request
Playbook used
Membership save
Outcome
Membership Restored · $1,640
Attribution proof
The restored membership and payment were recorded after the approved save workflow.
Membership and payment record · May 17ECHELON ID CONTEXT
Noah Williams
Business-account email permittedTransaction history
One open business invoice
Conversation history
Accounts payable confirmed the corrected reference number before payment.
Behavior signal
Invoice aged beyond the merchant’s normal window
Opportunity reason
Open invoice with a resolvable reference issue
Playbook used
Business invoice recovery
Outcome
Invoice Recovered · $2,115
Attribution proof
The settled invoice matched the open account record and the approved reminder sequence.
Invoice settlement · May 14ECHELON ID CONTEXT
Ava Johnson
Service reminders permittedTransaction history
Two completed maintenance visits
Conversation history
Customer selected the recommended maintenance window and confirmed the address.
Behavior signal
Expected maintenance window reached
Opportunity reason
Known service cadence with an eligible customer
Playbook used
Maintenance reminder
Outcome
Maintenance Booked · $1,685
Attribution proof
The booked maintenance visit and deposit matched the approved service-reminder record.
Booking and completed deposit · May 10ECHELON ID CONTEXT
Liam Carter
Existing account communication permittedTransaction history
Paused account with an open recoverable balance
Conversation history
Customer needed a policy exception, so the conversation was escalated to the team.
Behavior signal
Customer replied with an exception request
Opportunity reason
Recoverable account requiring human authority
Playbook used
Human-assisted recovery
Outcome
Account Reopened · $2,875
Attribution proof
AutoPilot prepared the context, a team member handled the exception, and the resulting payment was confirmed.
Human-confirmed payment · May 6
Revenue back in motion
+$4,600 illustrative opportunity
FROM CONTEXT TO CONTROLLED ACTION
ECHELON ID REMEMBERS.
AUTOPILOT ACTS.
Echelon ID keeps permissioned customer context connected. AutoPilot uses that context to identify an opportunity, propose the next action, stop where judgment is required, and record the outcome.
Identity, consent, transactions, conversations, behavior, timing, and opportunity stay attached to one customer context.
Approved playbooks coordinate conversations, appointments, recovery, and the decisions that need a person.
The merchant can see what happened, who owned the action, and what evidence supports the result.
Detect
A transaction, conversation, customer state, or timing signal creates an eligible opportunity.
Qualify
Rules confirm audience, consent, timing, suppression, value, and playbook eligibility.
Decide
AutoPilot proceeds inside its authority or pauses in Needs You with the reason, context, and recommended action.
Execute
It advances the approved conversation, appointment, recovery, or internal handoff without concealing ownership.
Attribute
Results remain connected to the originating signal, action, customer, financial event, and verification method.
WHAT AUTOPILOT CAN RECOGNIZE
SIGNALS BECOME VISIBLE.
OPPORTUNITIES GET CONTEXT.
A signal does not become an action until the merchant’s eligibility and authority rules are satisfied.
Changed return pattern
A normally active customer has not returned on schedule.
Value and loyalty
Purchase history supports a relevant recognition or retention path.
Timing window
A service interval, season, appointment, or follow-up date is approaching.
Conversation intent
A customer reply or open question reveals the next objective.
Post-purchase moment
Education, maintenance, review, referral, or support is due.
Human boundary
Price, policy, safety, exception, or sensitive intent requires a named person to decide.
APPROVED PLAYBOOKS
REPEATABLE WORK.
MERCHANT-DEFINED BOUNDARIES.
Win-back
Reconnect with an eligible customer whose normal return pattern has changed.
Customer recognition
Create an appropriate follow-up path for a valuable, loyal customer.
Appointment coordination
Propose, confirm, reschedule, and record an appointment inside the approved workflow.
Conversation follow-up
Continue a permissioned exchange while preserving objective, consent, and human takeover.
After the sale
Coordinate education, maintenance, feedback, review, or referral at the right time.
Internal handoff
Route the customer context and recommended next action to the right person.
HUMAN CONTROL
THE SYSTEM STOPS
WHERE JUDGMENT STARTS.
Needs You
See why a decision is required, what AutoPilot already completed, the customer context, and the recommended next action. Approve, edit, decline, send to team, or snooze.
Pause Everything
Stop active playbooks from one visible control without hiding the queue, the decisions already made, or the record of work.
Consent and suppression
Eligibility remains tied to channel permission, frequency, quiet hours, exclusions, and merchant-defined audience rules.
Human takeover
A named person can take ownership when a conversation becomes sensitive, complex, exceptional, or simply better handled by a human.
VISIBLE OUTCOMES
RECOVERY, CONVERSATIONS, APPOINTMENTS—
AND THE PROOF BEHIND THEM.
Recovered Revenue
Only verified financial outcomes enter the recovered ledger. Open opportunities remain visibly separate.
Revenue in Motion
See realistic opportunity value, current stage, last action, next action, and owner—without calling it guaranteed revenue.
Appointments Set
Connect the booking to its customer, source, confirmation state, timing, and location.
Active Conversations
Keep the message, objective, consent, stage, and human boundary together.
CONNECTIONS AND SCOPE
DESIGNED TO COORDINATE
THE SYSTEMS A MERCHANT APPROVES.
Integration availability depends on the merchant’s environment, provider access, data permissions, and implementation scope.
Payment and transaction systems
Use permissioned events to understand timing and outcomes.
CRM and customer records
Keep ownership and context visible across the customer journey.
Scheduling
Coordinate proposed, confirmed, changed, and completed bookings.
Approved communication channels
Respect consent, cadence, quiet hours, suppression, and human takeover.
The interactive product demo above is illustrative and runs entirely in this browser. It does not connect to a merchant account, send messages, create real appointments, submit leads, or alter live data.
NEXT MOVE
SEE WHETHER AUTOPILOT FITS YOUR CUSTOMER WORKFLOW.
Tell us which follow-up, retention, or revenue process currently depends on memory and manual effort.