Offer-to-action mapping
Each offer can point to the correct primary action, fallback action, provider, required inputs, and safe-test mode.
Customer action paths
Tell AI where to send the customer next.
Action Registry maps every product, service, package, or offer to the right next step: buy, book, inquire, quote, call, WhatsApp, deposit, form, or checkout. AI does not get to invent the route.
8+
Action types
Book, reserve, call, WhatsApp, form, quote, deposit, checkout
Tracked
Approval state
Draft, approved, disabled, needs review
Required
Fallbacks
Every critical commercial path can carry a backup route
Booking and inquiry paths
Fallback routing
Safe-test boundary
Platform layer
What this part of Akii actually does
Each part has one job: make client facts, buyer paths, or checks clear enough for AI and people to use.
Reachability checks
Validate whether action paths work on desktop, mobile, provider pages, forms, links, and fallback paths.
Approval workflow
Separate draft actions from approved commercial paths before they are exposed to agents or partners.
Fallback design
Define what agents should do when the primary booking, quote, or payment path is unavailable.
Workflow
Make the next step clear before AI needs it
Start with the client facts as they are. Turn them into approved data, clear customer paths, checks, and fixes.
1
Intent inventoryIdentify buyer intent
List the actions customers actually need: book, inquire, reserve, pay a deposit, call, or use a partner.
2
Draft action mapMap offer to destination
Connect each offer to the correct provider, URL, phone number, WhatsApp path, form, or fallback.
3
Test statusTest the path
Run safe checks for reachability, mobile handling, broken links, required inputs, and provider errors.
4
Approved Action RegistryApprove for agents
Publish only the action paths that the agency or client owner has approved for public endpoints and partner outputs.
How it works
Action Registry fields
The inputs and outputs stay visible, so the agency, client, and AI systems can use the same approved facts.
| Area | Input | Output |
|---|---|---|
| Action type | Booking, reservation, quote, call, WhatsApp, form, deposit, checkout | Clear intent label for agents |
| Destination | Provider name, URL, phone number, form, partner, internal owner | Approved route for the customer |
| Test status | Reachability result, last tested time, evidence, failure reason | Passed, failed, or needs review |
| Fallback | Secondary route and escalation notes | Safe behavior when the primary route fails |
Use cases
Where it is used
Booking-heavy services
Restaurants, venues, clinics, salons, hotels, and local services can expose the correct path per offer.
Agent handoff safety
Agents can send customers to approved destinations without inventing unavailable actions.
QA and monitoring
Broken links, dead forms, missing phone paths, and provider failures become defects to fix and retest.
Straight answers
The practical questions agencies and partners ask before they put Akii to work for a client.
Can one offer have multiple actions?
Yes. A primary action, fallback action, and partner handoff can be mapped separately with test and approval status.
Does Akii process the final booking?
Akii prepares and validates the path. The booking or transaction is completed by the client, provider, or approved destination.
What happens when a path fails?
The failure becomes a defect with evidence, severity, owner, recommended fix, and retest action.
Start with one client whose facts need work.
Structure what the business sells, publish approved outputs, and test whether AI can find the right facts and customer path.