Contact Support

Support Channels by Tier#

The support channels available to you depend on your OpenBoxes Lift subscription tier:

Channel Shared ($150/mo) Dedicated ($600/mo) Enterprise ($1,800/mo)
Portal chat support Yes Yes Yes
Community forum Yes Yes Yes
Priority email support — Yes Yes
First-response target — — 8 business hours (US business hours)
Named engineer with a faster target — — Available as an add-on

There is no phone support on any plan.

Response Times#

We do not publish response-time targets for Shared or Dedicated support requests; Dedicated requests are handled with priority. Enterprise agreements carry an 8-business-hour first-response target during US business hours, and a named Support Engineer (2-business-hour target) or Senior Engineer (1-business-hour target) is available as an add-on. These are response targets, not resolution promises.

How to Get Support#

Option 1: Chat (All Tiers)#

  1. Log in to the customer portal at app.openboxes.cloud.
  2. Click the chat icon in the bottom-right corner.
  3. Describe your issue and our AI support assistant will help you immediately.
  4. The assistant can look up your account, check your instance status, and search our knowledge base.
  5. If your issue needs human attention, you will be connected to a support agent.

Option 2: Email (Dedicated and Enterprise)#

Send an email to support@openboxes.cloud with the details of your issue. Email from Dedicated and Enterprise accounts is handled with priority; Shared customers get the fastest answer through the portal chat.

What to Include in a Support Request#

The more detail you provide upfront, the faster we can help. Please include:

  1. Your instance URL — e.g., yourorg.openboxes.cloud
  2. Description of the issue — What happened, and what you expected to happen
  3. Steps to reproduce — The exact sequence of actions that triggers the problem
  4. When it started — Date and approximate time (include your timezone)
  5. Who is affected — Just you, your whole team, or specific users
  6. Screenshots or error messages — Copy the full error text or attach a screenshot
  7. Browser and device — e.g., Chrome 120 on Windows 11
  8. What you have already tried — Clearing cache, different browser, etc.

Example of a good support request:

Subject: Unable to approve purchase orders since Tuesday

Instance: acme.openboxes.cloud

Description: When I click "Approve" on any purchase order, I get a red error banner that says "You do not have permission to perform this action." This started on Tuesday March 25. I am logged in as sarah@acme.org with the Manager role. I can view POs but cannot approve them. Other managers on our team have the same issue. I tried in Chrome and Firefox — same result.

Escalation Process#

If your issue is not being resolved in a timely manner, you can escalate:

  1. Reply in the same chat conversation or email thread and ask for escalation. Explain what is blocked and why it needs urgent attention — an outage or data problem is escalated immediately.
  2. Enterprise customers escalate under the support terms in their agreement; the Support Engineer add-on includes direct escalation to engineering, and the Senior Engineer add-on puts a senior engineer on your issues directly.

Issues that affect more than one customer are treated as platform incidents and tracked on the status page.

Support Scope#

Our support team can help with:

  • Platform issues (provisioning, login, performance, availability)
  • OpenBoxes configuration and setup guidance
  • Integration setup and troubleshooting
  • Account and billing questions
  • Data export and migration assistance

For issues that fall outside our scope, we will point you to the right resource:

Issue Type Where to Go
OpenBoxes bugs (software defects) GitHub Issues
OpenBoxes feature requests Community Forum
How-to questions about OpenBoxes features Help Site or Community Forum
Custom development or consulting Contact sales@openboxes.cloud

Contacting Sales#

For questions about pricing, plan upgrades, the Enterprise tier, or nonprofit and institutional arrangements: