Support

Tell us what broke, what is blocked, or what you need next.

One clear email is enough. Include the organization, the affected document, order, integration, or API call, any screenshots or exact error text, and how urgent it is.

Route the request

We triage by impact and unblockers first.

Use the closest lane below in your subject line. It helps us group duplicate reports and spot high-impact requests faster.

Urgent

Account and access

Sign-in trouble, invites, organization access, email verification, or anything blocking your team from entering Guliel.

Commercial

Billing and plan

Plan limits, Premium support, subscription questions, invoices from Guliel, or account ownership changes.

Operational

Product issue

Documents, expenses, suppliers, logistics, reports, automations, integrations, or data that looks wrong.

Builder

API, MCP, or feature request

Endpoint behavior, OAuth, MCP tools, migration requests, integration ideas, or workflows we should prioritize.

What to include

  • Your login email and organization name.
  • The page URL, document number, order ID, provider, endpoint, or request ID involved.
  • Exact error text, a screenshot, or the steps that reproduce the issue.
  • Whether this blocks issuing documents, receiving payments, closing books, or using an integration.

Support FAQ

Which address should I use?

Use support@guliel.com for product support, account access, billing questions, API/MCP help, and feature requests.

Can I write in Hebrew?

Yes. You can write to support in English or Hebrew. Include technical identifiers in their original language where possible.

Do paid plans get priority support?

Premium includes priority support. Every plan can contact support; priority changes the triage lane, not whether we read the request.

Where should legal notices go?

Use the contact address listed in the Terms for formal notices. Product and account issues should go to support@guliel.com.