## The Short Answer The best pre-meeting questions are specific, short, and tied to the type of meeting. They should help the host prepare, help the guest clarify what they need, and remove basic discovery from the first few minutes of the call. You do not need many questions. In most cases, two or three are enough. The trick is choosing questions that change the meeting. ## How to Use This List Do not copy all 25 questions into one booking page. That would create a terrible guest experience. Instead, choose a meeting type, pick the two or three questions that matter most, and attach them to that flow. For example, a product demo needs different questions from a coaching session. A support call needs different questions from a partnership conversation. The more specific the question is to the reason, the better the answer will be. ## Product Demo Questions 1. What problem are you trying to solve right now? 2. What are you using today? 3. How many people would use this workflow? 4. What made you start looking for a new solution? 5. What would make this demo useful for you? These questions help the host avoid a generic tour. They reveal the current workflow, the motivation, and the likely buying context. ## Consulting Questions 6. What would you like to make progress on during the session? 7. What have you already tried? 8. Where are you feeling stuck? 9. Is there any background material I should review? 10. What would a successful session look like? Consulting calls can easily become broad. These questions create focus before the clock starts. ## Recruiting Questions 11. Which role or opportunity are you interested in? 12. What is most important to you in your next role? 13. Are there any scheduling constraints we should know about? 14. Which part of your background should we spend the most time on? 15. Do you have questions you want to make sure we cover? Recruiting is partly about evaluation and partly about candidate experience. Clear questions help both sides prepare without making the process feel cold. ## Support and Technical Questions 16. What issue are you trying to resolve? 17. What steps have you already taken? 18. When did the issue first appear? 19. Which tools, accounts, or integrations are involved? 20. Can you share a link, screenshot, or recording? Support meetings should not spend the first half collecting details that could have been shared earlier. These questions move the meeting closer to resolution. ## Partnership and Strategy Questions 21. What kind of collaboration are you exploring? 22. Why does this feel relevant now? 23. Who should be involved if there is a fit? 24. Are there examples or references we should look at? 25. What decision or next step would you like to reach? These questions turn broad networking calls into clearer conversations. ## What Makes a Question Good A good pre-meeting question has three traits: - It is easy to answer in less than a minute - It gives the host information they would otherwise ask live - It changes how the host prepares If a question does not meet those criteria, remove it. ## Where to Put the Answers Collecting answers is only half the work. The answers need to show up where the host will see them. The calendar event is usually the best place, because it is where the host looks right before the call. MochiMeet turns these answers into a Meeting Brief, so the context stays attached to the booking instead of getting lost in a form submission. ## FAQ ### How many pre-meeting questions should I ask? Usually two or three. Four can work for high-value meetings. More than that should be used carefully. ### Should questions be required? For important external meetings, yes. For casual or internal meetings, optional questions may be enough. ### What is the easiest way to start? Write down the questions you ask in the first five minutes of your calls. Move the best two into your booking flow.