How it works

You do the work. Milita learns what matters.

Teaching Milita isn’t a project. You show her the process once, as the person who normally does it. She watches quietly, asks only what she needs to know, and then proves it on her own.

Preview. The teaching experience on this page is still being built.

Product preview

acme--release.sandbox.my.salesforce.com/lightning/o/Quote/list
RECORDING · DANAShowing me: a normal discount, then one over the lineDone showing Milita
Quotes
Q-1042 · Lakeview Supply
AccountLakeview Supply
Discount25%
Total$75,000
StatusFinance Review

Nothing in the window tells you where to click. Milita hasn’t seen your org yet — that’s why she’s watching.

Step 1

Say what must never break

Start with one sentence, in your own words. Milita doesn’t need a spec or a test plan — just the rule that matters. Not sure how to put it? She offers a few drafts, or you can say it your own way.

Product preview

What must never break in Salesforce?

Discounts above 20% must need Finance approval before the quote is sent.

A rep must never see another region’s pipeline.

or say it your own way

Discounts above 20% must require Finance approval before the quote can be sent.

Step 2

Connect the Bridge Preview — being built

The Bridge is a small helper on your computer. It lets Milita watch a Salesforce browser window that you control — and nothing else on your machine. Pairing happens right inside the conversation, so there’s no settings page to hunt for.

Before the window opens, you confirm:

  • The Salesforce environment (a sandbox by default)
  • Who you’re showing her as — for example, Dana · Sales Rep
  • Which test data she may use
  • Which actions are held, such as anything that would leave Salesforce

Product preview

Bridge
Ready
Environment
Release sandbox
Show as
Dana · Sales Rep
Test data
Approved test accounts only
Actions leaving Salesforce
Held
Start demonstration
Step 3

Show it, the way you always do Preview — being built

A browser window opens, signed in as Dana. Do the work normally. The window grows out of the conversation and folds back into it when you’re done.

At the top of the window, Milita’s strip shows:

  • that she’s watching, as whom, and where
  • what she asked to see, in her own words
  • how many things she’s noticed for later
  • the button that ends the demonstration

Product preview

acme--release.sandbox.my.salesforce.com/lightning/o/Quote/list
RECORDING · DANAShowing me: a normal discount, then one over the lineDone showing Milita
Quotes
Q-1042 · Lakeview Supply
AccountLakeview Supply
Discount25%
Total$75,000
StatusFinance Review

Nothing in the window tells you where to click. Milita hasn’t seen your org yet — that’s why she’s watching.

Step 4

She stays quiet, and asks only what matters Preview — being built

Most of what she notices waits until the end. She interrupts only when carrying on could cause a misunderstanding:

  • two controls could both be the one you meant
  • the business meaning isn’t clear
  • a value looks like an important boundary
  • an action could leave Salesforce or have a real-world consequence
  • it isn’t clear which result proves it worked
  • the person you’re showing her as can’t do what you just did

Product preview

One question

The signals don’t agree well enough on that one — I can read a label but nothing else confirms it, and I won’t guess.

Does “Submit for Finance Review” begin the approval, or only save the quote?

It begins the approval

It only saves it

Step 5

Handoffs: each person shows their part Preview — being built

If a process crosses people, each person shows their own part once. When Dana submits a quote for approval, Maria shows how she approves that exact quote. Her part is usually short.

Product preview

Dana Chen · Sales RepMaria Ortiz · Finance

Dana submits Q-1042. Maria approves Q-1042. The exact quote crosses the handoff.

Step 6

Confirm what she understood Preview — being built

When you’re done, Milita says back what she saw, and separates what she already has from the short list she needs from you. She may propose the rule. She never decides what your business meant.

Product preview

At 20% the quote became Ready to Send. At 25% it went to Finance Review and couldn’t be sent until it was approved.

Already have it

  • Both sides of the line — the pass and the block.
  • Sending refused before approval.
  • Eleven of thirteen controls recognized clearly.

Need you for these

  • ?Who approves the 25% quote. I haven’t been shown that half.
  • ?A name for the unlabeled ⋯ on the quote header.

Let’s take the first one. Who approves it?

Step 7

She proves it, on her own

Milita writes it up as a draft Promise and asks before running it. Then a fresh cloud session performs the whole process by itself — every person’s part, fresh test data, no help. Nothing from your demonstration counts toward the result. If every required result holds, the draft becomes a kept Promise.

Product preview

I’ll run the whole thing end to end — Dana’s part and Maria’s part together, in fresh browsers, with my own test data and no help from either of you. Shall I go ahead?

Yes — run itNot yet
Proof · Tuesday at 09:02
Dana and Maria · clean sessions · 9 of 9 held
Step 8

She keeps it

Once a Promise is kept, Milita checks it again when something meaningful changes, and stays quiet while it holds.

When Milita checksAvailability
When you askAvailable now
On a schedule you chooseAvailable now
When your release pipeline asksPreview — being built
After a managed-package upgradePreview — being built
In each Salesforce release previewPreview — being built
After a sandbox refreshPreview — being built

Recognizing controls

She recognizes a button the way you do. Preview — being built

Milita doesn’t store a click position or a fragile code reference. For each control, she records several independent clues and checks them against the live page while you work:

  • its role and name
  • its visible label, and the field’s underlying API name
  • a stable identifier, where the page has one
  • the section or dialog it sits in
  • the controls around it

Because she knows the field’s API name, renaming “Discount %” to “Discount Percent” doesn’t confuse her.

When the clues disagree, she asks.

She never guesses. She asks you once which control you meant, and remembers your answer as an anchor. If that screen later changes too much, the anchor expires and she asks again.

When she isn’t sure, the result says so.

If she had to act on a control she wasn’t sure of and a result then fails, the run is reported as inconclusive, not as a business failure.

Product preview

What I’m taking · 4 captured

New QuoteStrong
role: button
label: “New Quote”
API name: Quote.New
Discount %Strong
role: textbox
label: “Discount %”
API name: Quote.Discount__c
Status → Finance ReviewStrong
role: text
label: “Status”
API name: Quote.Status
⋯ row actionWeak
role: button
– label: none
– API name: none
Nothing here is a verdict. Watching can’t prove anything.

Repair

When one control changes, she asks about that one control. Preview — being built

I can no longer identify the Finance submission action. Show me that control again.

You show her that one control, in the same conversation. She updates a draft, tells you what business meaning she kept, and proves the revised Promise on her own. Until it passes, the last proven version stays in place.

When you finish

When you’re done, she stops watching. Preview — being built

  • The Salesforce session is revoked.
  • No reusable login stays on your computer.
  • What she learned is saved under your data policy.
  • The Bridge stops observing.
  • Closing the window brings you straight back to the conversation.
  • Anything weak or incomplete is clearly marked for you.

FAQ

Questions about teaching her

Why not just upload a video?
A video only has pixels. The Bridge reads the page’s structure and checks each control against the live page, so Milita knows whether she can perform the process on her own.
Do I have to install anything?
Only the Bridge, on the computer you teach from. Proofs run in our cloud, so nothing needs to stay running on your side.
Can Milita see the rest of my computer?
No. The Bridge works with the Salesforce browser window opened for teaching — nothing else on your machine.
Can I teach her in production?
No. Milita connects only to Salesforce sandboxes and scratch orgs, never production.
Does she need admin access?
No. She works with the same access as the person you’re showing her as. That’s the point: she proves what that person can actually do.
What if I click something that isn’t part of the process?
She notices it and keeps it aside. Only what matters to the Promise becomes part of it.
Does she replay my demonstration?
No. She turns what she saw into a Promise — the people, the steps and the results that must hold. Proofs run from the Promise, with fresh test data.

Show Milita the process you worry about most.

Free for one Promise, forever. Sandbox-first, with access you control.