Skip to main content

Blackleaf Help Centre

Blackleaf Texting FAQ

This English (India) edition answers questions about Blackleaf Texting for regulated retailers. Blackleaf supports messaging programmes in the United States and Canada. The Pricing page lists US plans and rates in US dollars (USD).

Compliance information is general guidance and does not replace legal advice. Requirements vary by jurisdiction, sender, content and use case.

6 answers

integrations

Integrations and API

POS data, synchronization, matching, and API access.

Do I need to switch POS systems to use Blackleaf Texting?

Short answer No. You can keep your existing POS when it has a supported connection for your Texting workflow. Confirm which customer, order or loyalty data your setup can share and how often it updates.

What can an integration sync?

Short answer Depending on the connector, Blackleaf can receive customer, transaction, loyalty, order, product, and event data. Fields and timing vary by integration.

Is POS data synchronized in real time?

Short answer Not always. Timing depends on the connector, source, data type, and processing state. Use the integration’s documented cadence for time-sensitive rules.

Can an integration create duplicate contacts?

Short answer Blackleaf matches available identifiers, but missing, changed, shared, or inconsistent identifiers can produce separate records. Names alone are not unique.