Home / Technical Support
SUPPORT & PRODUCT CARE

Six months of support. Confidence after delivery.

Every product we deliver comes with six months of support, including bug fixes at no additional cost.

If something in the delivered functionality is not working as agreed, tell us what is happening. We’ll review the issue, correct the bug and help you check the result.

INCLUDED WITH EVERY PRODUCT
6 months

Support after handover

Free bug fixes for the functionality delivered as part of your project.

Ready for what comes next

You can also request new features, improvements or changes. We review the requirements and agree on the next steps before work begins.

WHAT YOUR SUPPORT INCLUDES

Delivery is the start of using your product.

The included support period gives you a clear route to raise problems and have bugs in your delivered product corrected.

01

Report an issue

Tell us when a delivered feature is not working as expected, with enough detail to help us reproduce the problem.

02

Get the bug corrected

During the six-month support period, we fix bugs in the agreed, delivered functionality at no extra charge.

03

Check the result together

Once the correction is ready, we help confirm that the reported issue has been resolved.

A CLEAR SCOPE

Bug fixes and new ideas both have a place.

If you are unsure whether a request is a bug or a change, submit it. We’ll review it against the agreed functionality and clarify the approach.

INCLUDED BUG FIXES

Something does not work as agreed.

A bug is a problem with functionality included in the agreed project and delivered product. During the six-month support period, correcting these bugs is free of charge.

  • A delivered form fails to submit correctly.
  • An agreed workflow produces an incorrect result.
  • A page or feature has a fault in the delivered implementation.
NEW FEATURES & CHANGES

You want the product to do something new.

You can request additional functionality or changes while your product is under support. These requests are reviewed as further development, with scope, timing and any cost agreed before implementation.

  • A new page type, workflow or user role.
  • An additional integration or reporting feature.
  • A change to how an existing feature is intended to work.
HOW IT WORKS

A straightforward path from report to resolution.

01

Send the details

Share the project name, affected page or feature, and what you expected to happen.

02

We review the request

We investigate the issue or clarify the new functionality you need.

03

We agree the next step

A covered bug is corrected free of charge. Further development is scoped and agreed before work starts.

04

Review the outcome

We let you know what has changed and review the result with you.

Conceptual illustration of software maintenance, bug fixes and support conversations.
Conceptual illustration of software support and maintenance.
ROOM TO EVOLVE

Your next improvement can start with a support conversation.

Using a product often brings new ideas into focus. You may discover a useful feature, a better workflow or a new connection to another system.

Share the goal behind the request. We can discuss the requirements, review the impact on the existing product and propose an appropriate development step.

SUPPORT QUESTIONS

What to know before sending a request.

The included support period starts at final project handover. The handover date provides the reference for the six-month period.

Yes. Bugs in the functionality agreed and delivered as part of your project are corrected at no additional cost during the six-month support period.

Yes. Submit the idea through the same request form. We review new features and changes separately from bug fixes, then agree on scope, timing and any cost before work starts.

Describe what is happening and what you expected to happen. We review the request against the agreed functionality and clarify whether it is a bug fix or a change request.

Yes. You can send a support or development enquiry after the included period ends. We will discuss the required work and any applicable arrangements before proceeding.

Include the project name, affected URL or feature, steps to reproduce the issue, what you expected and what actually happened. If relevant, mention your browser, device and when the problem started.

No fixed response time is stated on this page. Any specific support hours, priorities or response commitments are agreed for the project or support arrangement.