How we approach support

We are a small team, so we cannot promise a call centre. We can promise that a person reads what you send, and that you will not have to explain it twice.

The BittaFlow team

2 min read

On this page
  1. One thread, not five
  2. A person, with a name
  3. Plain answers
  4. We will tell you when we are wrong
  5. What we are still working on
  6. What we ask of you
  7. What we will not do
  8. The standard we aim for
  9. Where BittaFlow fits

Every software company says support matters. Most of them mean the support page exists.

We are a small team. We are not going to pretend there is a twenty-four-hour call centre behind this blog. Here is what we actually try to do, and what we are still bad at.

One thread, not five

When you write to us, the reply should come from the same place, with the history attached.

Nothing is more frustrating than explaining a problem to three people in three channels, each starting from scratch. So we try to keep one thread per issue, and to read it before replying.

A person, with a name

Automated acknowledgements are fine. Automated answers to a real question are not.

If you ask something specific, a person should answer it, and sign it. If we cannot answer immediately, we say when we will.

Plain answers

Support replies should be readable by someone who is busy and slightly annoyed. Short sentences. No internal jargon. No “please be advised”.

If the honest answer is “that is a bug and we do not have a fix yet”, we would rather say that than write three paragraphs that avoid it.

We will tell you when we are wrong

Sometimes the problem is us. A message went out at the wrong time, a booking was duplicated, a setting did not do what the label said.

When that happens, the useful response is: here is what happened, here is what we changed, here is what it means for you. Not a discount code.

What we are still working on

Being honest about the gaps is part of this:

  • Response times vary. A small team means a busy week is a busy week. We would rather quote a realistic window than a flattering one.
  • We are better on email than on the phone. That is a limitation, not a policy.
  • Documentation lags behind the product. We write guides after we have answered the same question a few times, which means the first few people get a slower answer.

What we ask of you

  • Tell us what you were trying to do, not just what broke.
  • Send the message or the screenshot, if you can.
  • If a reply missed the point, say so. It is faster than starting again.

What we will not do

  • Argue about whether the problem happened. If you say it happened, we start there.
  • Close a ticket because we replied. It is closed when it is solved, or when you tell us to leave it.
  • Blame the customer’s phone, browser, or staff without checking our side first.

The standard we aim for

You should be able to get an answer without wondering whether anyone read your message.

That is a low bar, and it is harder to keep than it sounds when a team is small and growing.

Where BittaFlow fits

This is the company behind BittaFlow, and support is part of the product. The same shared inbox we build for service businesses is the one we use ourselves, which is a useful reminder of what a good thread looks like.

If something here does not match your experience, tell us. That is the only way this page stays honest.

Useful? Send it to someone who runs the phones.