Identity
Supported customer records, account links, and tokenized identifiers—without pretending every transaction identifies a person.
HOW AUTOPILOT WORKS
SEE THE SIGNAL.
CREATE THE ACTION.
Inside AutoPilot, permissioned customer context becomes a useful next move. The technology has one job: help the merchant recognize customer and revenue opportunities, then do something responsible and measurable with them.
THE MEMORY & INTELLIGENCE LAYER
ECHELON ID REMEMBERS.
AUTOPILOT ACTS.
Echelon ID is not a separate commercial product or a second dashboard. It is the context layer inside the Echelon system. It organizes what is known, what is allowed, what changed, and why an opportunity may matter.
Consent & Eligibility
Channel permissions, opt-outs, exclusions, quiet windows, and suppression rules that determine whether an action is allowed.
Transaction History
Available purchase, payment, visit, balance, and return patterns supplied by connected merchant systems.
Conversation History
Previous outreach, replies, open objectives, stated preferences, and the point where a human may need to take over.
Behavior & Timing
Recency, frequency, seasonality, rebooking cadence, inactivity, and other supported signals—not a guaranteed prediction.
Open Opportunity
The reason, current stage, estimated value, last action, next action, and whether AutoPilot or a human owns the move.
CONTEXT WITH BOUNDARIES
THE SYSTEM SHOULD EXPLAIN WHAT IT KNOWS—AND WHAT IT DOES NOT.
Useful intelligence is not a mystery score. The merchant should be able to inspect the source, permission, authority, action, and outcome behind the recommendation.
Data Map
Which connected system supplied identity, transaction, conversation, booking, or account context.
What this means
A missing feed stays visibly missing. The system does not fill gaps with invented certainty.
Permission Map
Which channel, audience, message class, timing window, and frequency rule apply to the customer.
What this means
Eligibility is checked before an approved playbook can execute.
Authority Map
What AutoPilot may complete, what it may prepare, and what must stop for human judgment.
What this means
Needs You is a control boundary—not a system failure.
Outcome Map
The action, response, financial event, verification source, and attribution limit attached to the result.
What this means
Confirmed, influenced, and estimated outcomes stay separately labeled.
THE SIGNAL-TO-ACTION FLOW
USEFUL CONTEXT.
CONTROLLED EXECUTION.
The order matters. The system observes and interprets before an action is approved, then records what actually happened.
Observe
Supported customer, transaction, conversation, and timing activity creates structured signals.
Interpret
Echelon ID explains the context, the reason an opportunity matters, and the limits of the available evidence.
Approve
The merchant defines the playbook, authority, channel, offer, cadence, suppression, and human boundary.
Measure
AutoPilot records the action and separates confirmed outcomes from influenced revenue and estimated opportunity.
RESPONSIBLE DATA
PERMISSION IS PART OF THE PRODUCT.
Technology earns trust when the merchant understands the data, controls the action, and can explain the result.
THE TECHNOLOGY TEST
IF IT DOES NOT CREATE A USEFUL NEXT MOVE, IT DOES NOT BELONG.
No dashboard theater. No mystery scoring. The product must help the merchant understand, decide, act, or measure.
NEXT MOVE
SEE HOW THE INTELLIGENCE LAYER FITS YOUR BUSINESS.
Tell us the use case, current system, and opportunity you want the technology to solve.