Responsible Outreach Controls
What our platform enforces, what clients configure, and where responsibility sits.
How to read this page
StrivePoint provides outreach software to business customers. Our customers decide who they contact, why, and what is said. This page describes the technical controls our platform actually operates today, stated plainly and without exaggeration. A control is listed only if it exists in the running product, and each is labeled with how it behaves.
- Enforced — the platform applies it automatically and a client cannot switch it off.
- Configurable — the client chooses the setting; the platform applies whatever is configured.
- Partially implemented — present, but with known coverage gaps.
- Planned — designed and scheduled, not yet operating.
- Not available — not offered.
We do not claim that any campaign run on this platform is lawful. Lawfulness depends on the data, the consent, the offer, the script, the seller, and the jurisdictions involved — all of which the client controls.
Control inventory
Campaign authorization
EnforcedA campaign cannot dispatch until an authorized user of the owning client account activates it, and the authorization event is recorded.
Active-client validation
EnforcedSuspended client accounts lose portal data access and their campaigns cannot dispatch.
Active-user validation
EnforcedOnly portal users whose membership status is active can read or act on client data.
Internal do-not-call suppression
EnforcedNumbers on the client's internal do-not-call list, and globally scoped safety entries, are held before dispatch and on every retry.
External DNC and phone screening
ConfigurableWhen a screening provider is configured, numbers are checked against national, state, and DMA do-not-call sources and for invalid or disconnected status. Unscreened and stale results fail closed.
Voice opt-out capture
EnforcedExplicit do-not-call requests detected in a completed call are recorded and suppress further automated dialing of that number for that client.
Contactability suppression
EnforcedWrong-party, disconnected, and do-not-call outcomes from prior attempts remove a record from future dispatch selection.
Universal calling window
EnforcedAutomated calling is confined to a single conservative daily window in United States Eastern Time, and every configured slot is intersected with that window.
Supported-timezone gate
EnforcedRecords that cannot be resolved to a supported continental United States timezone are excluded from automated dialing rather than dialed on an assumption.
Weekend exclusion
ConfigurableWeekend dialing is off unless an authorized user of the client account enables it.
Campaign calling slots
ConfigurableClients schedule the hours in which each campaign and each outbound number may dial.
Contact-frequency and attempt limits
EnforcedHourly and daily caps are reserved atomically per campaign and per outbound number, and a maximum attempt count ends outreach to a record.
Outbound number health
EnforcedPer-number hourly and daily safety limits and health events govern how each caller-ID number is used.
Duplicate-dispatch prevention
EnforcedReservations are atomic, so a record cannot be dispatched twice by concurrent scheduler runs.
Audit history
EnforcedCampaign authorization, lead activity, suppression changes, and security events are written to append-only audit tables.
Client isolation controls
EnforcedTenant, role, and row-level authorization controls are applied to client data and are designed to prevent unauthorized cross-client access.
Structured consent and list-provenance evidence
PlannedA structured, server-side record of list source, consent method, consent language, and channel authorization per record.
Pre-launch client compliance certification
PlannedA required, versioned certification by an authorized client user before a campaign may launch or resume.
Compliance evidence export
PlannedSelf-service export of suppression, certification, and campaign audit evidence for a defined period.
SMS program and opt-out handling
Not availableStrivePoint does not currently operate client SMS campaigns through the platform.
Client responsibilities
- Collecting records lawfully and holding the right to use them for outreach.
- Obtaining and documenting whatever contact permission applies to the channel used.
- Knowing and recording where each list came from and when it was acquired.
- Identifying the correct seller on whose behalf a call is placed.
- Setting campaign instructions, hours, caps, scripts, offers, and claims.
- Holding any registration or license their activity requires.
- Having their own counsel review their program.
- Responding to complaints and preserving evidence.
StrivePoint responsibilities
- Operating the documented technical safeguards described above.
- Applying the suppression a client has configured, on first attempts and on retries.
- Maintaining tenant, role, and row-level access controls over data in our custody.
- Keeping operational and audit records of platform activity.
- Processing data on documented client instructions.
- Acting on misuse we become aware of, including suspension.
Shared responsibilities
- Verifying that a campaign's configuration matches the client's intent.
- Preserving evidence when a complaint, demand, or legal hold arises.
- Handling complaints and investigations.
- Change control when a script, seller, list source, or channel changes.
- Periodic review of controls and settings.
What we do not say
We do not describe the platform as fully compliant with any statute, we do not promise that using it prevents claims or litigation, and we do not represent that our records will be accepted as sufficient evidence in any proceeding. StrivePoint is not a law firm and does not provide legal advice.
These operational safeguards do not constitute legal advice or guarantee that a campaign complies with every applicable law.
Contact
Compliance questions, complaints, and evidence requests: management@strivepointsolutions.com.
Effective July 29, 2026 · Last updated July 29, 2026 · Version 2026-07-29.1