Enterprise forms for Salesforce teams
Forms that look better upfront
and behave correctly downstream.
OK Forms is the capture layer for Salesforce teams that need cleaner user experience, controlled transport, and response data that can go straight back into operational systems.
Build richer form flows from a cleaner block system with fewer overlaps and broader coverage.
Structured capture, card-based selection, research methods, and utility logic now live in consolidated block families with Salesforce-safe mapping built in.
Included
Structured capture
Contact, address, scheduling, numeric ranges, availability, and location capture.
Choice systems
List, image, card, ranking, and best / worst flows from a cleaner choice family.
Scales & research
NPS, semantic differential, matrix, allocation, and open numeric grids.
Content, logic & data
Statement variants, hidden payloads, qualification gates, consent, and calculations.
Core families
Preset starting points
Compatibility
Built around the Salesforce-side objects and delivery behaviors campaign workflows already depend on.
One platform for capture,
governance, and activation.
Capture richer answers, govern how context moves, and return outputs your team can use immediately.
Lead Capture Form
98%
Single-question steps with keyboard navigation and mobile-first completion flows.
Survey Builder
85%
Image choices, conditional logic, and conversational UX that users appreciate.
Contact Form
92%
Brand-first design with headers, footers, and visual customization.
Capture
Guide people through richer questions, visual choices, and step-based form flows.
Response Tracker
Form Opened
0s
First Question
3s
Email Captured
12s
All Fields Complete
28s
Submitting to SFMC
...
Govern
Keep context handoff, response tracking, and transport behavior inside controlled rules.
Activate
Return mapped outputs to Salesforce structures, journeys, and downstream campaign logic.
Team Fit
Made for the teams that own the data after submit.
OK Forms fits best where the form is only the first step and downstream systems still need the response to arrive cleanly.
CRM teams
Downstream owner
Use governed forms to enrich customer records without handing transport logic to every campaign build.
Lifecycle marketing
Downstream owner
Capture preferences and follow-up signals in forms that can feed journeys and audience updates immediately.
Campaign operations
Downstream owner
Duplicate, brand, and launch form variants quickly without turning every campaign into a custom project.
Customer insight teams
Downstream owner
Collect richer feedback and compare engagement, drop-off, and response quality across programs.
Flow
A clear path from audience context to Salesforce-ready data.
This is the movement layer: where context starts, how forms collect it, and where the output goes after submit.
Audience context
Data Extensions
Automations
data collected
Salesforce-native flow
Audience context enters first, responses are collected in OK Forms, and the output leaves in a mapped structure.
Secure prefill patterns
Signed context resolves cleanly server-side and stays constrained to the fields the form should receive.
Global edge delivery
Forms served from edge locations worldwide for fast, reliable response collection.
Salesforce activation outputs
After submit, one response can feed Data Extensions, journeys, audience updates, and follow-up logic.
Salesforce
Map responses into Marketing Cloud without rebuilding the delivery model each time.
Connection settings stay centralized. Each form controls mapping, metadata, and insert or upsert behavior at the point of delivery.
Delivery model
Map the response once. Deliver it with the operational behavior you need.
Per-form SFMC controls
Enable or disable delivery by form, isolate mappings, and keep business-unit level connection settings centralized.
Field mapping to Data Extensions
Map form answers and metadata into target Data Extension attributes with exact control over what lands where.
Insert and upsert modes
Choose whether forms create new records or update existing ones based on your operational schema.
Metadata that can travel with the response
Insert mode
New row per response
Use when submissions should remain independent and historically traceable.
Upsert mode
Update based on a key
Use when the form should enrich or correct an existing customer record.
Comparison
Built for teams that need more than a generic submit button.
The difference is not only visual. The product is designed for governed transport, Salesforce writeback, and operational reuse after launch.
Capture experience
Salesforce delivery
Context handoff
Response behavior
Operational scale
Operations
Operational features that make the platform usable at team scale.
The product also has to work for marketers and operators who manage many active forms at once, not only for the person building a single flow.
Form organization
Use folders and structured lists to manage larger sets of forms without losing operational clarity.
5x
Faster setup
100+
Forms managed
Team
Ready
Reuse and duplication
Duplicate forms quickly to create campaign variants without rebuilding from scratch.
Brand governance
Keep headers, footers, widths, and surface styling consistent across live campaign variants.
Centralized configuration
Keep integration settings and delivery controls manageable across campaigns.
Built for scale
The platform stays manageable after the fifth form, not only the first one.
Use Cases
A product story grounded in real use cases.
Use cases make the value concrete: better segmentation, richer profiles, more usable feedback, and faster follow-up.
Preference capture
Collect declared preferences in a lower-friction flow and turn them into segmentation data teams can use immediately.
Enrichment flows
Fill profile gaps without sending people through a generic data-capture experience that feels disconnected from the campaign.
Survey programs
Run survey programs that generate more usable feedback and clearer performance signals than flat embedded forms.
Triggered follow-up journeys
Turn form submissions into follow-ups, audience updates, and downstream actions without rebuilding the activation layer each time.
Architecture
A delivery model technical teams can understand and trust.
Source context enters with rules already defined, OK Forms governs the intake layer, and Salesforce receives a mapped payload ready for action.
Source context
Audience, Data Extension, and automation inputs define what the form should know before the first step renders.
Secure intake layer
OK Forms receives the response, applies controlled metadata, and keeps transport logic in one governed runtime.
Salesforce writeback
The final payload returns to Marketing Cloud with the write behavior and downstream routing already defined.
FAQ
Questions teams usually ask before they adopt the workflow.
The important questions tend to be about transport, Salesforce behavior, partial responses, and operational control.
Get started
Build your first Salesforce-ready form.
Collect richer answers, govern transport, and return mapped outputs without rebuilding the workflow for every campaign.