How a proactive business assistant knows when to act

The owner describes the business signal and desired outcome in ordinary language. ValueSpace turns it into a reviewable instruction that remains available after the conversation ends instead of depending on chat memory.

• Tell me when a new Shopify order needs manual attention.
• Notify me if WooCommerce stock falls below the agreed level.
• When a qualified lead appears in the CRM, prepare the next-step brief.
• If a deal moves to Contract review, create a follow-up task for the owner.
• Check this product page every morning and tell me if the price changes.
• Warn me if the catalogue has not synchronised by 9:00.

The model is not limited to reminders or a fixed list of scenarios. Any business event exposed through a supported and authorised connection can enter the same trigger, action, approval and delivery lifecycle.

• Shopify and WooCommerce examples include new orders, status changes, stock thresholds, catalogue updates, refunds, fulfilment events, reviews and synchronisation problems.
• CRM examples include new leads, assignments, pipeline changes, customer statuses, tasks, notes, appointments, overdue follow-ups and missed milestones.
• The same approach can extend to booking systems, mailboxes, support tools, analytics sources, document processes, marketplaces and operational services.
• A named provider or event becomes available only after its connection, permissions and real behaviour have been verified.

Different systems produce different signals, but they can be understood through a small set of owner-facing trigger classes.

• Time: a one-time deadline or recurring schedule becomes due.
• Connected event: Shopify, WooCommerce, a CRM or another supported system reports a business change.
• Incoming communication: a new email, message, comment, question or reply arrives through an authenticated connection.
• Observation: a read-only check detects a changed value, threshold crossing, new item or state transition.
• Work progress: an import, export, campaign, document process or synchronisation reports progress, completion or failure.
• Absence: an expected reply, shipment update, approval or data refresh has not happened by its deadline.
• Manual check: an authorised owner tests or evaluates the instruction now without silently changing it.

Receiving an event is not enough. The instruction defines which store, account, customer, order, sender, value, status, topic or deadline makes that event relevant.

• Match a field, category, sender or set of allowed values.
• Detect a numerical change, range or threshold crossing.
• React to a state transition such as unavailable to available or open to completed.
• Find a new or removed item in a collection.
• Evaluate whether a content or record change is materially relevant.
• Detect a missing event, stale source, unusual count or combined set of conditions.
• Use cooldown, frequency and overlap rules to reduce duplicate or noisy work.

Separating these four decisions keeps the instruction understandable and lets the same business signal support different outcomes without granting broader authority.

• Source: where the trusted signal comes from.
• Condition: what makes the signal relevant now.
• Action: whether to notify, investigate, prepare work, update a project or propose a connected-system step.
• Delivery: who should receive the result, through which authorised channel, or whether the result should remain silent.
• The same order event can notify one owner, prepare a fulfilment brief or start an approval-gated workflow.
• The same CRM stage change can create a follow-up, prepare a private summary or require no visible notification.

ValueSpace retains the original instruction, the condition that matched and the evidence associated with it while the requested work progresses, waits or asks for a decision.

• Requested: one accepted signal creates one piece of work.
• Preparing: the assistant investigates or prepares the requested result.
• Waiting: external work, a later check or a human decision is still required.
• Ready for review: the proposed result and its evidence are visible.
• Verifying: the latest external state is compared with the completion condition.
• Completed: current evidence confirms the requested result.
• Blocked or handed over: a permission, connection, ambiguity or human judgement prevents safe continuation.

A useful proactive assistant should not notify on every check, and a flexible trigger must not become unlimited authority to change connected systems.

• Unchanged, irrelevant or duplicate signals can close silently.
• Cooldowns and digests can prevent repeated low-value notifications.
• Read-only checks, comparisons, summaries and private drafts can run within the configured policy.
• Sending, publishing, purchasing, refunding, deleting or changing an external record may require explicit approval.
• A semantic judgement can classify a signal but cannot authorise a consequential action by itself.
• Permissions, connector access and action policy are checked again before an approved external change is applied.

The architecture can accept many kinds of business events, but a live instruction is possible only when the source is supported, authorised and reliable enough for the requested decision.

• ValueSpace cannot monitor an arbitrary source without an authorised connection or bounded read-only capability.
• Shopify, WooCommerce and CRM coverage must be verified event by event for each connector.
• A page or third-party service may be delayed, unavailable or return ambiguous information.
• Meaningful-change rules may need refinement when the monitored source produces noise.
• External channel delivery may be delayed or unavailable and should not cause the business action to run again.
• A trigger cannot grant broader permissions than the owner or connected application already has.

The unified proactive-work experience is designed to let business owners define monitored work in ordinary language while keeping sources, conditions, actions, approvals and results inspectable.

• A standing instruction separates its source, matching condition, action and delivery preference.
• Shopify, WooCommerce, CRM events, schedules and other supported signals can enter the same understandable workflow.
• Any business event exposed by a verified connection can be evaluated as a trigger without creating a provider-specific assistant experience.
• The assistant can establish a baseline and remain silent when nothing relevant changes.
• A matching signal can notify, investigate, prepare work or begin an approval-gated action.
• Work can wait for an external result or human approval without losing its objective and current state.
• The owner can inspect, test, pause, edit, resume or delete a standing instruction.

See how ValueSpace can also plan, check and complete long-running work.