Support

Keep install, rollout, and listing support in one narrow lane.

The support surface exists to help a careful buyer or operator install Native Intake, understand the launch-state trust boundary, and pull the current marketplace-facing assets without chasing internal project notes.

Start with one repeatable internal process and one clear owner.
Use the install guide before expanding rollout expectations.
Use the trust docs to keep public and operator claims aligned.

Book a guided demo See the product flow

Support posture

Keep rollout support smaller than the ambition.

Native Intake support should help the buyer or operator prove one governed internal workflow cleanly. The point is to reduce ambiguity around install, configuration, and proof boundaries, not to widen the launch story into an unsupported platform promise.

Free: documentation-first support for one admin, one portal, and one pilot workflow.
Growth: standard support once one SMB team needs several governed intake paths in one portal.
Pro: priority triage and guided rollout support for lower mid-market, agency-managed, or higher-support rollout.

When a rollout question starts expanding beyond one pilot workflow, move the conversation back to scope, owner, and support burden before changing the public promise.

Manual review-host demo requests: email the team.

Support docs

Start with the right document for the question at hand.

These routes split install, proof boundary, and buyer-facing trust so support and growth can answer the next question without sending people back into project artifacts.

Install guide

Use the current install path and preflight checks

Review the setup sequence, the required admin decisions, and the rollout checks to complete before wider use.

Read install guide

Trust docs

Review the supportable proof boundary

Use the trust docs to understand supported placements, admin control, and which claims stay out of public-facing copy until validation closes.

Read trust docs

Trust page

Use the shorter buyer-facing trust narrative

The marketing trust page stays focused on scope clarity and rollout posture for evaluators who do not need the fuller operational doc set.

Review trust page

Package policy

Support the exact launch-package language.

Support, marketplace, and onboarding surfaces should use one shared definition set and one support-lane map so buyers do not hear a different commercial story after install.

Active intake

A published intake that can be used in the live portal

Count only published intakes that are available for real use in the installed HubSpot portal.

Submission

One successful intake submission counted at the portal level in a calendar month

Count successful submissions against the installed portal's monthly total rather than per user or per form draft.

Portal

One installed HubSpot account

Launch packaging assumes one subscription maps to one installed HubSpot portal by default.

Asset exports

Use the checked-in marketplace and social sources directly.

These asset links point to the current public-safe sources already served by the site. Use them to review, export, or hand off the marketplace-facing packaging without hunting through the repo.

Social preview

Site social card source

Use the checked-in social card source when the site or listing needs the current launch-safe product framing.

Primary social-preview source. Keep the runtime crop dominant and preserve the approved launch framing.

Open social-card.svg

Marketplace icon

Marketplace icon source

Use the approved icon source for HubSpot listing submission and export the marketplace-ready raster from this file.

Export a PNG at 800 x 800 for HubSpot submission. Do not add text or a wordmark.

Open marketplace icon SVG

Review board

Marketplace and social asset pack board

Use the review board to keep the screenshot order, caption intent, and supporting still-life usage aligned with the approved launch packaging system.

Use as the packaging reference for listing screenshots, icon export, and social preview updates.

Open asset-pack board

Asset preview

Review the first public gallery set in the same page family.

These previews make the marketplace pack reviewable on the live site itself, so board feedback can react to the actual public packaging instead of separate files passed around in isolation.

Marketplace screenshot showing Native Intake running inside a HubSpot record.

Gallery slot 1

Run in record

Lead with native placement so reviewers understand immediately that the product runs inside the HubSpot record.

Marketplace screenshot showing Native Intake configuration and outcome setup.

Gallery slot 2

Configure outcome

Follow with the settings proof that shows scope, outcome choice, and publish clarity.

Gallery slot 3

Install

Keep the install/start posture concrete and narrow so the public package stays operational rather than aspirational.