A client intake form often tries to do three jobs at once: capture an enquiry, qualify an opportunity and collect everything needed for delivery. The result can feel like homework for someone who has not yet had a conversation with your team.
Separate those moments. Your first form should help the right person respond with context. A later questionnaire can gather the detailed assets, requirements and approvals needed to start the work. Use the questions below as a starting point, then remove any field you cannot explain.
The useful idea
Ask for information that changes your next action. Keep the first enquiry short enough to complete, and collect detailed delivery inputs after you understand the engagement.
Decide what will happen after submission
Choose the next action before designing the fields. Will an account lead arrange a discovery call, will a photographer assess a shoot enquiry, or will a consultant check whether the request fits their service? The form should collect enough information for that action.
Assign an owner for new submissions and define the confirmation message. Tell the client what happens next without promising a response time your team cannot consistently meet. A submitted form is the beginning of a conversation, not automatic acceptance of the work.
Ask for the need, context and timing
Start with a question the client can answer in their own words: ‘What are you hoping this work will change?’ Pair it with a simple service choice if that helps route the enquiry. Provide an ‘I’m not sure yet’ option when uncertainty is a normal part of the request.
Ask about timing in a way that reveals the reason for the date. ‘Is there an event or dependency driving your timing?’ is often more useful than a date alone. Avoid turning an initial preference into a promised delivery commitment.
| Question | Why it earns a place |
|---|---|
| What help are you looking for? | Routes the enquiry to the right person |
| What should be different afterwards? | Starts the outcome conversation |
| What is the context or current situation? | Helps the team prepare relevant questions |
| Is there a date or event we should know about? | Reveals timing and dependencies |
| How should we contact you? | Enables the requested follow-up |
Distinguish required information from useful detail
Require only what you need to process the enquiry. A business website, examples or a rough budget may help, but they are not always known or appropriate at this stage. Explain optional fields so people understand why you are asking.
Budget questions should suit your sales process and audience. If you use ranges, include a way to say the amount is not decided. Do not force a client to provide a made-up number that later looks like a confirmed requirement.
Use conditional questions sparingly
Different services need different context. A shoot enquiry may ask about location and intended image use; a software project may ask about the current system. Show those questions when relevant instead of asking everyone to fill every field.
Check the form with each route and with uncertain answers. If a person changes their service choice, make sure the final submission remains understandable and does not include contradictory hidden responses. Test the actual form tool’s behaviour rather than assuming every branching feature works the same way.
Make the form clear and proportionate
Use visible labels, concrete hints and plain language. Explain unfamiliar terms and avoid asking for account passwords, sensitive documents or access credentials in a general enquiry form. Provide another way to contact the team if the form is difficult to use.
Place the relevant privacy information where the client can find it. Describe the purpose of the submission accurately and keep any optional marketing choice separate from the enquiry. This is form design guidance; your actual privacy wording needs to reflect your operating policies.
Carry the answer into the next conversation
Review the response before contacting the client. Start from what they told you rather than asking the same questions again. Link the source response to the opportunity or client record so the context can travel into the brief if the work proceeds.
After a few real enquiries, review unanswered fields and responses that required clarification. Shorten questions that people misread and remove fields that never change the next action. Form quality is visible in the conversation it enables, not just in how polished the fields look.
First-enquiry questionnaire
Use these as question prompts, not a mandatory field list.
FIRST CLIENT ENQUIRY Your name and preferred contact: [contact] Business or project: [name] What help are you looking for? [service / not sure] What would you like this work to change? [outcome] What is happening today? [context] Is an event or dependency driving the timing? [detail / not sure] Anything useful for us to review first? [optional link] How would you prefer us to follow up? [preference] INTERNAL FOLLOW-UP Submission owner: [name] Next action and date: [action / date] Response linked to: [client or opportunity]
Bring the context into your workspace.
Explore how Tamaam connects the relationship and the work around it. Tamaam is in development; product pages show previews and illustrative workflows. Joining early access does not start a subscription.
Found something we should clarify? Send a correction or question.
