Managed configuration and ongoing support

We keep the group's operating platforms configured as the business changes, on your accounts. That covers rule and template changes, user and permission administration, release checks, new zone or brand set-up, minor integration repairs and an answer for the user who is stuck.

Each month you receive a change log and a short note on what the platforms need next.

• A configuration baseline document for each platform, kept current.
• A change log listing every request, approver, change and date.
• An access review each quarter, listing users and permissions against roles.
• Release notes reviewed against your configuration, with actions.
• A monthly service report: requests handled, response times and recommended changes.
• A named contact and an agreed response time for urgent faults.

• Requests reach a completed change sooner, measured as time from request to completed change.
• Urgent faults are restored inside the agreed time.
• Users hold the permissions their role needs, and the quarterly review counts the users who hold more.
• Every change is recorded, and the changes recorded are compared with the changes made.
• Vendor releases are checked before they reach your users.

Configuration drifts. New staff are given the wrong permissions, a zone is edited in a hurry, a vendor release changes a behaviour, and the person who made the original choices has gone. Small faults then cost the group delivery time and customer goodwill.

• Only one person knows how the platform is set up and they are leaving.
• Users hold permissions they no longer need.
• Vendor releases arrive and nobody checks what changed.
• Requests for a new rule wait weeks for an owner.
• There is no record of who changed what, and when.

Groups that implemented a dispatch, commerce or CRM platform and then lost the person who understood it, and operators who do not want to employ a full-time administrator for each tool.

Qasim Abbas brought more than seven companies at Nexxo Pay and QPay International onto one set of numbers, which is why a change log matters: who approved each change and what it did to the numbers. We keep that log for every platform we administer.

We work across the platforms in your register, including Tookan, Yelo and Hippo, on the licences you hold with each vendor. See how fees work.

Can our own staff keep administering?

Yes. We run alongside your administrators or take over the tasks you choose, and the baseline and change log record every change either team makes.

What happens when the vendor changes something?

We read the release notes against your configuration, check the release and tell you what to expect before your users see it.

What do we get each month?

A change log and a short note on what the platforms need next, with the requests handled and the response times in the service report.

List the platforms you rely on and who administers each today. We show what a monthly service covers and where your team keeps the controls.