Explain the process. Collect what you need.

Create a customer intake form from Confluence

Use Confluence content to explain your onboarding or implementation process, then collect the customer details your team needs from the same external page.

Join early access Explore intake use cases

Keep your guidance in Confluence and collect structured customer information without giving access to your workspace.

Customer intake is more than a list of questions

Before a customer can complete an onboarding or implementation form, they often need to understand the process, gather information, speak to colleagues, and make decisions.

Confluence may already contain the instructions, definitions, examples, technical requirements, and preparation guidance. But the customer is often sent to a separate form with little context.

A customer intake form published alongside the Confluence content would let customers understand what is required and submit the right information from one place.

What is a Confluence customer intake form?

A structured customer form supported by guidance managed in Confluence

Your team creates and maintains the onboarding or implementation guidance in Confluence. The selected content is published as a customer-facing website page, with an intake form placed alongside it.

Customers can review the instructions, understand why each piece of information is required, and submit a more complete response without needing a Confluence account.

A simpler intake journey

Understand the process

The customer reads the onboarding or implementation guidance published from Confluence.

Gather the information

They use the guidance to prepare answers, identify stakeholders, and collect the required details.

Submit a structured response

Your team receives the customer information needed to plan the next step.

Why customer intake becomes fragmented

The instructions, questions, documents, and customer answers often end up spread across several different tools.

Email the customer a document

Documents are easy to send, but responses become inconsistent and multiple versions may circulate between teams.

Send guidance and a separate form

Customers must move between the instructions and the questions, increasing the chance that important context is missed.

Invite the customer into Confluence

This can create unnecessary account administration and expose customers to a workspace experience they do not need.

Publish the guidance and intake form together

Keep the source content in Confluence while giving customers one clear place to understand and complete the request.

What can a Confluence customer intake form support?

Use the published page to explain the process and collect the information needed to move work forward.

Customer onboarding

Collect contact details, business information, goals, stakeholders, dates, and onboarding preferences.

Software implementation

Gather technical requirements, integrations, environments, security constraints, and deployment information.

Project discovery

Ask customers about the current process, problem, desired outcome, scope, risks, and success measures.

Professional services

Collect the information needed to scope consulting, migration, configuration, or delivery work.

Migration planning

Capture source systems, content volumes, formats, ownership, dependencies, and target deadlines.

Customer change requests

Explain the change process and collect the business reason, requirements, urgency, and impact.

Structured customer information

What information could an intake form collect?

The published Confluence content can explain each section so customers understand what is required and why.

Customer and company details

Organisation name, customer contacts, locations, departments, and account information.

Goals and outcomes

The problem being solved, desired outcomes, priorities, and measures of success.

Stakeholders and ownership

Sponsors, decision-makers, technical contacts, administrators, and day-to-day owners.

Technical requirements

Systems, integrations, environments, authentication, security, and infrastructure details.

Timescales and milestones

Target dates, dependencies, availability, review points, and important deadlines.

Risks and constraints

Known blockers, compliance requirements, resource limits, dependencies, and areas of uncertainty.

How a customer intake page could work

Keep the onboarding guidance in Confluence and turn the selected page into a structured external intake experience.

Step 1

Write the guidance

Explain the process, responsibilities, definitions, requirements, and next steps in Confluence.

Step 2

Publish the intake page

Turn the selected content into a clean external page for the customer.

Step 3

Add the intake questions

Ask for the information your team needs to plan onboarding, implementation, or delivery.

Step 4

Review the response

Receive a structured submission that your team can review before the next customer meeting.

Why combine Confluence guidance with customer intake?

Receive better answers

Give customers the context and examples they need before asking them to submit information.

Reduce follow-up questions

Clarify terminology and requirements before the customer completes the form.

Standardise intake

Ask every customer a consistent set of questions while still providing detailed guidance.

Keep the guidance current

Update the instructions in Confluence rather than maintaining another copy in a separate intake tool.

Protect the workspace

Give customers access to the selected page and form without exposing internal Confluence content.

Prepare before meetings

Review the response in advance so customer sessions can focus on decisions rather than basic information gathering.

The Satori Cloud approach

Turn Confluence onboarding content into a customer intake experience

Satori Cloud is being built to publish selected Confluence pages as external websites. Customer intake forms would let those pages collect structured information without sending customers into your internal workspace.

Explore other Confluence form use cases

Customer intake is one way to make externally published Confluence content interactive.

External submissions

External Confluence forms

Collect structured responses from customers, prospects, partners, and suppliers.

Explore external forms

Reader feedback

Confluence feedback forms

Let customers rate documentation, report problems, and explain what information is missing.

Explore feedback forms

Security and compliance

Security document request forms

Let prospects request security documents, compliance evidence, and restricted resources.

Explore security forms

View the complete Confluence forms guide

Questions about Confluence customer intake forms

Can I create a customer intake form in Confluence?

Confluence apps can support internal form workflows. Satori Cloud is exploring customer intake forms attached to externally published Confluence pages, without requiring customers to access your workspace.

Can customers complete the form without a Confluence account?

That is the intended experience. Customers would view the published intake page and submit their answers without logging in to Confluence.

What should a customer intake form ask?

Common sections include contact details, goals, stakeholders, technical requirements, timescales, dependencies, risks, and measures of success.

Why not use a separate form builder?

A separate form can collect answers, but it may separate the questions from the detailed guidance customers need to answer them correctly.

Does the intake page expose internal Confluence content?

No. The goal is to publish only the selected guidance and intake form while keeping the rest of the Confluence workspace private.

Is this available in Satori Cloud now?

Satori Cloud is currently validating demand and shaping its first version. Join early access if customer intake forms would be useful to your team.

Related Confluence publishing guides

Explore more ways to publish selected Confluence content as clean public pages.

Want customers to give you the right information before onboarding begins?

Join early access and help shape a simpler way to publish onboarding guidance from Confluence and collect structured customer responses.

Join early access