← Back to use cases
Customer portals

Surveys and forms inside your customer portal

Example walkthrough: Harborline is a fictional product and all numbers are sample data.

Embed feedback surveys, intake forms, and check-ins in your customer portal, signed in through your portal and styled to match it.

Start freeView pricing
9:41●●● ▮
Hportal.harborline.example
Website redesign · Phase 2

How is the project going so far?

Secured by Harborline

The phone is live — tap through the Harborline survey.

Who it is for

Agencies, service providers, and B2B companies that run a customer or client portal.

Project check-insIntake formsPost-delivery feedbackRead-only result sharing

What you get

  • Feedback and intake in the portal customers already use
  • Answers linked to the signed-in customer
  • A portal that looks like one product

Questions it answers

Can customers answer without another login?Can we link answers to the account?Can we share results back?
Product walkthrough

From a question to an experience inside your product

ResponseDock supplies the survey engine. Your application keeps the relationship, context, and visual identity.

Start with project milestone check-in and combine choice, scale, text, consent, and logic-based questions. Structure, publishing, and versions live in one workspace.

Example product screens for the project milestone check-in workflow, with sample data.

How it fits together

What you connect and what you get

Your portal identifies the signed-in customer with a verified user ID, and the survey appears inline, in a modal, or on a hosted page under your theme. Your team can manage surveys and read results from an embedded workspace, and you can choose to share a read-only results view.

  1. 01

    What your app sends

    • Verified customer ID
    • Account or project ID
    • Theme file
  2. 02

    What you get

    • Inline, modal, or hosted forms
    • Answers linked to the customer
    • Embedded results for your team
    • Optional read-only results view
  3. 03

    Good practice

    • Turn on identity verification so answers cannot be spoofed
    • Ask at project milestones, not on a timer
    • Share results back when customers would value them
Your product, powered by ResponseDock

A survey engine, not another disconnected destination

Keep users inside your application while ResponseDock handles survey building, response collection, permissions, publishing, and results behind the scenes.

  • Theme filesColors, typography, logo, radius, buttons, options, width, and shadows.
  • Flexible surfacesInline embeds, modals, hosted surveys, and embedded management views.
  • Context-awareLink responses to the signed-in user, account, plan, or product event.
  • Controlled resultsKeep results private or expose a read-only public results experience.
product-feedback.ts
import { ResponseDock } from '@responsedock/sdk-browser';
import theme from './responsedock-theme.json';

ResponseDock.init({
  projectKey: 'pk_live_your_project',
  theme,
});

ResponseDock.identify({
  externalUserId: currentUser.id,
  traits: { plan: currentUser.plan },
});

ResponseDock.embed(
  'customer-portals',
  '#survey-container',
);