Private release · SaaS for Salesforce

Useful AI, inside your Salesforce workflows.

Add AI to a Salesforce process without rebuilding the request and response handling each time. EKWIS AI provides reusable Flow actions for field updates, text and structured responses, using your own supported provider credentials.

Salesforce managed package · Private release with guided adoption

A case summary for the next ownerIllustrative Flow
01 / Context selected by Flow

Service interruption

“The customer’s connection is unavailable. The initial checks are complete; the technical team needs to investigate.”

EKWIS AI · Response ServiceSummarise the case and suggest a category
02 / Structured response
Summary
Connection unavailable. Initial checks complete; technical investigation required.
Suggested category
Service interruption
03 / Flow presents the draft to its ownerReview before use
Illustrative content and a review-based Response Service workflow. The surrounding Flow supplies the context and implements the review step.

Two focused Flow actions

Prepare a Salesforce value. Or return a response your Flow can use.

Choose the action that fits the job. Both use the context and instructions supplied by your Flow; the implementation determines how the result is used.

01 / Record Updater

Work with a Salesforce field.

Use Salesforce field information to guide an AI-generated value. The action supports field types, picklist options and address handling so the proposal fits the target field.

Return a proposal for review

Configure analysis only, then use a separate Flow decision, screen or update step to handle the result.

Update through the action

Use the action’s update mode where the agreed workflow permits the record change.

02 / Response Service

Return text or structured content.

Request a summary, classification or defined set of values. Flow receives the response and can pass it to the next step.

Text for people

Prepare a summary or draft using the selected record and message context.

Structured output for a process

Request a known JSON shape, then validate the content and use Flow decisions to route it.

Configure review deliberately. The current Record Updater updates the record unless “Skip Record Update” is enabled. Enable that option when your Flow needs to review the proposed value before a separate update.

Built-in controls in the Record Updater

These controls come with the package, so each Flow does not have to rebuild them.

  • It reads and updates records with the running user’s object and field permissions.
  • It saves only exact, valid picklist values.
  • Each result comes with a high, medium or low confidence rating and an explanation, so your Flow can decide what a person should check.
  • It returns one result per record, including any errors, so your Flow can handle each one.
  • It never resends a request automatically, so a slow response cannot cause a duplicate.
  • Saved API keys are stored encrypted and cannot be read back.

Your Flow supplies the content sent for analysis, so the Flow design decides what leaves Salesforce. See where the data goes.

Places to start

Give one step in the process an AI action.

These are examples to configure around your workflow, data and review needs.

01

Prepare the next handover

Give the next case owner a concise account of the issue, the work so far and the questions still open.

02

Turn notes into usable fields

Suggest a value for a selected Salesforce field using the context and instructions supplied by your Flow.

03

Extract information for the next step

Return defined values that your automation can validate, route or send to a person for review.

In use

Running in production, starting with our own support desk.

We use EKWIS AI on every new support case. A recent customer upgrade shows how the Record Updater’s controls behave in a production org.

We use it ourselves

Our support desk runs on EKWIS AI.

EKWIS AI is installed in our own production Salesforce org. Flows on our support desk use it in four places.

  • Size each new caseEvery new case gets a size estimate with written reasoning, which customers also see in the support portal.
  • Set the type and reasonThe case type and reason are set as soon as the case arrives.
  • Summarise the caseAI prepares case summaries for the team.
  • Draft repliesAI drafts update and closing replies for the team to review and send.

See the support portal

From a customer rollout

Upgrading a Record Updater in production.

A customer was using the Record Updater in production to set picklist values on new records. We took the upgrade through their UAT, QA and production orgs, checking each one before moving to the next.

  • Exact values onlyOnly complete, valid picklist values were saved.
  • Existing values keptValues already filled in were left as they were.
  • AI values markedEach value set by AI was marked, so the team can tell it apart from values entered by hand.
  • No guessesRecords the model could not classify were left unchanged.
Customer story · ECI Partners

More recently, they have helped us put AI to use through Ekwis AI, with tools to check and enrich contact and company data and bring together key information on investment opportunities.

— Sam Veevers, Investment Team, ECI

Read the ECI Partners story

Guided adoption

Start with one workflow the team can own.

We agree the use case, inputs, expected output and checks before configuring the package and Flow. Representative test cases help the team decide whether it is ready to use.

  • A Salesforce environment that can install the managed package and run the required Flow actions.
  • A suitable customer-owned provider account and API access.
  • A business and technical owner, test examples and an agreed review route.

Provider compatibility and fit are confirmed during onboarding.

Private release with guided adoption

Available now
Existing EKWIS customers can discuss a suitable use case with their account or support contact.
Delivery model
The Salesforce managed package is provided on a SaaS subscription. We agree the onboarding scope and initial use case before installation.
Wider availability
Organisations that are not yet EKWIS customers can register interest and discuss fit ahead of wider release.
Discuss the private release

Setup and data handling

Know where the data goes.

The configured provider processes the context your workflow sends. EKWIS AI uses your provider credentials; the workflow design determines which information is sent, what is stored and how a result is used.

Selected context leaves Salesforce for AI processing. We make that data path and the surrounding controls part of the implementation.

How does EKWIS AI connect to a provider?

The managed action calls the configured provider from Salesforce using customer-owned credentials held in Salesforce credential infrastructure.

EKWIS AI does not add EKWIS-hosted model middleware to the request path. The provider response returns to the customer’s Salesforce Flow.

Who owns the provider account and usage?

The EKWIS AI subscription and the customer’s provider relationship are separate. Provider access, credentials, usage and terms remain under the customer’s account.

What is stored or logged?

Provider processing and retention follow the customer’s selected account and terms. Salesforce storage and logging follow the agreed Flow design, with the full data path documented during onboarding.

What helps with setup and reusable context?

The Admin Centre provides provider defaults, credential configuration and connection checks from Salesforce admin screens.

The Message Builder helps assemble message context for Flow actions. Each implementation still needs appropriate instructions, validation and exception handling.

Where does human review fit?

The Flow design decides which results need review and what happens after a response. For Record Updater review before change, enable “Skip Record Update” and place the decision and any later update in the surrounding Flow.

People remain accountable for process design, security, testing and release decisions.

  1. Your Salesforce orgFlow selects the contextThe record details and instructions your workflow chooses to send.
  2. Your Salesforce orgEKWIS AI actionThe managed package prepares the request inside Salesforce.
  3. Your Salesforce orgYour stored credentialsSalesforce named and external credentials hold your provider key.
  4. Your provider accountYour AI providerProcesses the request under your account and terms.
  5. Your Salesforce orgBack to your FlowYour configuration decides whether a person reviews the result, the record is updated or the next step runs.
The request path for an EKWIS AI action. No EKWIS-hosted service sits between your Salesforce org and your AI provider.

Explore the right next step

A package for Salesforce. A team for the wider workflow.

EKWIS AI is one way to put AI into a working process. Our consulting can help when the job spans other systems, information sources or the way your technical team delivers work.