HR Software Resources

Say a payroll question comes up on a Friday afternoon and needs a person: I've been looking into how RUN Powered by ADP users get through to a phone agent rather than the chatbot, and the route described in recent G2 reviews is to ask for a human directly, either inside the AI chat or on the phone system, with chat often reaching someone sooner than the phone line. Phone waits are what stretch, particularly in busy periods and around tax season.

Once someone is on the line, the support itself is what people value: representatives who are responsive and knowledgeable, chat help that's available straight away, and guidance through the initial setup. In small business payroll, that's the reason to want a person at all. A question about a pay run usually needs someone who can see the account and explain what happened, and that's the kind of help people describe getting once they're through.

What I'd like to hear from people who contact support regularly:

• Do you ask for a person straight away, or let the AI try first?
• Outside tax season, is chat or phone quicker for you?
• Is there a time of day you've found works better for calls?

And for anyone who now does most of their support over chat, what still makes you pick up the phone?

Been looking into what a BambooHR custom report can actually be built to do. From the reviews, the standard set covers headcount, turnover, time off balances and employee data, all drawn from the employee record. Filtering options and field selection are what people ask about once the question sits outside that set.

Compared with most HCM Software, the single-record foundation is the quiet strength here, and it is worth stating plainly: because every report pulls from one source, numbers reconcile against each other without anyone checking. HR teams coming from spreadsheets or from a system where payroll and HR hold separate records will recognise how much work that removes.

Where it gets harder is the gap between what is stored and what someone is asking for. A question that needs data from outside BambooHR, or a cut the field structure does not support, is the point at which people export.

Things I'd like to hear from people who build these regularly:

• Which fields are filterable versus display only
• Whether custom fields you add become available in the report builder

And separately, something I'm curious about rather than critical of: how many of your reports are genuinely new questions, versus the same monthly set? That ratio seems to decide whether built-in reporting is enough.

A question I keep coming back to with BambooHR is what happens to an approval that does not fit the standard shape. From the reviews, two situations recur: a request needing two sign-offs, and one that should reach a function such as finance rather than a line manager. The single-approver path covers the common case and these are the edges around it.

What does come through positively is that the standard approval paths are described as low-maintenance once set, with time off, onboarding and data changes each having their own route. For organisations where one manager approves for their own team, that covers the common case without anyone configuring per-employee rules.

The gap people describe shows up in specific situations rather than generally:

• Requests above a threshold that should need a second sign-off
• Approvals that belong to finance or legal rather than the line manager
• A manager requesting leave, where the approver is themselves

What I'd like to know is which of those you have hit, and what you did. Routing to a shared inbox, approving outside the system, or restructuring the org chart to make it work are the options I can imagine, and none of them is obviously right.

A second question for anyone further along: did this become a reason to look at other HCM Software, or is it a manageable gap?