Skip to content
Start with enquiries. Explore quotation drafts.
procora.
DAFind your solution

Marketing & Repeat Business

Prepare the source, owner and controls before connecting a campaign.

Review customer history, bookings, evidence, sender setup and duplicate-contact controls for a clearly scoped planned marketing workflow.

Planned serviceRepeat Business and Reviews & Referrals are planned. These pages describe proposed work; no campaign channel or paid marketing service is activated.

Discuss this serviceExplore the example
Procora · Workflow example

Contact preferences take priority

CountryBelgium
PurposePromotional rebooking
ChannelEmail · check evidence
Unknown permissionBlocks contact
New opt-outCancels future promotion

Language, country and permission are separate fields.

Fictional example · localised website visual

The work, in practice

Useful customer history may already exist in several systems, but a connection is only valuable if the required fields and decisions are reliable. The planned Procora marketing scope starts with that review. Naming a CRM, booking tool or provider on a page does not establish an operational integration.

01 · Marketing & Repeat Business

Separate current tools from the proposed marketing job

Existing Procora tools handle customer-requested enquiries, configured bookings and owner notifications. Certain connectors push a captured lead or appointment into a configured system. Those functions have their own prerequisites and direction; they do not prove that Procora reads full purchase history, maintains campaign preferences or synchronises repeat-business results.

The current catalogue keeps Repeat Business and Reviews & Referrals planned, unavailable and unpriced, with no enabled campaign channel. Database contact and suppression foundations are not a complete dispatcher. Begin by choosing a proposed job and the exact source information it would require rather than assuming that an integration-directory entry activates a campaign.

02 · Marketing & Repeat Business

Define the source contract for customer history

A proposed source record should include a stable customer reference, relevant completed service or purchase, date, business location, status and update information. Specify which system owns each field and what corrections mean. An illustrative Belgian retailer may use its existing business software; this example does not claim a Procora connection to that software or one standard system for Europe.

Review read and write directions separately. Sending a captured contact into a CRM is not the same as reading historical services back from it. A future history scope needs field mapping, access permissions, freshness checks and failure handling. Start with a small sanitised sample; do not provide passwords or an entire private customer file through the public enquiry.

03 · Marketing & Repeat Business

Check current bookings and completed interactions

The Spanish appointment example needs the actual service, confirmed status, relevant location and business timezone. A calendar showing a occupied time does not necessarily identify which customer need is covered. Cancelled, rescheduled and completed events must be distinguishable so the proposed process does not invite someone who already has a suitable visit.

If the source goes offline or contradicts the history record, pause the affected work and give a person the references. Agree how a booking change would reach the proposed contact process and how quickly it must be checked. This public example cannot create a booking, reserve staff capacity or verify a live customer's attendance.

04 · Marketing & Repeat Business

Bring preferences and suppression from their real sources

A history import needs a separate source for the intended contact evidence, relevant preferences and stops. An address labelled subscribed is not enough to explain what the person chose. Preserve the source, purpose and channel, and decide how conflicting values are resolved. A later opt-out must affect pending promotional work rather than wait for another import.

Define who can correct a record and how the decision is documented. Imported duplicates should not undo a stop by creating a second identity. Existing suppression storage can support an agreed control, but no complete market/channel preference synchronisation is claimed. The owner remains responsible for reviewing the applicable basis and proposed workflow before operational use.

05 · Marketing & Repeat Business

Review sending and replies as a separate prerequisite

Any future customer campaign would need an approved sender, suitable authentication, provider limits, a working reply destination and a verified stop route. Existing email or SMS notifications to the business owner do not establish that setup. A provider account or SMTP field also does not grant permission to contact the selected audience.

Agree the provider dependency and cost before activation, including who handles failures and uncertain delivery. Avoid enabling a new channel simply because a message template exists. The website release does not buy provider services or alter commercial subscriptions. All public demonstrations remain local, with no provider call or real outbound message.

06 · Marketing & Repeat Business

Prevent duplicate contact from existing systems

Ask which CRM, booking, newsletter or service system already contacts the same customer and for what purpose. A proposed new workflow should have explicit priority, shared limits and exits. A review invitation in one product and an identical invitation in another are still duplicate work, even if each local job appears eligible.

Test booking after selection, changed offer, human takeover, new suppression, duplicate identity and missing source access. Verify that the appropriate pending steps stop and that an owner receives unresolved work. Tests should use fictional records and isolated conditions, not a production list. A successful import alone is not acceptance of the complete customer journey.

07 · Marketing & Repeat Business

Agree responsibilities and a small initial scope

Name the owner of source quality, commercial wording, contact evidence, replies, provider issues and results. Review the support actually needed rather than promising a dedicated retention team or response guarantee. A useful initial discussion identifies one job, countries, languages, approximate volume, present systems and the main exception that currently causes manual work.

The service enquiry stores that scope request in the protected intake, shows a reference and creates a review task; it is not an invitation to share confidential contact records. Marketing consent remains separate. No standalone price or chatbot-plan inclusion is invented. A future pilot and sending activation require their own verified prerequisites and agreement while the public service remains planned.

Useful resources

Bring the work into your own process.

Original templates, checklists and measurement guides. Read them online, copy what you need or download a text version.

Marketing & Repeat Business · Practical guide

Plan one useful repeat-business campaign before considering contact.

A practical planner for purpose, source records, eligibility, exclusions, owner approval, exceptions and meaningful results.

Read, download and use
Marketing & Repeat Business · Practical guide

Write a reactivation message with a useful reason to reply.

Practical message patterns for a relevant service invitation, appointment return, human reply and respectful closure, with eligibility and approval checks.

Read, download and use
Marketing & Repeat Business · Practical guide

Ask for honest feedback and let customers share a link voluntarily.

A practical review and referral policy with neutral invitation examples, complaint handoffs, voluntary link sharing and a local checklist.

Read, download and use

Explore related work

Build an audience you can explain, including who is left out. →Respect the contact basis and the customer's latest choice. →Plan one useful repeat-business campaign before considering contact. →

Questions worth answering

Does a CRM connection mean customer history is synchronised?

No. Check the actual field coverage and direction. A lead/contact push can work without any service-history read, preference update or campaign-result connection. Those require separately verified scope.

Can I use my current provider account immediately?

This page does not enable it. A future campaign needs sender/reply setup, suitable controls, reviewed costs and contact eligibility. Owning a provider account does not establish audience permission.

What should I include in the service enquiry?

Describe the job, countries, main systems, approximate workload and current difficulty. Do not include credentials, private lists or sensitive customer documents. The saved enquiry starts scope review and changes no subscriptions.

A connected business journey

One next step leads to another.

  1. 01Enquiry & appointment ↗
  2. 02Quotation & decision ↗
  3. 03Accepted work & invoice ↗
  4. 04Appropriate next interaction ↗

This map explains how the work relates. Scope, ownership and availability are agreed at each hand-off; it does not mean every transition is automatic.

Selected service: Repeat-Business Follow-up

Your next step

Tell us where the work gets stuck.

Describe the process you want to improve. We will save the enquiry for a scope review, confirm what is available and agree the next step with you.

Please keep customer records, financial documents and passwords out of this form. Submitting it does not activate a subscription, campaign, booking or customer-contact workflow. Marketing permission is separate.

Privacy policy (Danish) ↗