Skip to content
Beeye Beeye
Features Workload plans, time and profitability, in detail Resolve Every scheduling issue, with a fix and the fees at risk AI connectors Claude, Copilot and ChatGPT connected to Beeye Integrations Your tools connected to Beeye through the API Security Hosting, compliance and contractual commitments

Comparisons

Beeye vs Excel The point by point comparison

Content

Blog Articles and news Resources Webinars, guides and white papers
Log in Book my demo FR
  • Features
  • Resolve
  • AI connectors
  • Integrations
  • Security
  • Beeye vs Excel
  • Blog
  • Resources
  • Log in
  • Français
Book my demo
Support

Open a support ticket

One problem, described once and precisely · our team replies by email

What makes a ticket move fast

A complete ticket avoids the back and forth of clarifying questions, which costs far more than the two minutes spent filling it in.

A subject that names the symptom

“The workload plan no longer shows September engagements” gets worked. “Beeye issue” gets queued.

What you expected, and what happened

Both, not just the second. The gap between them is often the problem itself.

The steps to reproduce it

Numbered, starting from a known screen. A problem we can reproduce is a problem we can fix.

A screenshot

It carries in one image what a paragraph describes badly. What it should show is detailed further down.

Who is affected, and since when

One person or a whole office, since this morning or since the last release: that is what sets the priority.

One problem per ticket

Two subjects in one thread always end up blocking each other. Open two.

Describe your problem

Only the starred fields are required.

The screenshot that actually helps

A screenshot cropped to the error message alone removes exactly what would let us place it.

The full screen, address bar includedthe URL says which page and which record you were on
The whole error messageincluding the code or technical reference at the end, even if it means nothing to you
The clock, if it is visibleit places the problem in our technical logs
Redact what needs redacting before you sendclient names, amounts, personal data: a blur or a solid rectangle is enough, and the rest of the screenshot keeps all its value
For a sequence, a short video beats stillsa few seconds of screen recording shows the path that three screenshots never quite tell

What happens next

01Acknowledgement

You get a confirmation email with your ticket reference. Keep it: that thread is the request.

02Triage

Someone on the support team reads your request, qualifies it and comes back to you, asking for detail if the ticket does not say enough.

03Follow-up

Everything happens on that same email thread. To add a screenshot or a detail, reply to the thread rather than opening a second ticket.

Two kinds of request do not belong in this form: a security incident or a question about personal data goes to security@mybeeye.com; a contract or billing question goes to your usual Beeye contact.

Beeye Beeye

Workload planning, time tracking and profitability for accounting, audit and advisory firms.

Product

  • Features
  • Resolve
  • AI connectors
  • Integrations
  • Security

Resources

  • Beeye vs Excel
  • Blog
  • Resources

Company

  • Book my demo
  • Contact
  • LinkedIn
© Beeye
Terms of use Privacy policy