Factorial support UK: how to get help with your HR software

Key Takeaways

A clear support request is easier to resolve when you know what happened, who was affected and what you have already checked. These steps can help you get useful assistance without sharing more information than necessary.

• Check the help options and support routes available to your organisation.
• Record the affected user, dates, expected result and actual result.
• Try basic access, configuration and browser checks before escalating.
• For payroll or leave questions, identify the relevant period or request.
• Keep a case reference and agree who will provide the next update.

Choose the right Factorial support channel

If you're looking for Factorial support UK, start by checking the routes your organisation can actually use. The right choice depends on whether you need a quick answer, guidance on a task or help that relates to your company’s setup. Keep the question focused so it reaches the right person. If the issue affects several people or a deadline, mention that when you get in touch.

Start with the in-platform help options

If you can still access the software, look for help or guidance within the area where the problem appears. A relevant prompt or help option may point you towards the next step, while the page itself can help you name the feature involved. If you cannot find a useful route, note where you looked and move on rather than repeating the same search.

Search the help centre for step-by-step guidance

A help centre can be useful when you need instructions for a task you can complete yourself. Search using the words on the screen, the name of the task or the exact error message, then check that the guidance matches your situation. If the instructions do not fit your company’s configuration, save the page or note the step where they stop being relevant. That gives support a useful starting point.

Contact your account representative for account-specific help

An account representative may be a suitable contact when your question depends on your organisation’s setup or previous conversations. Explain what decision or configuration you need help with, and include any relevant context you have already agreed. If your business uses Factorial, Faqtic specialises in the platform and offers implementation, process configuration and ongoing HR technology support. You can get practical implementation support if the issue points to a wider setup or adoption need.

Check which support routes are available to your organisation

Support arrangements can differ, so do not assume that a particular contact method, service or response time applies to your organisation. Check your internal guidance, account information or existing support records first. If you are unsure, ask your usual contact which route is appropriate and what information to include. This avoids sending the same issue to several places without a clear owner.

Get ready before contacting support

A short, well-organised report gives someone a better chance of understanding the problem quickly. Before you send it, identify the affected person or group and the part of the process that has stopped working. Include enough context to reproduce the issue, but keep personal information to a minimum. A little preparation can prevent several rounds of follow-up questions.

Note your company details and the affected user

Include the company name and the role or account type of the person affected, if relevant. Use the person’s work email or an internal identifier only when the support route requires it. If the issue affects a group, describe the group and how many people are involved rather than listing everyone’s personal details. This helps establish whether the problem is individual or more widespread.

Describe what you expected and what happened instead

Explain the task you were trying to complete, what you expected to happen and what happened instead. This contrast is often more useful than a broad description such as “the system is broken”. A compact comparison can help you make the report precise:

Once you have set out the difference, add the point at which the process went off track. That gives the person reviewing the issue a specific place to begin.

Include relevant dates, screenshots and error messages

Dates and times help show when the issue occurred and whether it happens repeatedly. If a screenshot would clarify the problem, check it for personal or confidential information before attaching it. Copy error messages accurately, including any short reference code, but do not try to interpret them as a confirmed diagnosis. These details make your report more useful without needing a long explanation.

Avoid sharing passwords or sensitive employee information

Never include passwords, authentication codes or security answers in a support message. Share only the employee information needed to identify the issue, and use an approved secure route if sensitive details are genuinely required. If you are uncertain whether an attachment is appropriate, ask before sending it. Keeping the initial report minimal protects both the employee and your organisation.

Troubleshoot common HR software issues

Some problems have a simple cause, while others need someone to review the setup. Try a few basic checks first, but avoid changing settings at random, especially if they affect several users. Note what you checked and what changed, if anything. That record helps distinguish a local access problem from an issue that needs further investigation.

Check login access, permissions and multi-factor authentication

First check whether the affected person can sign in and whether the issue occurs for just one account or several. Confirm that they are using the right work account and completing any required authentication steps. If they can sign in but cannot see or complete a particular task, the issue may relate to their access permissions. Record the exact message shown rather than guessing at the cause.

Review employee records and configuration settings

If a task depends on employee information or a company rule, check that the relevant record is complete and that the setting matches the process you intend to follow. Compare the affected case with a similar one, where appropriate, without exposing unnecessary personal details. Avoid editing several settings at once: make a note of the original state and change only what you are authorised to change. This makes it easier to see whether a particular adjustment helped.

Look for missing or delayed data in reports

When information appears to be missing, check the report’s filters, date range and selection criteria before assuming the underlying record is absent. Consider when the information was entered and whether the report reflects the period you expect. If a comparison would help, check whether another authorised user sees the same result. Keep a copy of the report name and settings so support can understand what you viewed.

Rule out browser, device or connectivity problems

A quick local check can help establish whether the issue follows one device or appears more widely. Try these steps in order, stopping if the problem clears:

• Refresh the page and sign in again if appropriate.
• Check whether your internet connection is stable.
• Try an approved browser or another device, if available.
• Record whether the same issue affects another authorised user.

If the problem persists across devices or users, include that result in your support request. If it happens only in one environment, share that detail too, since it may narrow down the next check.

Get help with payroll, leave and compliance workflows

When a process involves pay, time away or records that may be used for compliance, it is worth being careful about changes. Start by separating a software question from a question about processing, policy or a decision that needs internal approval. Keep the relevant dates and records to hand, but share them only through an appropriate route. If you are unsure about the effect of a change, ask before making it.

Identify whether the issue concerns software or payroll processing

Describe whether you cannot complete a step in the software or whether the question concerns the processing of payroll itself. Those are different issues and may need different people to review them. Include the action you attempted, the point where it stopped and any deadline involved. Do not assume that a software error explains a payroll result until the relevant records have been checked.

Check leave policies, approval steps and employee records

For a leave question, confirm which policy applies and whether the request has reached the expected approval stage. Check the dates and the relevant employee record, then note any mismatch between the policy and what you see. If the question is about how a policy should be applied, involve the person responsible for that decision in your organisation. A technical review cannot replace an internal policy decision.

Gather details about the relevant pay period or request

The date range or request reference can help keep the conversation focused. Before contacting someone, gather the details that explain the issue without sending a full set of employee records. Useful points to have ready include the relevant period, the affected process and any action already taken. This makes it easier to discuss the specific case rather than the workflow in general.

Ask how changes could affect audit trails or reporting

Before changing a record or configuration, ask what the change will affect and whether it can be reversed. Where records may support an audit or a report, keep a note of the reason for the change and who approved it. If your organisation uses Factorial, Faqtic can help with HR process configuration and reporting optimisation as part of its HR technology services. This can be useful when the question is about how a setup fits your process, rather than a one-off user error.

Understand support availability and response expectations

Do not rely on a support-hours estimate unless it has been confirmed for your organisation. Availability and response expectations may depend on the route you use and the arrangements that apply to your account. Ask what to expect before treating a query as urgent or assuming that an update will arrive by a particular time. A clear record makes it easier to follow up constructively.

Check current support hours and regional coverage

Look for current information in the support guidance available to your organisation, or ask your usual contact to confirm it. Check whether the hours apply to your region and whether they refer to submitting a request or receiving a reply. If the issue arises outside those hours, record when it started and whether work is blocked. Avoid relying on third-party listings for information that may have changed.

Confirm expected response times for your support plan

Ask which response expectation applies to your organisation and whether it changes for different types of issue. A response may acknowledge the case without resolving it, so clarify what the timing refers to. If you have a plan or agreement, check its wording rather than relying on a general statement. This gives you a sensible basis for deciding when to follow up.

Ask how urgent issues are prioritised

Explain the practical impact of the issue, including whether employees are unable to complete a task or a time-sensitive process is at risk. Ask how urgency is assessed and what information would help the team understand the impact. A concise description is more useful than simply labelling a request “urgent”. It helps the person receiving it judge the next step.

Keep a record of the case and any agreed next steps

Save the case reference, the date you contacted support and any updates or actions agreed. If someone gives you a next step, write down who owns it and when you should expect to hear more. This creates a shared record if the issue needs to be handed to another person. It also makes a later follow-up easier to keep factual and focused.

Escalate an unresolved support issue

If an issue remains open, a calm and specific follow-up is usually more effective than restarting the conversation from scratch. Bring the existing case details together and state what is still unresolved. Explain the effect on employees or work, without overstating it. Then ask for a clear next step and a realistic update point.

Summarise the impact on employees or business operations

Describe what people cannot do, how many are affected and whether a deadline or business process is at risk. If the problem has a workaround, say what it is and what limitations it creates. Keep the impact statement factual and proportionate. That makes it easier for the person reviewing the case to understand why the issue needs attention.

Share the case reference and troubleshooting already completed

Include the reference number and a short summary of the checks already performed. Note which steps changed nothing and whether the issue still affects the same users or process. This avoids repeating work and gives the next person useful context. If new evidence has emerged, add it clearly rather than sending the entire history again.

Request a clear owner and expected update

Ask who is responsible for the next action and when you should expect an update. If a resolution date cannot be given, request a time for the next status check instead. A named next step is more useful than a vague promise to look into the issue. Confirm what you should do if the agreed update does not arrive.

Review available alternatives if the issue remains unresolved

If the issue is still blocking work, ask whether there is a safe temporary workaround and what its limitations are. Check with the appropriate internal owner before using a manual alternative, particularly where it could affect employee records or reporting. Keep a record of any temporary process and reconcile it once the underlying issue is addressed. Avoid making duplicate changes while the original case remains open.

Conclusion

Good support starts with a clear description, careful checks and realistic expectations about what happens next. Keep your case details together, protect employee information and ask for an owner if the issue remains unresolved. If you want a partner beyond a single support query, Faqtic helps businesses implement, configure and get more from Factorial, with ongoing HR technology support as needs change.

Frequently Asked Questions

What should I include in a software support request?

Include the task you were trying to complete, what you expected, what happened instead, when it occurred and who was affected. Add relevant error text and the checks you have already tried.

How can I tell whether an issue affects one user or many?

Ask another authorised colleague whether they see the same problem, where appropriate. Record how many people are affected and whether they use the same process or access level.

Should I send screenshots when reporting a problem?

A screenshot can help explain what appeared on screen, but check it for personal or confidential details first. Do not include passwords, authentication codes or information that is not needed to explain the issue.

What should I do if I cannot sign in?

Check that you are using the correct work account and completing the required sign-in steps. If access still fails, record the message shown and contact the support route available to your organisation.

What information helps with a payroll or leave query?

Have the relevant pay period or request dates, the process involved and any reference details ready. Share only the information needed through an appropriate route, and involve the internal person responsible for policy or approval decisions.

When should I follow up on an open support case?

Follow up when the expected update time has passed or the impact has changed. Include the case reference, a short account of what remains unresolved and any new information.

What can I do while waiting for a response?

Keep a record of the issue and avoid making unapproved changes that could affect records or reporting. If work is blocked, ask whether a safe temporary workaround is available and confirm its limitations before using it.