Skip to content
MESSAGING OPERATIONS · CLIENT Fine Touch Marketing

Multi-Site Follow-up

Multi-site lead routing with complete booking confirmations, provider-acceptance checks and consent-aware follow-ups.

Illustration of Multi-Site Follow-up: a booking form routed through n8n, Sheets and Twilio to a booking-summary text with tracked outcomes
ILLUSTRATION
CURRENT SCOPE

Client automation · October 20 booking-confirmation release live

WHO IT'S FOR

Client project · Fine Touch Marketing

Paid agency engineering for multi-site lead follow-up. October repair records distinguish provider acceptance, actual delivery and consent.

THE ENGINEERING

Client automation connecting JotForm, n8n, Google Sheets and Twilio for site-specific lead intake, welcome messages and scheduled follow-ups across nine active routes. The October 20 release gives one client site a complete booking confirmation (service, contact details, appointment time, timezone and consent choices) in warmer wording, sent identically to the customer and the business. The other eight routes keep their behavior, and all three deployed workflows matched local source. An earlier controlled booking test reached provider status delivered for both messages; the revised wording was checked offline without paid sends. Twelve site-specific follow-ups are prepared but switched off pending cost confirmation. October 11 repairs require matched provider acceptance before marking a message sent and suppress marketing after an explicit opt-out. Blank or unknown marketing consent is not yet rejected, so this is not a general fail-closed consent guarantee.

n8nTwilioConfiguration

BEFORE → AFTER

Real problems from this build, what I changed and the verified result.

  1. CASE 01
    Before

    Booking welcome texts showed only name, date and time, and consent choices appeared as raw TRUE/FALSE values.

    After

    Customer and business copies match, eight other routes were preserved and live workflows matched local source. Live delivery of the revised wording is not yet verified.

    How I fixed it

    Rendered the full booking summary for one site from configuration, with Yes/No labels over the original stored flags, limited by form routing.

  2. CASE 02
    Before

    A rejected or ambiguous provider response can incorrectly mark a contact as sent.

    After

    October 11 behavioral evidence verifies accepted updates and loop continuation without a paid send; acceptance does not establish delivery.

    How I fixed it

    Required valid matched provider acceptance, preserved stage markers and refused ambiguous item linkage.

  3. CASE 03
    Before

    An opted-out contact can remain eligible for later campaign stages.

    After

    The current source and retained regressions distinguish accepted, opted-out, failed and unpaired outcomes.

    How I fixed it

    Revoked marketing consent on explicit opt-out while preserving prior sent history and site isolation.

Evidence reviewed: Google Doc release note reviewed October 25, 2026; verification dates and open gates stated above