Review Assistant actions, templates and permissions

Review each action

1. Read the exact content, changed records, recipients, cost/limits, date and timezone.
2. Choose Approve or Reject for that action. To request edits, type what you want changed in the same conversation; the Assistant keeps the relevant proposal context and prepares a fresh preview.
3. The decision button shows a spinner while saving and prevents repeat clicks. Once accepted, the card shows saved/executing progress instead of another Approve button. If the response is lost, it checks the saved status before another decision. Wait for the recorded result; saving approval or preparing checkout does not prove execution.

Changed or expired proposals require renewed review. A strategy approval does not authorize its child actions. Provider authorization and payment steps may need a secure external flow. Order cancellation or a status change does not prove a refund.

On WhatsApp, each proposal has one message with its exact preview, a naturally worded approval question and buttons in your reply language. After a decision, wait for one generated outcome; the Assistant does not add a separate “decision saved” message or repeat the full template. If other proposals still need decisions, it may briefly explain that wait. Approving a proposal is not proof that it executed.

Long previews that exceed WhatsApp's button-message limit direct you to AI → Tasks for review and a decision. Select the named workspace and review the complete proposal there; no details are silently cut to make approval clickable. Expired or changed proposals need a fresh review. If generation is unavailable, a short factual fallback preserves the actual state.

Prepare a WhatsApp template

1. Ask the Assistant to create a WhatsApp template, or open WhatsApp → Templates. Request a wording-only draft explicitly if that is all you need.
2. Review the selected sender, name, category, language, exact text, buttons and synthetic variable examples.
3. Use Approve on the saved submission preview. Accepting wording in chat prepares this preview; it does not submit it. Authentication templates require the provider dashboard and sync.
4. Wait for current Approved status for that sender. Pending is not approval; rejection needs a reviewed revision. Prior versions remain saved.
5. Approve campaign preparation and launch separately. Meta approval never authorizes launch.

Predefined shipping and abandoned-cart drafts include closing text after their final variable. If your edited body starts or ends with a variable, the error identifies which end to fix: add words before the first variable or a closing sentence after the last one. Fill in every variable sample before submission.

A separately approved template-review watch can resume planning in the same chat after the verdict. Ask to stop the watch; it cannot recall an already dispatched submission. Consent, DND, audience eligibility and sender/template readiness are checked before delivery.

Check status and choose a number

• In WhatsApp → Templates, choose WhatsApp number. The selector shows only onboarded, connected phone numbers. Without one, the menu is hidden and creation/sync require connecting a number in Channels. There is no generic Meta profile. Legacy records without a known sender stay read-only.
• The Assistant uses the sole eligible connected number for its preview, or asks which number when several are available. A sender-selection error does not mean WhatsApp is disconnected. If no approval card appears, no submission proposal has been saved; ask for the submission preview.
• Salla installation, updates, authorization and settings reads do not add templates. Prepare templates only when you request them.
• Provider events trigger a fresh status check; background recovery and Sync can recover missed updates. Check Last checked, rejection details and template activity. Pending never means approved.
• Approval, rejection, pause, disablement and applied category changes produce dashboard notifications linked to Templates.

Optional WhatsApp status alerts

One administrator opt-in covers all workspace templates. Review your verified Assistant-paired number, language, timezone and quiet hours, then confirm. The Assistant can prepare the same change for its own approval. Stop alerts here or ask the Assistant to revoke them.

These alerts await the complete operations release. When available, they require your existing morning subscription, today's activation, a real open 24-hour reply window and current permissions. Quiet hours and Do not disturb still apply. Otherwise, updates stay in the dashboard for catch-up. Provider fees may apply; no extra notice templates are created.

Review the Assistant's own morning template

Only administrators in the configured internal Replify Assistant workspace can review these drafts under WhatsApp → Templates, with its registered WhatsApp number selected. Review Arabic and English separately, including buttons. Save edits as a new version; submission needs its own confirmation. These drafts do not appear in merchant workspaces or other numbers' catalogs. Morning delivery remains unavailable until the complete operations release and recipient opt-in.

Future-action permissions

Where available, ask for a reviewed permission for tags, contact updates, conversation assignment, deals, appointment creation or social/campaign drafts. It belongs to the assigned administrator and workspace; reassignment clears it. Ask to require approval again to revoke it.

A saved preference grants no authority. Outbound sends, publication, financial changes, prices and stock retain separate approval. Uncertain provider effects must be reconciled before retrying.