Contact HospiEdge

Start the conversation with the people who own the reply.

Rollout planning, buying questions, Master AI timing, engineering diligence, or training support — tell us what has to work first and we route the reply from there.

Best first note What has to work first, how many accounts or locations, and when you want to move.
What helps most A short note with scope and timing — not another platform recap.
Start your message Review reply order Email directly

Still deciding where the question belongs? Use About or Investor for company context, and Pricing, Products, or Engineering only when you still need that page-level detail. If the next move is a real reply, start here.

Reply-ready intake

Set the reply path before the first email goes out.

Choose the conversation type, include the scope that matters, and keep the note tied to what must work first.

Who replies matters here. The same leadership team visible on the site owns the intake path, so make the opening message the real conversation starter.

How to start the conversation well

Reply order

Name the decision

Platform fit, buying path, Master AI timing, implementation review, or enablement support — pick the one that matters first.

Reply order

Include scope and timing

Account count, locations, and launch window let the first reply skip basic qualification.

Reply order

Files follow the note

Use the form for the message, then email menus, screenshots, or technical documents with the same subject line.

Reply ownership

Who owns the next step once you send the note

The trust family should stay visible here too. Different conversations stay tied to named leadership instead of disappearing into a generic software inbox.

Founder & CEO

Shalom Bennett

Product direction and company decisions. The first reply comes from the same person who built the platform.

Best for: platform fit, buying path, investor follow-up, and direct company questions

Start with: what has to work first, how many locations or accounts are involved, and what kind of conversation you want next

Director of Operations

Aliya Hale-Bennett

Launch discipline and rollout planning. Operations questions route here from the first note.

Best for: launch order, rollout timing, multi-location setup, and operational constraints

Start with: the first workflow you need live, any timing pressure, and the part of operations that cannot break

Director of Client Experience

Adalisa Bennett

Communication quality and relationship continuity. The team that opens the conversation stays on it.

Best for: training, enablement, follow-through, and keeping the conversation human once it starts

Start with: who needs to be enabled, what support will matter after kickoff, and how the handoff should feel

Choose the conversation path

Buy or demo

Platform fit and first-call planning

Where to start, who joins the first call, and what rollout order to review.

Master AI timing

Master AI now, later, or not yet

Separate the Master AI decision from the core platform conversation.

Implementation

Engineering, diligence, and ownership

Diligence review, custom build scoping, licensing, or technical implementation detail.

Enablement

Training and Reader support

Onboarding, Reader access, training rollout, or enablement planning. Or email admin@hospiedge.com directly.

Page fit

Use Contact when public detail is no longer enough.

Use this page when the next move is a real reply, not another public-page read. Step back only when the question still belongs to company context or one detail page.

Use Contact now

You already need a real reply

Stay on this page when the question has moved past public detail and into rollout planning, ownership, timing, or a direct implementation conversation.

Use other pages first

You still need page-level detail

Step back only when the question still belongs to company context or one public detail page. Use About or Investor for company trust, and Pricing, Products, or Engineering only when you still need that public explanation before a real reply.

Fastest path

Keep the note short and operational

What must work first, how many locations or accounts, and when you want to move is more useful than a long recap of the site.

Still comparing public detail? Pricing, Products, and Engineering are still there. If the next move is a reply, keep going below.

Required fields route the first reply without a second qualification step. Use the email you want on the thread and include account count, locations, or launch timing if known.

Every valid contact request gets a reference code and a saved fallback before we depend on email delivery. Stay on this page after submit so you can capture the confirmation banner.

Reply proof

Capture the reference code

A valid submit returns a contact reference in the confirmation banner. Keep it with any follow-up note or file send.

Reply proof

Saved first on the server

Valid contact requests are written to the server-side contact queue before email delivery is attempted, so delayed mail does not erase the request.

Reply proof

Send files only after submit

If you need to send menus, screenshots, or technical notes, email admin@hospiedge.com after the form with the same subject line and, when shown, the reference code.

Best info

Launch scope

Account count, locations, and whether this is a platform review or a one-app start.

Best info

First workflow

Name what has to work first so we route the reply correctly.

Best info

Master AI timing

Whether Master AI belongs now, later, or not at all.

Step 1

How should we reply?

Contact details and inquiry type for the first response.

Required.
Optional, but helpful for routing.
Use the email you want us to reply to.
Required. Helps us route your message to the right follow-up faster.
Step 2

Route the conversation

Separate buying-path, Master AI timing, and diligence questions before the reply is written.

Optional. Helps us separate active Master AI timing from later-phase or future-interest questions without turning the whole reply into AI jargon.
Keep this short and specific. Examples: 3-account launch review, POS plus HETable first, or Master AI timing for current platform.
Step 3

Write the note

Short, specific, tied to what must work first. Files follow by email after submission.

Current stack, launch timing, account count, and Master AI relevance help us reply faster. One concrete first workflow is better than a long recap.
After you send

Reply routed by workflow

Your workflow and timing details set the reply path — no generic software response.

After you send

Master AI kept distinct when needed

If Master AI is a now-or-later question, that decision stays distinct from the core platform conversation.

After you send

Saved before email delivery

Valid contact requests are written to the contact queue first, so the page can show a real reference even if server mail is delayed.

Screenshots, menus, or technical notes? Email admin@hospiedge.com after submission with the same subject line and, when shown, the confirmation reference code. The banner will tell you whether the request was saved to the queue, sent by email, or both.