Skip to content
SelconLead CRM

Platform practices

Client-specific messaging, not one universal opt-in

Selcon provides communication software and safeguards. Each participating business is responsible for the sender identity and consumer relationship used for its own messaging program.

Selcon's role

Selcon Lead CRM helps participating businesses organize conversations, apply suppression controls, recognize common STOP and HELP requests, respect configured sending windows, and keep production delivery behind explicit launch gates.

The participating business's role

The business contacting the consumer must use a recognizable sender name, define its message purposes, collect and retain appropriate permission, provide support and policy information, and honor opt-out requests.

One client, one program

Each client should have its own business profile, sender configuration, registration evidence, message categories, and support owner.

Registration proof

Public forms, screenshots, disclosures, policy links, and program descriptions show reviewers how a specific business obtains permission.

Recipient proof

Each live recipient still needs a traceable record tying the phone number to the sender, message purpose, source, disclosure version, and consent time.

Before a client sends live messages

  1. Confirm the real legal entity, DBA or brand, and the name consumers recognize.
  2. Confirm who collected permission and obtain the actual form, disclosure, screenshots, or source records.
  3. Separate provider-registration evidence from recipient-level consent evidence.
  4. Create a client-specific Twilio configuration and complete the applicable sender registration.
  5. Import known opt-outs before approving any live recipient.
  6. Run controlled testing, then record an explicit client-specific launch approval.

Questions or support

Participating businesses can contact support@selcon.space or use our contact page.