Workeros — Product Decisions

P1 · Slack + WhatsApp

After a run fires from chat — does the operator hear back?

Today: trigger from Slack/WhatsApp → ack → silence. You must return to the web UI to see the result.

Build the completion loopREC

run my CRM sync

On it — run started.

✓ Done · synced 14 contacts to HubSpot

Emily DMs the outcome. Channels become real "operate-from" surfaces.

Trigger + approve only

run my CRM sync

Run started (run_id a1b2c3)

…no further updates — check the web app

No new infra. Be explicit in copy that channels fire + approve, not monitor.

P2 · Slack + WhatsApp + Emily

Each channel can do different things — should we make that visible?

WhatsApp pushes approvals, Slack doesn't; Slack has buttons, WhatsApp is text. Nothing tells the user what each channel can/can't do.

Show capabilitiesREC

Slack

WA

Run

✓

Approve

✓

/floom help → what each channel does

A help command + Settings section listing each channel's powers.

Just reach parity

Slack

WA

Run

✓

Approve

✓

Make Slack = WhatsApp so there's nothing to explain.

Leave (current)

Slack

WA

Push

✗

✓

Buttons

✓

✗

Asymmetric + invisible. Lower priority than P1/P3.

P3 · Web UI

The worker page shows 8 tabs incl. code — too much for a non-technical operator?

The most-used page exposes YAML, Python, retry config + MCP allowlists to someone who just wants to run their sync and check results.

Operator viewREC

RunRunsMemoryAdvanced ▾

Hide Source/Tools/Settings behind Advanced. Operator sees the essentials.

Two entry points

Simple⟶ full dev page

Simple view for operators, full 8-tab page for developers — separate routes.

Keep + rename

AboutRunRunsSourceSettingsBrainTools

Tools→Integrations, Settings→Schedule. Source stays. (Brain stays Brain.)

P4 · WhatsApp · OSS vs hosted

The WhatsApp QR is a hardcoded number — intentional or a bug?

Settings hardcodes WA_BOT_NUMBER = 16503999709. Self-hosted OSS users get a QR pointing at someone else's number.

Intentional (hosted)

+1 650 399 9709Connect to EmilyHOSTED CLOUD

Keep one number; label it clearly as a hosted-cloud feature for self-hosters.

ConfigurableREC

+[your number]From env / configPER-INSTANCE

Read from env; self-hosters set their own. Treat the hardcode as a bug.

P5 · Slack + WhatsApp

When Emily creates a worker in chat — link, or a tappable card?

Today she replies with text + a web link the operator has to open separately.

Rich card in-channelREC

Worker created · Lead Scorer

ReviewRunDisable

Review / run / disable right from Slack + WhatsApp.

Create in the app

Created your worker.

workeros.floom.dev/workers/8f3a…

Channels run + approve; creation happens in the app where review is natural.

Bonus · #1373 · per-worker memory

Should every worker remember out of the box?

Today memory.enabled defaults to false — workers don't remember unless you turn it on.

A · On by defaultREC

Lead Scorer

MEMORY.md · remembers across runs

Folder created at worker-create, visible in Brain. Matches your mental model.

B · Opt-in, obvious

Lead Scorer

Memory

A clear on/off toggle on the worker with a one-line explainer.