A customer texts first
Maya says she is your AI assistant, includes the required SMS notice, and asks one relevant question.
MayaOne complete customer journey, who owns each leg, and the rules behind every message.
Maya says she is your AI assistant, includes the required SMS notice, and asks one relevant question.
MayaScope, address, priorities, and corrections are held and reused instead of asked twice.
MayaMaya organizes the scope. You write or revise the range and the assumptions behind it.
You decideMaya asks whether the approved range still works, and is explicit that it is not a final quote.
MayaMaya gathers preferences and shares the windows you gave her. You confirm the final pick.
You decideAfter the visit Maya organizes what is known and asks what the customer should hear next.
You decideEvery claim on this site maps to a registry entry that ships with the same build.
Project questions, corrections, remembered facts, and one useful next step per message.
Compact requests carrying customer context, the exact revision, and the outgoing preview.
Price and timing move only through an explicit decision from you, reviewed hands-on during the pilot.
Business facts and a sample conversation are reviewed before activation. Post-visit next steps stay yours.
When one of these ships, the versioned registry changes first. This page follows.
Maya names herself as your AI assistant from the first reply. She never claims to be a person.
Each message answers only what is supported, states a boundary when one matters, and asks at most one question.
Approval applies to one wording. Change a word and it needs its own approval.
A promise is queued only after its owner, deadline, and recovery path are recorded.
When an answer can’t be supported, Maya routes the question to you instead of manufacturing certainty.
The published transcripts include a correction and a late answer — not just the clean path.