To begin with - sorry for the delay in response to your ticket. Regardless of my formal and informal explanation of the scenario below, a sorry is warranted here. We'll look into getting a response to your specific case handled.
Typically, it doesn't take that long to get a response from Contact Us. A subset of the Community Growth Ops team, the duo of JNat and animuson, is responsible for running through tickets when they come in. Holidays or other elements might interfere with the process temporarily but the vast majority of tickets get handled swiftly. Sometimes, such as appealing (or even simply just discussing) a suspension, it'll require one of the other Community Growth team members to step in, do deep research and potentially reaching out to the moderators in question as well, before composing the response. Typically this shouldn't take much more than the time it takes to grab someone - they might be in the middle of a task but they usually round it up in tasks to handle by the end of day or at least end of week.
If a longer amount of time is expected, then usually the assigned individual will send a ticket saying something along the lines of "We are looking into this but it may take a while." But if it isn't expected to take a long amount of time, then this kind of formality might end up passed over. Which is usually fine since that means it usually gets responded to quickly enough to not need it... but...
Workloads fluctuate. Between championing some of our other services (Docs, Dev Story, etc.), or handling recurring/important tasks (Area 51, elections, DMCA, etc.), there's a lot of times when one of us... bites off more than they can chew. They grab something which looks like it'll only take a quick bit in the afternoon but get ambushed with a other piles of work that makes the original task fade out of mind for... too long.
Basically this is a pretty longwinded way of saying "Normally it doesn't take that long but oops someone made a goof."