Sendoo: WhatsApp service and Whatson profile

Service architecture

Sendoo is a WhatsApp service based on Whatson profiles available under the platform contract. It is not Meta WhatsApp Business Platform and does not share Meta account assets, approved templates, or service-window rules.

Every customer service instance receives one free provider profile. Availability is checked both remotely and in local ISP/customer assignments so that the same identity is not sold twice.

Prerequisites

Provider access and APIs are prepared at platform level. The ISP needs the enabled module, a configured Sendoo catalog service, and available Whatson profiles. Before selling, define price, billing cycle, included support, acceptable use, and termination procedure.

The settings page explains the service but does not request per-ISP credentials. Provider-access failures must be handled by the platform administrator, never by inserting keys into unrelated fields.

Create the customer service

When creating the service instance, select Sendoo and choose a genuinely free profile from the module-specific field. The list excludes deleted profiles, profiles assigned to an ISP, and profiles already owned by another customer.

Review remote ID, telephone number when present, and state before saving. Activation binds the profile to the customer; a conflict blocks assignment instead of overwriting the existing owner.

Administration area

The instance panel displays Whatson ID, number, and provider state. If the provider is temporarily unreachable, keep the existing association, diagnose connectivity, and retry the read instead of recreating the service or profile.

When changing the customer on an instance, the mapping moves only if the profile is not owned by an ISP or incompatible subject. Confirm the new account holder before saving.

Customer Area and QR

The customer sees profile, telephone number, and state. When pairing is required, generate the current QR and scan it with the WhatsApp device intended for the service. Treat the QR as a temporary credential and never place it in a public ticket or shared document.

After scanning, wait for WORKING. FAILED or ERROR requires diagnosis; refresh state before requesting another pairing operation.

Suspension, termination, and security

Suspension and termination request provider disconnection. Termination also releases the customer association, making the profile eligible for reuse only after remote state and residual-data checks.

Never reassign a profile that remains linked to a device. Verify disconnection, data-retention obligations, contractual closure, and administrative completion before reuse.

Checklist

• Enable the Sendoo module and catalog service
• Define price, cycle, support, and termination terms
• Select a truly free Whatson profile
• Verify profile ID, number, and state
• Assign one customer only
• Protect every pairing QR
• Wait for WORKING before use
• Do not recreate mappings after transient errors
• Disconnect on suspension or termination
• Verify remote state before profile reuse