Help & support

Contact Support

Reach HospiEdge support for live workflow issues, billing, setup, scheduling, and buyer questions. Messages go to admin@hospiedge.com with visible app and account context when available.

Return to Legal Ask Advisor first Open operator guide Stay on support form

Reply target Uses the email you enter

Current app https://hospiedgetool.org

Restaurant Not linked

Fast answer first Open Advisor before support when the team still needs a quick operating answer.

Keep support from becoming a first stop when the issue still belongs to a fast coaching reply, a service call, or a live operations judgment.

Documented workflow Use the guide when the next move depends on the written standard or route owner.

Let documented workflow own repeatable how-to clarification so human support can stay focused on blocked follow-through instead of replaying SOP content.

Human follow-through Stay on support only after the lane is clear and the request truly needs a person.

Route the issue here once Advisor and the guide no longer unblock the work, so support receives the app context and the exact next move in one pass.

Recovery handoff

Route context stays attached

The page that sent you here already attached the route and topic. Use the return links below when you need to go back.

Open guides first Review the platform overview Return to settings Stay on the support form

Fast routes

Support, trust, pricing, or schedule?

Use the right desk first when the answer may already live in Advisor, pricing, policy, buyer guidance, or scheduling before you open a ticket.

Fast answer first Ask Advisor before the ticket Use Advisor first when the team mainly needs a quick operations answer, coaching language, or a fast shift decision. Route to support form Start a pilot or buying question Best when you need rollout help, pilot fit, pricing clarification, or a guided next step. Policy and trust Review privacy, AI, and record rules Use the legal summary when your question is about data handling, retention, acceptable use, or AI limits. Buyer overview See the full platform story Use the overview page when you need product fit, pricing lanes, rollout framing, or connected-app context. Schedule surface Check schedule and labor planning Go here for the scheduling and labor-planning lane before opening a support request about team workflow.

Connected desks

Keep support connected to trust, buyer proof, and owner follow-through

Support works best when the request keeps its lane. Keep policy questions tied to legal, buying-fit questions tied to the public proof path, and active-owner questions tied to billing and recovery.

Trust first Legal & privacy desk Use this for policy, AI, retention, and record-trust questions before the ticket becomes a back-and-forth. Buyer path Platform overview Route back into the public proof path when the question is still about fit, rollout shape, or lane selection. Owner return Billing & plan desk Use the owner desk once the account is live and the next step is plan, renewal, credit, or billing follow-through.

Operator continuity

Keep one help stack from fast answer to documented workflow to human support.

Support should be the last desk in the chain, not the first reaction. Use Advisor for quick operating guidance, the guide for the documented standard, and stay on support only when a person really needs to take over the next move.

Advisor → Guide → Support. This page still shows the full escalation order before you submit.

Quick answer first Open Advisor when the team mainly needs a fast operations answer or short coaching help.

Use the AI lane for a quick response, shift wording, or coaching prompt before you open a human thread for something the team can solve immediately.

Open Advisor Advisor desk

Documented workflow Open the guide when the team still needs the written standard, route owner, or handoff rhythm behind the issue.

Keep support from becoming a how-to library. The guide should own repeatable workflow clarification before the issue becomes a person-to-person escalation.

Open guides Quick start

Human follow-through Stay on support when the lane is already clear and a person still needs to step in.

Once the fast-answer lane and guide no longer unblock the issue, submit the routed request here so support receives the operational context instead of a cold start.

Complete the form Return to Legal

Support status

Add the details support needs

Fill in your name, a reply email, a clear subject, and the message so support can respond without extra back-and-forth.

Send a routed request

Tell support what actually happened

Keep the request specific. The existing email routing, context capture, and return-path handling stay the same underneath.

Try Advisor first Review guide Return to Legal

Name

Product area

Impact

Page or screen

Device or browser

Subject

Use one clear subject line so support can route this request without re-reading the whole thread.

Message

Include what happened, what you expected, and who is blocked. 0/8000

Replies default to admin@hospiedge.com. Send the form first, then reply to the email thread with screenshots or extra files if support asks for them.

Request context

What will be sent with this request

Reply toUses the email you enter

Apphttps://hospiedgetool.org

User IDGuest

Restaurant IDNot linked

ImpactNot provided

Page/legal.php

SubmittedWhen you send this form

Fastest request templates

Start with the right support framing

Access issue Best for sign-in, permissions, or missing app access. Subject: Login or access

POS or sync problem Use when checks, users, locations, or cross-app data are not matching. Subject: POS sync issue

Billing help For invoices, subscriptions, card issues, or plan questions. Subject: Billing question

Schedule or team issue For shifts, permissions, onboarding, and team flow questions. Subject: Schedule / team issue

Quick answers

Before you send the ticket

What makes support faster?

The fastest tickets include where you were in the app, what happened, what you expected, and who was affected.

Can I attach screenshots here?

This form does not upload files. Send the ticket first, then reply to the support email with screenshots if needed.

Should I use support for billing?

Yes. You can send billing questions here, but checking billing admin first may answer plan or invoice questions immediately.

Open operator guides Check walkthroughs and how-to guidance before you open a ticket. Review billing admin Use the billing surface for plan status or account payment context.

Follow-through

From request to follow-up

1. Send the routed request

Use the form with the clearest subject, the affected page, and who is blocked so support can route the request without a second discovery step.

2. Keep the reply thread together

Support replies to the address you enter. Add screenshots or extra files there so the same ticket keeps the app context and restaurant details together.

3. Return to the right lane

Use the route cards and recovery links on this page to go back to pricing, schedule, policy, or the blocked screen while follow-up continues.

Return routes

Go back to the right lane

Self-serve route Open guides first Use the guide library when the answer may already exist in a documented workflow or operator reference. Platform story Review the platform overview Use the overview page when the question is really about product fit, pricing lanes, or rollout framing. Workspace hub Return to settings Go back to Settings for connected-account, owner, invite, or billing context before escalating. Human handoff Stay on the support form Use the form when you need a person to respond after checking the fastest self-serve route first.

Keep the lane clear

Support should finish the help stack, not replace the desks before it.

Use Advisor for the fast answer, the guide for the written workflow, and stay on support when the next move truly needs a person to step in with the route context already attached.

Ask Advisor Open guide Return to Legal