Appearance
Onboarding Intake Forms
Intake forms collect the information your team needs to do the work. The platform's intake system has two delivery flavors:
- Public intake links — pre-purchase / pre-account discovery forms.
- Magic-link post-purchase onboarding — guided onboarding right after a storefront purchase.
Both share the same form builder and the same response storage. The difference is how the client gets to the form.
Building a form template
Onboarding question sets live per service in Settings → Services → row → Edit → Onboarding Questions (owner/admin). When a client buys that service, this set drives their onboarding flow.
Field types you can add
- Short text — one-line free text
- Long text — paragraph free text
- Dropdown — single-select from a list of options
- Checkbox — single yes/no
- Multi-select — pick zero or more from a list of options
- File upload — attach one or more documents (PDF, image, etc.)
- Social links — structured collection of social URLs (Facebook, Instagram, LinkedIn, etc.)
- Date — date picker
Required vs. optional
Mark fields required to block submission until they're filled. Optional fields can be skipped.
Public intake links
Public intake links are generated from a service's Onboarding Questions configuration in Settings → Services.
- Each link has a unique token:
dashboard.localvisibilitylab.io/intake/<token>. - Anyone with the link can fill it out (no sign-in).
- Send via email, embed in a proposal, paste into Slack — wherever you talk to the prospect.
- On submit, a notification email goes to a configured agency address; the response appears in the Intake responses list.
You can generate multiple links for the same service (one per prospect, or one general-purpose). Each link's response is logged separately.
Magic-link post-purchase onboarding
When a client buys from your storefront:
- Stripe Checkout confirms.
- The platform creates a customer account behind the scenes.
- An onboarding form template is attached based on the service they bought (configured per service in the catalog).
- A magic-link email is sent: "Get started with [Service Name]".
- The client clicks → signs in automatically → lands in the onboarding form.
- As they progress, the form auto-saves.
- On final submit, a case is opened for your team with all responses attached.
This flow is the default for storefront sales. You can disable it per service if you'd rather handle onboarding manually.
Where responses live
- Per case — if the intake was tied to a purchase, the response appears in the case's Documents tab.
- Per business — even if not tied to a case, responses are linked to the business.
- Per template — under Intake Forms → Template → Responses you see every submission for that template, exportable as CSV.
Document scoping
Onboarding documents (files uploaded during intake) are scoped per-profile. If a business has multiple profiles, the platform attributes each onboarding's docs to the profile(s) the case is linked to. This prevents cross-location leaks.
For ambiguous cases (legacy data, multi-profile businesses without per-case linkage), the platform falls back to a fail-closed rule: docs are only visible if the business has exactly one active profile.
Response review
When a response comes in:
- Notification email + dashboard activity feed entry.
- Open the response — you see all answers in a clean read view.
- Uploaded files are linked inline.
On the roadmap
AI-generated response summaries (a one-paragraph synthesis at the top of each intake), self-serve Re-open for editing with versioned response history, and form-level analytics (conversion rate, drop-off by step, completion time) are all on the roadmap (see Roadmap under Feature Reference). Today, follow-up clarification is done via the case's message thread or a fresh intake link sent from the contact's record.