Fidelity Bank — Turning a bank's web forms into a routing system nobody has to code | Engage Evolution Skip to content
Engage Evolution
← Case studies
Fidelity Bank Banking Salesforce Marketing Cloud

Turning a bank's web forms into a routing system nobody has to code

Replaced per-form CloudPage builds with a single data-driven form that routes leads and opportunities from a data extension row.

  • CloudPages and AMPscript
  • SFMC to Salesforce lead routing
  • Deliverability remediation
  • Audience strategy

The situation

Fidelity Bank runs its marketing on Salesforce Marketing Cloud, with inquiries from the website feeding Salesforce as Leads and Opportunities. Every new product inquiry form meant another CloudPage build — new markup, new AMPscript, new routing logic, new owner assignment. Each one was a small development project, which meant each one waited in a queue.

Alongside that, two older problems were quietly costing them reach: a backlog of held emails, and a large segment of contacts who had stopped engaging years earlier and were still being mailed.

What we did

One form, driven by data. Rather than building a CloudPage per product, we built a single generic inquiry page that reads a f parameter from the URL and looks up a matching row in a EE_Form_Routing data extension. Everything that used to be hard-coded now lives in that row: the heading and intro copy, the product type and product line written back to Salesforce, the record types, the routing owner, lead priority, whether a known customer should generate an Opportunity instead of a Lead, the task subject prefix, the confirmation copy, the contact name and phone numbers, and the scheduling link.

The practical effect is that adding a product form is now a spreadsheet row, not a code change. Marketing can stand up a new inquiry form without waiting on a developer.

A detail worth mentioning, because it is the kind of thing that decides whether a system stays maintainable: phone numbers are stored twice in the routing table, once in display format and once as a bare dial string. Deriving one from the other in AMPscript takes four nested Replace() calls, which is fragile and unreadable. Two columns is the cheaper answer.

Held emails and audience hygiene. We worked through the held-email backlog and rebuilt the re-engagement path for inactive contacts rather than simply flushing the queue, and set up evergreen audience definitions so segmentation stopped being rebuilt by hand for each campaign.

Where it landed

The routing data extension and submissions table are live in Marketing Cloud, seeded with the bank’s three priority forms, with copy taken from the live product pages. Values the bank still needed to supply were seeded as TBD- placeholders so an incomplete import fails loudly rather than silently publishing a half-configured form.

Something similar on your side?

Thirty minutes, no deck. Tell me what's going on and I'll give you a straight read on it.

Book a working session