Maximum Depth of a Call Hierarchy

I've been wondering for some time now what's the maximum depth for a call hierarchy. If I have a big method, after refactoring, I often come to code looking like this:

void A()
{
    //...
    B();
}

void B()
{
    //...
    C();
}

void C()
{
    //...
}

So I am calling a method which calls a method which calls a method (and so on) - all in the same class. Is there a rule of thumb how many levels are too many? (And is the term "call hierarchy" correct for this issue?)

Would it be better if I refactor so that A somehow calls both B and C?