Built-in AI & Agent
Built into the platform
AI is included with the platform account instead of being broken out as a separate SKU.
Attached to real work
Menu setup, launch help, training, and operator support stay inside the app surfaces teams already use.
Agent stays premium
HospiEdge Agent remains the separate command-center add-on for leadership review above the apps.
Restaurant AI inside the apps. A separate Agent layer when leadership needs oversight.
HospiEdge keeps setup help, training support, and operator guidance inside the live products. HospiEdge Agent stays separate for cross-app review, approvals, and follow-through above the stack.
Open Products for workflow proof, Pricing for bundle math, and Engineering only when implementation depth is the remaining question.
Built-in AI and HospiEdge Agent solve different jobs.
Stay here when the question is faster setup, learning, and in-app help. Open the Agent page only when the need shifts to cross-app oversight above the apps.
Built-in AI inside the platform
Use built-in AI for faster setup, clearer training, and operator help that belongs inside the core apps instead of becoming a separate AI product decision.
HospiEdge Agent as a separate premium command center
Use HospiEdge Agent when leadership wants the separate premium command center above the apps. That command center is priced separately from the included AI layer.
What the AI layer supports
These are the core built-in AI jobs that make setup, training, and day-to-day support easier without changing the buying path.
Menu AI
Stage menu import, review structure, and carry setup work forward before live commit instead of forcing one risky import pass.
AI setup / go-live assistant
Guide teams through staged launch work, setup sequencing, and next-best-step logic while the account is being built out.
Operational guidance
Support operators with practical help across standards, setup, and connected workflow questions inside the platform.
Reader and training support
Keep AI attached to Training and Reader content so teams can move from explanation into the next real task without leaving the platform.
Built-in AI stays inside the apps
Built-in AI belongs inside the products so setup help, training, and operator support stay attached to real workflows.
Agent stays separate
HospiEdge Agent remains the premium cross-app command center above the apps for leadership review, approvals, and follow-through.
Where AI shows up in the operating system
AI helps most when it reduces setup and training friction across real platform surfaces.
During setup
Help with staged menu build, launch sequencing, and next-step clarity while the account is still being configured.
During training
Support Reader and Training content so managers can move from explanation into action without leaving the platform.
During operations
Answer workflow questions tied to real product surfaces such as POS, Label, scheduling, and standards control.
During expansion
Stay useful as teams add more accounts, locations, and connected workflows instead of becoming a one-time import helper.
Decision proof
Use built-in AI for enablement, then switch pages when the decision changes.
Use this proof board to confirm what built-in AI should own, what Agent should own, and when the next question belongs on another page.
Built-in AI is included
Agent stays separate
Route the next decision cleanly
Setup, training, and operator help stay inside the apps
Built-in AI belongs inside real HospiEdge workflows instead of becoming a separate commercial product.
HospiEdge Agent sits above the apps
Cross-app asks, reports, approvals, actions, and oversight stay on the separate Agent page for active bundle customers.
Switch pages by decision type
Only leave this page when the remaining question becomes pricing, workflow proof, Agent oversight, or deeper diligence.
What this page should prove before you leave it
Keep the AI story attached to real operating work, then move to the page that fits the remaining decision.
| Buyer moment | Right page | Why this is the cleaner read | Best next page |
|---|---|---|---|
| The question is buying and launch math | Keep AI as included platform support and move the conversation to Pricing for bundle plans, account count, and launch billing. | This keeps built-in AI from pretending to be a separate SKU while preserving the included-in-platform story. | Go to Pricing when the next decision is commercial instead of operational. |
| The question is workflow fit inside the stack | Move to Products when the buyer wants POS, Label, HETable, Schedule, Ops, Training, or Reader proof beyond the AI explanation. | The stack pages show where AI support attaches to real app surfaces instead of future-tech positioning. | Use Products or the matching buyer page when feature depth matters more than AI positioning. |
| The question is cross-app oversight above the apps | Move to HospiEdge Agent when leadership wants the separate premium command-center add-on for asks, runs, reports, actions, approvals, cases, watchlists, playbooks, and talent follow-through. | This keeps built-in AI and the Agent add-on distinct instead of collapsing them into one vague AI story. | Use the Agent page when the buyer wants oversight above the stack, not more setup help inside it. |
| The question is implementation depth or architecture review | Open Engineering only after the AI story, workflow fit, and commercial direction are already clear. | This keeps diligence work on the Engineering page and prevents the AI page from carrying technical review it does not need to own. | Use Engineering after the page path and commercial fit are already settled. |
Before you continue
- Confirm that built-in AI still reads as included platform support instead of a separate product line.
- Use the proof board to decide whether the next real question belongs to Pricing, Products, Agent, or Engineering.
- Leave this page as soon as the decision turns into bundle math, workflow proof, or deeper diligence.
Implementation path
- Start with built-in AI when the team needs staged setup help, training support, or operator guidance inside the apps.
- Switch to Products, Pricing, or Agent as soon as the decision becomes feature proof, commercial math, or cross-app oversight.
- Open Engineering only after the AI story and commercial direction are already clear.
Connected pages
Once the AI story is clear, open the page that matches the remaining question.
Built-in AI page job
Keep this page focused on built-in enablement, then switch when the next decision is clear.
Use Pricing for bundle math, Products for workflow fit, Agent for cross-app oversight, and Engineering only when diligence is the remaining task.