What to know before you get started

Reach2Sell is a customer marketing and automation platform for independent commerce businesses. It brings authorized store data, customer segments, email and SMS content, automated journeys, delivery records, and analytics into one workspace.

Start from a supported app marketplace or the Store Integrations page in Reach2Sell. After granting platform access, sign in to or create a Reach2Sell account, then confirm the connection under Settings > Store Integrations. The service only accesses the permissions listed on the authorization screen.

• Use a store administrator account to grant access.
• Never send store passwords, access tokens, or other secrets through chat or email.

The scope depends on the permissions you grant and the integration you enable. It generally includes customers, orders, products, checkout and fulfillment status, and store events used to update customer profiles and trigger automation.

• The authorization screen, console status, and Privacy Policy define the actual scope.
• Installing the app does not grant access to data outside the approved permissions.

Sync time depends on store data volume and platform API availability. Check the status under Settings > Store Integrations. Until synchronization is complete, customer counts and analytics should not be treated as final.

• If progress appears stuck, contact support with the store domain, start time, and displayed status.

The production workspace currently supports email and international SMS marketing, including templates, one-time campaigns, automated journeys, and delivery results. Availability can vary by plan, business verification, region, and channel configuration.

• Rely on the channels currently visible and usable in your console.

First confirm that each recipient has the required marketing subscription or another valid legal basis. Build a customer segment, prepare a published email or SMS template, then create a one-time campaign or compose a journey with event triggers, conditions, delays, and send nodes.

• Before sending, review the audience, content, variables, schedule, and unsubscribe method.
• After sending, use delivery records to review acceptance, delivery, failure, and related reasons.

The service uses email and SMS subscription states and suppression records maintained by the merchant or provided by an integrated platform to restrict sending. Customers who are unsubscribed, suppressed, or missing valid contact details should not receive marketing.

• The merchant remains responsible for any notice, consent, or other legal basis required by applicable law.
• Store events or past orders do not automatically prove consent to marketing.

When enabled by the merchant, Reach2Sell may record email opens, link clicks, timestamps, IP addresses, and device details to report campaign performance. Merchants should disclose this tracking in their customer-facing privacy notice and obtain consent where required.

Uninstalling ends the ongoing connection for that store. For a valid customer or store deletion request, we verify the request and normally delete or de-identify the relevant personal information within 30 days. Limited records required by law are restricted in use and access.

• Some platforms send a store deletion request about 48 hours after uninstall.
• Residual backup copies are removed through backup rotation and disaster-recovery procedures.

A merchant customer should normally contact the merchant they purchased from first. Merchants can forward a request through an integrated platform privacy workflow or email support with the store domain, integration, and request type. We verify identity, authority, and scope before acting.

• Do not include passwords, access tokens, or full payment-card details in ordinary email.

Plan features, price, billing cycle, and renewal information are shown before purchase. Plans ordered through a third-party app marketplace should first be viewed or managed in that marketplace. To request cancellation or a refund, email support with the store domain, plan or transaction details, and the reason.

• Eligibility, process, and timing depend on the terms shown at purchase, the purchase-channel rules, and applicable law.
• Submitting a refund request does not mean that a refund has been approved.

The support mailbox accepts requests 24 hours a day, 7 days a week. Include the account email, store domain, incident time, reproduction steps, and screenshots without sensitive credentials. Mark data-rights or security requests clearly in the subject.

• Installation, billing, data-rights, and security requests are prioritized.