Testimonials Pipeline & CRM Enrichment

The Problem vs. The Outcome

Before

Testimonials collected via Typeform but never organized
No one consistently checking the Typeform dashboard
Contacts who left testimonials never added to the CRM
No automated follow-up or thank-you process
Team had no visibility into new submissions

After

Every submission instantly logged in a structured Notion database
Contacts automatically created or updated in the main CRM
Branded thank-you email sent via Notion Sender on every submission
Internal Notion comment posted for team review and approval
Full testimonials library — searchable, categorized, always current

How It Was Built

Step 1

Audit & Map

Reviewed the Typeform structure, identified all fields, and mapped how each piece of data should land in Notion and the CRM.

Step 2

Testimonials Database Setup

Built a dedicated Notion Testimonials database with fields for quote, program, city, submitter details, and approval status.

Step 3

CRM Cross-Reference Logic

Designed the Zapier logic to check whether the contact already exists in the CRM — update if yes, create if no.

Step 4

Parallel Action Triggers

Configured two simultaneous actions per submission: the Notion Sender thank-you email to the participant, and the internal Notion comment flagging the entry for team review.

Step 5

Approval Workflow

Set every new testimonial record to "Pending Review" by default, giving the team a clear queue to work from inside Notion.

Step 6

Test & Handoff

Ran multiple test submissions, verified database entries, CRM updates, email delivery, and internal notifications before going live.

Project Timeline

Day 1: Typeform audit and data mapping

Field inventory and Notion/CRM mapping.

Day 2–3: Notion Testimonials database setup

Schema and approval status fields.

Day 4–5: CRM cross-reference logic build in Zapier

Create-or-update contact logic.

Day 6–7: Parallel action triggers — email and internal notification

Notion Sender and Notion comments.

Day 8: Approval status and review queue configuration

Pending Review default and team workflow.

Day 9–10: End-to-end testing and client handoff documentation

Validation and handoff.

Full Breakdown

The Problem

The client had a Typeform embedded on their website specifically for collecting testimonials, and people were filling it out regularly. But without any automation behind it, each submission just sat in a Typeform dashboard that no one was checking consistently. Testimonials weren't being organized, contacts weren't being logged in the CRM, and the team had no reliable way to know when a new submission had come in.

The Approach

I treated this as a three-part problem: capture and organize the testimonial, enrich the CRM with the contact, and trigger the right internal and external actions automatically — all without any manual steps in between.

The Build

The workflow started with a Zap that fired the moment a Typeform submission came in, creating a structured record in a dedicated Notion Testimonials database — automatically categorized by program and city, with approval status set to "Pending Review" by default. Simultaneously, the automation cross-referenced the main CRM: if the contact existed, their record was updated with a "Testimonial Submitted" tag; if not, a new contact was created. Two parallel actions then fired without any manual trigger — a warm thank-you email through Notion Sender to the participant, and an internal Notion comment on the record flagging it for team review.

The Result

The client went from a disorganized Typeform inbox to a fully structured, searchable testimonials library — with a consistently enriched CRM, reliable participant follow-up, and a clear internal review process. All of it running automatically from the moment someone hits submit.