PRIVATE RELEASE · SAAS FOR SALESFORCE

Put controlled AI actions inside Salesforce Flow

EKWIS AI gives Salesforce teams focused Flow actions for preparing field values and returning structured AI responses.

The managed package keeps the workflow in Salesforce, uses customer-owned provider credentials and leaves each response under Flow control.

Discuss the private release Check availability

TWO FOCUSED FLOW ACTIONS

Choose A Field Value Or Keep The Response For Flow

EKWIS AI separates two different jobs. The Record Updater prepares a value for a chosen Salesforce field. The Responses Service returns text or structured content so Flow can validate, split and route it.

Record Updater

Pass approved record context and instructions from Flow, then receive a proposed value for the target field.

Responses Service

Request text or structured JSON when the automation needs to decide what happens next rather than update one field directly.

AVAILABILITY

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.

SECURITY & DATA FLOW

The Flow Defines What Leaves Salesforce And What Happens Next

In the current private-release architecture, the managed action calls the configured provider from Salesforce using customer-owned credentials. AI processing requires selected context to leave Salesforce for that provider; the Flow should minimise the context and validate the response before it drives an operational action.

  1. 01 Salesforce Flow

    Selects the approved record context and instruction.

  2. 02 EKWIS AI Action

    Builds the bounded request from configured Flow inputs.

  3. 03 Customer Credential

    Authenticates provider access through Salesforce credential configuration.

  4. 04 Configured Provider

    Processes the selected context under the customer’s provider relationship.

  5. 05 Response To Flow

    Returns a field value, text or structured content.

  6. 06 Validation & Action

    Flow applies rules, review and the approved operational next step.

No EKWIS-Hosted Model Proxy

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

Separate Provider Relationship

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

Retention Depends On The Configuration

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.

SUPPORTING COMPONENTS

Configuration And Reusable Context In Salesforce

Message Builder

Assemble reusable message context for richer prompts without writing a custom integration for each Flow.

Prompt context Reusable Flow

Admin Centre

Configure provider defaults, customer-owned credentials and connection checks from Salesforce admin screens.

Configuration Connection check

SUITABLE USE CASES

A Bounded Task With A Clear Check

EKWIS AI is for operational steps where Flow can supply the right context and control what happens after the response.

Case & Handover Summaries

  • Prepare relevant case context for the next owner.
  • Keep open questions visible for human follow-up.
  • Route the summary through the existing support process.

Field Preparation

  • Suggest a value from notes or record context.
  • Validate the proposal before update.
  • Send uncertain results to a review path.

Structured Decisions

  • Return several values in a known JSON shape.
  • Let Flow check and split the response.
  • Use normal Flow decisions for the next action.

GUIDED ADOPTION

Start With One Workflow The Team Can Own

Onboarding focuses on a bounded use case, its data and its control points. The goal is a working Salesforce process with a named owner, not an isolated product installation.

Use-Case Design

Agree the task, inputs, expected output, review route and measure of acceptable quality.

Configuration & Release

Install and configure the product, build the Flow, test representative cases and release through the customer’s agreed path.

Customer delivery evidence Anonymised customer deployment

Deployed And Validated In A Customer Production Org

An EKWIS AI customer deployment has moved through managed-package installation, customer-specific Flow deployment, permission assignment and production validation.

ONBOARDING PREREQUISITES

What Needs To Be In Place

Provider compatibility and fit are confirmed during onboarding.

Salesforce Environment

An org that can install the managed package and run the required Flow actions through an agreed release path.

Customer Provider Access

A suitable provider account and API access, with credentials owned by the customer and configured in Salesforce.

Owned Use Case

A named business and technical owner, representative test cases and an agreed route for review and exceptions.