Raise and follow requests
Raise a request in the portal or by email. Each one gets a case number, and replies from the portal and email stay in one history, with the files shared on the case.
Managed Salesforce support
A Salesforce team that knows your system.
Bring day-to-day problems and larger changes to the same technical team. We investigate the cause, explain the options and deliver the agreed work, with priorities and progress visible.
Your support workspaceIllustrative view
Service contract
Example CoWork and allowance
- Purchased
- 40 h
- Used
- 24 h
- Remaining
- 16 h
- Billing sync diagnosisNext: confirm the recoveryWorking
- Renewal reminder FlowNext: customer testingStaging
- Customer reportingNext: agree the scopeQueued
The work we can take on
The fixes. The improvements. The bigger technical questions.
A reporting problem, a failing integration or a new approval process needs people who understand the system around it. Support gives that work a standing route into investigation and delivery.
Keep daily work moving
Resolve access, data, reporting and automation issues. Trace unexpected behaviour through Salesforce configuration, code and the systems connected to it.
Improve the way Salesforce works
Refine Flows, Lightning pages, reports and security. Take on Apex development, integrations and larger changes when the agreed scope and support model fit.
Plan the next change
Work through design decisions, release planning and Salesforce platform changes. Keep a prioritised improvement plan alongside the immediate requests.
Your support portal
Requests, hours and decisions in one place.
Your team can follow the work in the EKWIS Support portal: what is in progress, what needs a decision and how much support time is left, without waiting for a status email.
Follow each change
Each request shows a size estimate with its reasoning. Development work shows when it reaches testing and when it goes live.
See your support hours
Check the hours left on each support contract, how they are used month by month, a forecast to the end of the contract and who did the work.
Review designs before we build
We publish proposals and solution designs to you for review. You comment on the exact version we shared, so everyone works from the agreed design.
Meeting notes and recordings
Notes and recordings from meetings we share with your organisation stay in the portal, ready for anyone who missed the call.
Private to your organisation
Only people we hold as contacts at your organisation can sign in, and they see only your organisation’s records. Access is checked continually, so it ends as soon as someone is removed as a contact. Sign in with a passkey or password, and add an authenticator app for a second step.
From request to release
Find the cause. Fix the problem. Keep the context.
When a request needs a change, the team that investigated it carries it through to release. We explain the cause and the change we propose, so you can agree the approach.
Changes are built and tested in a sandbox before production. You can try them there, ask for adjustments and decide when they go live. The request, the decisions and the release stay together on the case.
A scheduled Flow kept stopping at a Salesforce limit.
A customer raised the problem in the portal. A reminder Flow that runs on a schedule was failing with a query-limit error.
- Find the causeThe Flow handled many records in one transaction and repeated its lookups for each one. We showed where the limit was reached and proposed handling each record separately.
- Agree the changeThe customer approved the approach before we built it.
- Build and test in a sandboxWe rebuilt the Flow in a staging sandbox. After testing it, the customer asked for documented elements and error handling before release.
- ReleaseWe added both and deployed the Flow to production.
- Deal with what followsNew failures then traced back to invalid email addresses in the data. Changing that field risked the customer’s other processes, so we added a check and an alert instead. It was tested in staging and released once the customer approved it.
A way of working that fits
Choose the right home for the work.
We agree the scope and operating terms up front. Larger programmes can have a separate plan while ongoing support keeps the day-to-day work moving.
Ongoing support allowance
An allowance of hours, usually for a year, for support and continuous improvement. You set the priorities and see how the time is used.
Time and materials
A route for defined pieces of work or demand that varies too much for a recurring allowance.
A separate project
Dedicated scope and delivery planning where dependencies, a cutover or a committed milestone need it.
Joining starts with your Salesforce setup, the systems around it and the priorities your team needs help with.
Talk through your support needsCustomer experience · Arkessa
Support that continues after launch.
Implementation and ongoing Salesforce improvement for a growing IoT subscription business.
Read the Arkessa story“Salesforce is a critical tool for our business...Ekwis's availability and project-led approach was one of the key factors enabling launch of new features.”
Kapil Joysurry, Business Process Architect, ArkessaRole at the time of the testimonial