Owners setting up the command center
Use this guide when the owner needs the cleanest first-use path for Agent and wants the leadership role clear before rollout details take over.
HospiEdge Agent guide
How to use HospiEdge Agent without turning it into another dashboard
This guide explains the plain-language owner and manager path for HospiEdge Agent: how first use should start, what the live command center already does well, and how to tell when the add-on belongs in the leadership workflow.
- Owner setup once: the owner finishes command-center setup and access mapping before the broader team relies on Agent.
- Manager sign-in path: invited managers use their work email, and new invites can use a temporary Agent password for first sign-in.
- First real use: start with one grounded question or one focused review instead of trying to learn every screen at once.
- Why it earns the add-on: leadership gets one live command center above the connected apps instead of another disconnected dashboard.
Who should read this page
Use this guide when the question is how a real owner or manager should start using Agent and what role it should play above the stack.
Managers being invited into Agent
Use this guide when a GM, assistant manager, or supervisor needs the plain-language first-use story before stepping into the live command center.
Operators evaluating the command-center add-on
Use this guide when the team wants to understand what leadership work Agent actually improves so the add-on is judged on workflow value instead of AI hype.
How to start using Agent in a real account
This is the safest plain-language first-use sequence for owners and managers.
1. Owner finishes the setup once
The owner signs in with the work email, completes the command-center checks, confirms account and location mapping, and makes sure the connected HospiEdge systems are available before asking managers to rely on Agent.
2. Invite managers with the same work email they use across HospiEdge
The owner adds managers or supervisors to Agent, assigns their access, and gives the temporary Agent password for first sign-in when needed. That keeps the team inside the same restaurant group instead of creating separate standalone accounts.
3. Start with one question or one guided review
The fastest first use is not to click everywhere. Ask one grounded question or run one focused review for labor, turnover, service, operations risk, training, or profitability.
4. Turn the output into owned follow-through
Move from findings and recommendations into actions, approvals, cases, or watchlists so the work does not die in chat, meetings, or email.
5. Close the loop with proof
Use the shared command center to see what was assigned, what is blocked, what was approved, and what closed with proof. That is where Agent becomes more than another dashboard.
What the built app already does well
Use this section for command-center proof first so the product can be judged on operating value before the commercial decision.
Grounded cross-app review
The built app is designed to read across five connected read-only source systems — POS, Schedule, Floor, Ops, and Label — while writing its own runs, cases, approvals, and workflow records inside Agent itself.
Analysis that turns into command-center workflow
Agent already has live command-center surfaces for ask, runs, reports, findings, recommendations, actions, approvals, cases, watchlists, playbooks, talent review, source visibility, settings, audit trail, user management, and location management.
Command-center visibility instead of siloed manager notes
Owners and managers can use one command center to see what matters now, what is overdue, what needs approval, what changed, and what closed with proof across the connected stack.
Supervised follow-through, not black-box automation
Permissions, approvals, redaction, and audit logging are part of the product story. That makes Agent stronger for real operations than a vague automation claim with no visible controls.
Why Agent is worth the add-on
Agent becomes easier to justify when buyers can see that it is a leadership command-center layer, not a second copy of the apps they already run.
It increases the value of the bundle you already pay for
Agent is worth the add-on when the team already has labor, operations, floor, POS, and label data inside HospiEdge but leadership still has to piece together the story manually.
It compresses multiple management lanes into one command center
Instead of bouncing between reports, messages, spreadsheets, and separate manager follow-up lists, Agent gives leadership one command-center lane for decisions, approvals, cases, and next steps.
It helps work reach closure
The strongest product difference is not that Agent can generate text. It is that Agent can help a restaurant move from signal to owner, from owner to action, and from action to proof.
It is cheaper than rebuilding the same oversight layer with separate vendors
Restaurants often pay separately for labor control, tasking, reporting, floor tools, compliance, and leadership follow-through. Agent earns the add-on when it gives ownership one place to review all of that together above the stack.
Boundary rules that keep the story honest
These are the practical rules that keep Agent positioned like a real operating layer instead of hype.
Agent does not replace the core apps
The live apps still handle the daily operational work. Agent sits above them as the leadership and review layer.
Host systems remain the source of truth
Schedule, POS, HETable/Floor, Ops, and Label keep owning their records while Agent owns its own review and orchestration records.
Managers should not rerun owner setup
Owners set up the command center once. Invited managers should sign in with their work email and land in the correct command-center lane or see a clear access-pending state.
The product story should stay honest
Agent should be sold as supervised cross-app follow-through and review, not as unlimited unapproved automation or a disconnected chatbot.
FAQ
These are the plain-language answers owners and managers usually need first.
Who should sign in to HospiEdge Agent?
The owner signs in first to complete the command-center setup. After that, invited managers and supervisors should sign in with their work email and password tied to their HospiEdge access. New invites can use the temporary Agent password for first sign-in and then set a personal password.
What should the first real use of Agent be?
Start with one grounded question or one focused review such as labor drift, turnover, service risk, training follow-through, or profitability review. Do not try to make the team learn every screen on day one.
What does Agent do better than a normal AI chat tool?
Agent is stronger because it is connected to real restaurant context and can turn review into a live command-center lane with runs, reports, actions, approvals, cases, watchlists, and follow-through instead of stopping at a text answer.
Why is Agent worth paying for on top of the platform bundle?
Because it gives leadership one command center above the apps to review signals, route work, preserve accountability, and close the loop with proof. That makes the data inside the platform more valuable and reduces dropped follow-through.
Is Agent included in the HospiEdge platform bundle?
No. The public story is that AI is included in the platform, while HospiEdge Agent is a separate premium add-on for active bundle customers.
What is the current public add-on pricing story?
The current public direction is $199/month per active Agent location with 2,000 monthly Agent Credits included per active Agent location, plus usage packs when a team needs more processing.
Use Agent above the stack
Start with one grounded review, then decide whether Agent belongs in your leadership workflow.
Use this guide for first-use clarity, the product page for fit detail, the live command center for inspection, and pricing or contact once the rollout decision becomes specific.