Sales automation

Sales automation removes repetitive assignment work while keeping every decision visible. Open Settings → Automation to configure and review automation recipes.

AI conversation replies are configured in the same settings area but use a separate safety boundary. See AI auto-reply to configure Draft or Automatic mode, schedules, approved knowledge, service scope, and human handoffs.

Round-robin qualified-lead assignment

This recipe assigns newly qualified opportunities across an approved group of teammates.

Open Settings → Automation.
Find Assign qualified leads round-robin.
Choose a Pipeline. Only that pipeline’s active, non-terminal stages appear.
Select its qualifying stages and the teammates who may receive assignments.
Enable the rule and choose Save settings.
Repeat for other pipelines that need automatic assignment.

Each pipeline has an independent enabled state, teammate list, qualifying-stage selection, and rotation. An assignment in one pipeline does not advance another pipeline’s turn. Disabling one pipeline leaves the others unchanged. A pipeline without a saved rule is disabled.

When an opportunity is created in, or moves into, a selected stage, Qonvera chooses the next eligible teammate in that pipeline’s rotation. It aligns the opportunity owner, linked conversation assignee, and existing open follow-ups. This recipe does not create a follow-up.

Save settings saves only the selected pipeline. Switching pipelines keeps unsaved edits during the current visit; leaving the page discards them. If another administrator saves the same pipeline first, your save is rejected instead of overwriting their changes. Choose Discard edits and reload this pipeline, review the latest settings, and make your changes again.

If no assignment occurs, check that the pipeline and stage are active, its rule is enabled and saved, and selected teammates still belong to the workspace. Changes are triggered by opportunity creation or a qualifying stage change; saving a rule does not reassign existing opportunities. Owners and Admins can edit these rules; Managers can only review them.

If a selected stage or teammate becomes unavailable, choose Remove unavailable selections, select valid replacements, and save. You can still disable the rule while correcting its selections.

Create an opportunity after service confirmation

Enable Create an opportunity after service confirmation when a teammate should be able to turn a confirmed service interest into a complete opportunity from the Inbox.

Optionally set the delay before the first next action and write its default instruction. Leave both fields empty to create opportunities without a follow-up.
Enable the recipe and choose Save settings.
In the Inbox, review the customer identity and the suggested or manually selected service.
Choose Confirm & create. If you selected a different service, choose Use service & create.

Qonvera creates the opportunity only after this explicit teammate action. It uses the recognized contact, the confirmed active and priced service, that service’s configured active pipeline, the first valid active stage, and the conversation’s assigned owner. If the conversation is unassigned, the confirming teammate becomes the owner. A first follow-up is created only when both its delay and instruction are configured. Existing settings retain their follow-up until you clear both fields and choose Save settings; existing opportunities and tasks are not changed.

If you provide a follow-up, its delay must be 1–43,200 minutes and its instruction no longer than 2,000 characters. Completing only one field prevents saving. You can add a follow-up later from the opportunity or Inbox. Opportunities without one can still appear under No next action risk alerts.

AI remains suggestion-only. A confidence score, matching alias, or AI response cannot run this recipe on its own. Missing contact, price, pipeline, stage, or active owner setup stops the action safely. An existing active opportunity requires review and is never silently duplicated or overwritten.

When the recipe is disabled, the service is placed in the existing manual opportunity form instead. Completed actions appear under Recent runs.

Customer-reply owner notifications

Enable Notify the opportunity owner when a customer replies to create a persistent notification when a new inbound message belongs to exactly one active opportunity with an active owner.

The alert appears in the Qonvera notification bell and opens the conversation.
Agents can receive and read alerts for opportunities they own even though they cannot open Automation settings.
If the conversation has no active opportunity, more than one active opportunity, or no eligible owner, Qonvera does not guess who to notify.
Recent runs show the notification result without copying the customer’s message text.

High-risk, high-value manager escalation

Enable Escalate high-value opportunities at risk to notify selected Owners, Admins, or Managers when an active opportunity meets both conditions:

Its value is at or above the configured minimum in the configured currency.
It has at least one selected risk signal: no next action, overdue next action, inactivity, or too long in its current stage.

The threshold currency is read-only here and always comes from Settings → General → Display currency. Change and save the General setting when the organization needs a different escalation currency. Qonvera compares only that exact currency: for example, an AED threshold does not estimate or convert a USD opportunity. This avoids escalating on an unsafe exchange-rate assumption.

Changes to every automation recipe remain a local draft until an Owner or Admin chooses Save settings. Navigating away without saving leaves the active recipe unchanged.

Qonvera checks for risk regularly and sends at most one escalation per opportunity per day, using the organization’s timezone. The alert appears in the notification bell and opens the opportunity. If expected alerts do not appear, check the saved rule, opportunity currency, risk signals, and selected recipients, then contact support if the problem continues.

Permissions

Owner and Admin: configure, enable, disable, and save recipes.
Manager: review configuration and recent runs, but cannot change the recipe.
Agent: does not have access to Settings, but can receive an owner notification and explicitly confirm a service during normal Inbox work.

Recent runs and auditability

The recent-runs section shows whether a recipe ran, skipped the record, or failed. Disabled recipes do nothing. A failed assignment leaves ownership unchanged, and a failed notification does not stop customer messages from arriving. Review the result before trying an action again.