HospiEdge Agent
Leadership job
Clear blocked work, approvals, saved findings, and accountable next steps from one command center instead of bouncing across app tabs and inboxes.
Best fit
Start here when the missing layer is supervised cross-app review and visible follow-through above the apps already running the operating workflows.
Commercial path
Agent is a premium add-on for active bundle customers, so prove leadership workflow fit first, then move to Pricing, Contact, or the live command center.
Supervised AI command center for cross-app review, approvals, and follow-through
HospiEdge Agent gives owners and managers one supervised leadership surface for asks, runs, approvals, actions, cases, talent signals, source health, billing visibility, and live operating proof above the connected HospiEdge stack, so cross-app review does not dissolve into dashboard hopping, vague AI summaries, or manager-note cleanup.
Use the live route only after the leadership-control question is clear; use the review lane below when the buyer still needs fit and boundary proof.
Stay on Agent when the question is leadership workflow. Move lanes when the question changes.
Stay here when the buyer is deciding whether the premium cross-app command center is the right place for leadership review, approvals, follow-through, and live operating proof above the HospiEdge stack. Move to Pricing when the real decision becomes bundle math, add-on fit, or phase-one scope. Move to Contact when the buyer is ready to discuss launch timing, rollout, or account setup. Open Engineering only when the commercial and workflow fit are already clear and the conversation turns into architecture review, implementation depth, or lifetime ownership evaluation.
- Stay on Agent: confirm whether owners and invited managers need one supervised command center above the apps for cross-system review, proof, and follow-through.
- Go to Pricing: settle the commercial path, included monthly Agent Credits, and whether Agent belongs in the active bundle launch before going deeper.
- Open Engineering: use the deeper diligence lane only after the workflow and commercial fit are already clear.
Behind HospiEdge Agent is a visible family-run leadership team.
HospiEdge ties Agent to a visible company leadership team instead of an anonymous AI brand. Shalom Bennett serves as Founder & CEO, Aliya Hale-Bennett serves as Director of Operations, and Adalisa Bennett serves as Director of Client Experience, so Agent buyers can connect launch, approvals, and customer experience to the people guiding the cross-app command center behind the platform.
The live Agent command center is already one click away.
Use the live Agent landing page when the owner or invited manager is ready to sign in. The current route is hospiedge.org/master_ai/public. Sign in with the work email and password already tied to the HospiEdge account, or use the temporary password issued during invite for first sign-in.
How to start using Agent in a real account
Keep the first-use path simple for owners and managers so Agent feels like a leadership command center, not another dashboard to learn all at once.
Owner finishes setup once
The owner signs in first, confirms command-center and location mapping, and makes sure the connected HospiEdge systems are ready before managers rely on Agent day to day.
Invite managers with the same work-email identity
Managers should use the same work email stored across the HospiEdge stack. New invites can use a temporary Agent password for first sign-in and then set a personal password.
Start with one leadership review
The strongest first use is a grounded review for labor drift, turnover, service pressure, training follow-through, recruiting visibility, or profitability — not a broad click tour of every page.
Move work into owned follow-through
Turn findings into actions, approvals, cases, watchlists, and playbooks so the work becomes visible, assigned, and reviewable instead of staying trapped in meetings or messages.
What leadership can see and clear from one command center
The strongest upgrade in the updated app is simple: leadership can now open one command center and see what needs attention, what is blocked, what is aging, and what has real closure proof.
Today command center
Leadership can open one home screen that pulls together urgent approvals, blocked signals, recent runs, and the next role-specific priority instead of forcing owners to hunt through separate app tabs.
Pressure boards that show what is slipping
Agent can keep overdue actions, stale cases, and blocked work visible so operating pressure shows up early instead of quietly aging in manager notes or inboxes.
Outcome and closure proof
The command center is built to preserve saved reports, closure signals, recent completions, and role-aware focus guidance so leaders can see what actually moved, not just what was discussed.
A cleaner decision lane
Approval queues, action follow-through, case escalation, and visible ownership help leadership clear work from one command center instead of jumping between review, delegation, and proof surfaces.
How Agent fits the stack
HospiEdge Agent makes the most sense after buyers can already see what stays in the apps and what should move up into the leadership command center.
Agent works best as the premium command center above the stack after the platform decision is already clear. It is not a replacement for the live apps, not a duplicate of built-in AI, and not a second operating system.
Start with the platform account
The main buying decision is the platform account count, because that unlock path keeps labor, floor flow, service, labels, and training under one commercial frame.
Run the work inside the live apps
Teams still do the daily work inside Ops, Schedule, HETable, POS, Label, the Training & Reader layer inside Ops, and the other live surfaces tied to the same operating model. For HETable specifically, keep the buyer page, guest-facing Public Reservations path, and live host-stand app route distinct.
Keep built-in AI and launch help inside the workflows
Menu AI, setup help, training support, launch help, and app-native guidance stay attached to the core workflows instead of turning into a second disconnected product.
Add Agent when leadership wants one review lane
HospiEdge Agent sits above the apps as the premium owner and manager command center for cross-app review, follow-through, approvals, cases, playbooks, and talent visibility.
Platform below, leadership above
Let the apps run the workflows, let built-in AI support those workflows, and let Agent handle the cross-app review, proof, and follow-through above them.
The add-on is easier to justify when buyers can see what stays in the apps, what moves into Agent, and when the conversation should shift to pricing or launch review.
Need the total platform + Agent monthly math?
When the workflow fit is already clear and the buyer wants the total monthly math, the fastest next step is the Products hub section that shows bundle-only, one-location Agent, and all-location Agent launch examples in one place.
Go straight to the combined monthly math
Open the Products hub to review the combined bundle-plus-Agent monthly totals, included monthly Agent Credits, and usage-pack options in one place.
Keep the buying rule clean
Choose the platform first, then add $199/month for each active Agent location. Each active Agent location includes 2,000 monthly Agent Credits, and extra usage can be added through the published credit packs when needed.
The current Agent capability map is broader than one review screen
These are the grounded product lanes Agent already supports today without changing the current add-on truth or source-of-truth boundaries.
Ask, runs, and saved reports
Use Ask Master AI, focused reviews, run detail views, saved reports, findings, and recommendations to move from a question into a grounded leadership review with preserved context.
Actions, approvals, and accountable follow-through
Agent includes a real action inbox, approval queue, and follow-through capture so important work can move from recommendation into owned next steps with visible review boundaries.
Cases, escalation, and closure
Open cases from findings, route action from cases, escalate when needed, and preserve closure evidence so longer-running issues do not disappear after the first conversation.
Watchlists and playbooks
Keep recurring pressure lanes in view with watchlists and turn repeat issues into reusable playbooks so the team can respond with more consistency over time.
Talent and recruiting oversight
Review talent queue signals, refresh scores, save talent snapshots, draft recruiting follow-through, and keep approved-hire planning visible without pretending Agent owns the hiring system of record.
Source health and setup confidence
Agent shows source status, source testing, account mapping, location mapping, and setup confidence so leaders can see whether the connected data lanes are healthy before trusting outputs.
User, location, and permission controls
The product already includes user invites, role-aware access, location management, self-service profile updates, password changes, approval-policy visibility, permissions summary, and audit visibility.
Billing, credits, and live operation
Agent includes activation flow, billing overview, usage balance, credit-pack purchase surfaces, bundle verification, queue heartbeat visibility, webhook sync visibility, and live checkout signals.
Where Agent adds value across the connected stack
Agent adds value as the cross-app oversight layer. Outside actions still depend on approved integrations and host boundaries.
Labor, hiring, and people-risk oversight
Use Agent to review turnover, staffing pressure, onboarding blockers, hiring follow-through, and leadership exceptions above Schedule while Schedule remains the operational source of truth for its own records.
Operations and standards oversight
Bring together cases, incidents, execution drift, manager follow-through, and cross-location pressure so operators can supervise what needs attention across the connected stack.
Service and guest-flow review
Agent can read across POS, HETable, and scheduling context so service, guest flow, and floor-execution questions can be reviewed from one leadership command center before work is routed back into the right lane.
Commercial and live-operation oversight
The product also helps leadership supervise activation, bundle verification, credit usage, queue health, and live operating signals rather than treating AI as a black box with no operating proof.
Talent and recruiting oversight is now part of the value story
The updated app gives leadership a stronger recruiting lane without pretending Agent owns the hiring site, candidate source systems, or Schedule hiring truth.
Talent queue and saved snapshots
The current talent lane can score candidate signals, save talent summaries, refresh queue context, and keep hiring follow-through visible for the people leading recruiting.
Jobs-network and hiring-hub launch paths
Agent can surface launch paths into the jobs network and hiring hub so recruiters and operators can move from leadership review into the right live recruiting surface without losing context.
Signed hiring-site summary proof
The updated app can probe a read-only signed hiring-site summary, preserve integration history, classify endpoint host posture, and show payload-hash proof so hiring visibility feels real instead of assumed.
Approved-hire and onboarding direction
Agent can help leadership supervise approved-hire follow-through and onboarding blockers, but it does not claim to own hiring-site records or replace Schedule as the hiring or onboarding system of record.
What the built app already does well
These are the strongest current product strengths for buyers who want to understand what Agent already covers well.
A real AI command center above the stack
The built app already has a dashboard/command-center surface with urgent approvals, blocked signals, overdue pressure, stale-case visibility, recent runs, and outcome proof.
Follow-through depth, not just analysis
The product already includes action inbox, approvals, case creation, escalation, closure capture, watchlists, playbooks, and recommendation-to-action routing instead of stopping at insight generation.
Stronger recruiting oversight than the public page used to show
The talent lane already supports queue review, score refresh, saved snapshots, drafted talent actions, jobs-network launch paths, hiring-hub links, and signed hiring-summary proof surfaces.
Commercial, admin, and operating depth
User management, location management, permissions, audit visibility, billing, credits, activation, source testing, webhook sync, queue heartbeat, and live diagnostics make Agent feel like an operating product, not a thin AI wrapper.
Why the add-on earns its price
Agent earns its price when it makes the existing bundle more useful for leadership after the platform is already in place, instead of acting like a replacement system.
One command center above the bundle
Managers already paying for the bundle do not need another disconnected dashboard. Agent gives leadership one place to ask questions, launch reviews, clear approvals, and decide what needs action next across the systems they already use.
Supervised AI workflow, not loose chat
Runs, actions, approvals, cases, watchlists, playbooks, audit visibility, and permission boundaries make the add-on more valuable than a generic AI conversation with no ownership model.
Live confidence becomes part of the value
Source testing, runtime visibility, webhook sync, activation posture, billing visibility, contract proof, and payload proof help buyers trust the live product instead of hoping the AI layer is wired correctly.
The stack data gets more leverage
Agent earns add-on pricing because it increases the leverage of the apps already in the account. Labor, operations, guest-flow, hiring, and commercial signals become easier to review together from one leadership command center.
What reviewers can safely verify today
These proof points help buyers, partner reviewers, and launch evaluators understand what Agent already supports before the conversation moves into pricing, launch review, or engineering diligence.
Leadership can verify what needs attention first
The command center already supports visible pressure lanes for urgent approvals, blocked work, overdue actions, stale cases, recent runs, and saved closure proof.
Source-backed outputs stay more honest
Source connection status, testing surfaces, setup mapping, and health visibility help reviewers see whether the data lanes are ready before they trust reports or recommendations.
Talent and hiring proof stays bounded and specific
Agent can show recruiting adapter visibility, jobs-network launch paths, signed hiring-summary proof, endpoint host posture, and payload fingerprint details without overstating direct hiring-site ownership.
Admin, audit, and billing lanes are already visible
User invites, location control, approval-policy visibility, permissions summary, audit log, bundle verification, activation posture, credit balance, and webhook sync all strengthen buyer trust in live operating visibility.
Live operating proof belongs on the page now
One of the strongest trust upgrades is simple: buyers can see runtime, billing, source, and hiring-summary proof for a real live operating product.
Source health and source testing
Operators can see connection status, last-tested posture, setup/account/location mapping, and source-backed live confidence before a run becomes something leadership relies on.
Queue worker and runtime proof
The updated product includes queue-worker heartbeat and runtime visibility so leaders can tell whether saved runs, follow-through, and support lanes are backed by a live operating engine.
Billing, activation, and webhook visibility
Bundle verification, activation posture, included-credit balance, credit-pack visibility, live checkout signals, and Stripe webhook sync visibility all help the add-on feel like a real product, not vague AI pricing.
Contract, endpoint, and payload evidence
Hiring-site probe history, endpoint-host labels, payload snapshots, payload hashes, and live integration evidence give reviewers stronger proof that the connected lanes are being checked honestly.
Guardrails that keep the message accurate
These distinctions matter for buyer clarity, partner review, and long-term trust.
Bundle-customer add-on
HospiEdge Agent is not included in the current platform bundle. It is a separate premium add-on for operators who already run the HospiEdge bundle and want one supervised command center above the live apps.
Built-in AI still belongs in the apps
Menu AI, setup help, and other app-native AI features still belong to the apps that already use them. Agent adds command-center review above those workflows; it does not replace them.
Read across systems, do not replace them
The current Agent posture is to read across connected HospiEdge systems, keep host systems as the source of truth for their own operational records, and store Agent-owned workflow data inside Agent itself.
Sensitive work stays supervised
Permissions, approvals, redaction, audit visibility, and partner-bound integration rules matter. Agent is designed for supervised follow-through, not unsupervised outside writes or inflated autonomy claims.
No file-import-only public offer yet
Today Agent is sold as an add-on for active bundle customers, not as a separate file-import-first product. Teams that want Agent should start from an active bundle account path.
Pricing and launch
The commercial path stays simple: choose the core platform first, then add Agent as the separate premium command-center layer for active bundle customers when cross-app review, approvals, and live operating proof need their own lane. Each active Agent location includes 2,000 monthly Agent Credits, with optional usage packs when more processing is needed.
Pricing
Starting public recommendation: $199/month per location for HospiEdge Agent as a separate premium add-on for active bundle customers, with 2,000 monthly Agent Credits included per active Agent location and usage packs available when teams need more once the platform decision is already clear.
Best fit
Best for operators who already run the HospiEdge bundle and want one command center for cross-app review, follow-through, recruiting oversight, admin visibility, and live operating proof after the app-level workflows are already in place.
Integration posture
Some outward actions depend on approved third-party integrations, approved partner APIs, or enabled host helpers. That boundary matters when teams plan launch and ownership.
Live recruiting context
Use the Jobs buyer page when the conversation turns into public hiring visibility, location career pages, or how Agent can sit beside the live jobs network without overclaiming direct hiring-site ownership.
Launch path
Use Contact when you want to discuss launch timing, account rollout, partner review, integration direction, or how Agent should sit beside the existing apps in a real account plan.
HospiEdge Agent FAQ
Short answers on pricing, scope, command-center value, live operating proof, and boundaries so buyers can separate Agent from both the bundle and the built-in AI already present in the wider stack.
Is HospiEdge Agent included in the platform bundle?
No. HospiEdge Agent is positioned as a separate premium add-on for active bundle customers and is not included in the current bundle pricing.
Is HospiEdge Agent the same as the AI already inside the apps?
No. Existing HospiEdge apps can still include their own built-in AI features. HospiEdge Agent is the separate cross-app command center for oversight, follow-through, review, and proof above those workflows.
What can leadership actually see from the command center?
The grounded product story now includes urgent approvals, blocked signals, overdue actions, stale cases, recent runs, role-specific focus guidance, and saved closure or outcome proof from one leadership command center.
Does Agent include real workflow and accountability surfaces?
Yes. The current product already includes actions, approvals, cases, escalation, closure capture, watchlists, playbooks, saved reports, findings, and recommendation-driven follow-through rather than stopping at chat.
What does Agent do for talent and hiring oversight today?
Agent can supervise talent queue signals, refresh scores, save snapshots, draft recruiting follow-through, surface jobs-network and hiring-hub launch paths, and show signed hiring-summary proof while keeping hiring-site records and Schedule hiring truth outside Agent ownership.
Does Agent show whether the data lanes are healthy before we trust outputs?
Yes. The current product direction includes source status, source testing, setup and location mapping, source-backed live confidence, queue-heartbeat visibility, and other operating signals so operators can review the posture before trusting outputs.
Does Agent include user, location, and audit controls?
Yes. The updated app already includes user invites, role-aware access, location management, self-service profile and password controls, permissions visibility, approval-policy visibility, and audit log review.
Does Agent include billing, credits, and activation surfaces?
Yes. The add-on already has activation flow, billing overview, bundle verification, included-credit and purchased-credit visibility, credit-pack purchase surfaces, and live operating signals around checkout and webhook sync.
Can HospiEdge Agent take actions outside HospiEdge on its own today?
Some actions depend on approved third-party integrations, partner APIs, or bounded host workflows, so the right expectation is supervised action orchestration and approval-ready follow-through rather than universal unsupported direct automation.
Can someone buy HospiEdge Agent without the bundle today?
No. Agent is currently offered as an add-on for active HospiEdge bundle customers rather than as a standalone purchase for teams outside the bundle.
Why is HospiEdge Agent worth the add-on price?
Because it gives bundle customers one supervised command center for cross-app review, approvals, cases, talent oversight, saved proof, and live operating confidence instead of making leaders piece those decisions together across separate systems and manager notes.
Who should evaluate HospiEdge Agent?
Operators, multi-unit leaders, owners, executive managers, or partner reviewers who want to see how HospiEdge can support cross-app oversight, hiring review, action follow-through, and live operating confidence above the current apps.
Once Agent fit is clear, move to the next decision.
Most buyers do not need another pass through Agent once the fit is clear. The next decision is whether the conversation should move into commercial fit, launch planning, or deeper engineering diligence. Choose Pricing when the real question is bundle math, active-location launch, included monthly Agent Credits, or whether Agent belongs in phase one. Choose Contact when the buyer is ready to scope rollout order, leadership onboarding, or launch timing. Open Engineering only when the commercial and workflow fit are already clear and the buyer now wants implementation depth, architecture review, or lifetime ownership evaluation.
- Go to Pricing: settle bundle math, add-on fit, and launch timing before the conversation gets more technical than it needs to be.
- Go to Contact: move into a real launch conversation when the buyer is ready to talk first-phase scope, account setup, or leadership onboarding.
- Open Engineering: use the deeper diligence lane only after Agent already makes operational and commercial sense.
Separate premium command center
Keep the stack clear, then add Agent when cross-app follow-through and live operating proof matter.
Use the existing app pages and platform pricing to understand the core stack first. Then add HospiEdge Agent for active bundle customers who need one command center for supervised review, action routing, talent oversight, live operating proof, and leadership visibility after the app-level workflows are already established. If the next question is commercial fit, go to Pricing. If it is launch timing, go to Contact. If it is deeper implementation diligence, move to Engineering.