MANSOUR GROUP

WhatsApp Automation

Team, chat and feature controls

SYNTHETIC TESTING

Owner access

Use the private owner launcher to open local controls.

Feature controls

Permissions always apply to the current environment and chat scope.

Internal autonomy permits authorized team-only messages without individual approval. Defined exceptions require approval. Outsiders or unknown participants always block autonomous sending. All modes remain subject to the outbound permission and emergency stop.

Team roster

Add or edit a member

Chat controls

Optional overrides for individual chats. Unlisted eligible conversations automatically follow the team roster; you do not need to add them here. These controls can restrict access, never override participant or sending safeguards.

Use WhatsApp's internal conversation identifier, not its display name. Add a chat only when it needs a specific override.

Eligibility preview

Anyone on the verified active roster, other than Mohamed, makes a chat eligible. Outsiders never become authorized send recipients.

Advanced settings

These limits use the same saved configuration and change history. Confirm business limits and time zone before enabling each connected feature. Working raw context defaults to about30 days.60 days is a flexible cleanup target for unnecessary old copies; WhatsApp history is left alone.

Processing, recovery, attention, model quality and cost

Use a model profile that reliably meets the task’s quality requirements. Escalate for complexity, ambiguity, risk or low confidence. Cost limits hold work for review; they never force a weaker model. A profile requires a verified model connection. Retry settings never authorize repeating an uncertain send.

Owner operations and handoff

Owner-only access for this pilot. This shows the last recorded operator check; it is not continuous monitoring. Credentials are never shown here.

Use the owner launcher to refresh checks or open the private credential-handoff window. Keep credentials and your saved private recovery key in your password manager. Routine backups use the public recipient without password prompts. No secondary operator receives access through this page.

Change history and rollback

Rollback creates a new audited revision. It cannot enable sending. Older revisions without advanced settings use the versioned safe defaults.