Skip to content
Content SnareHelp centre

How to create great requests

Quick answer

A great request has clear questions and instructions that even your most difficult client could follow. Ask only for what you need, and pick the field type that fits each answer. When clients get stuck on a question, reword it for next time.

Iterate over time

You can send a rough request today and sharpen it later. Your requests and templates don't need to be perfect from day one, because they evolve on client feedback. When someone misreads a question or asks what you meant, that's your cue to reword the instruction or add an example, so the next client has an easier run. Keep doing that and your templates get better over time.

Why the client's view is deliberately simple

Your client sees a stripped-back version of the request, made for people who have never used it and won't be trained on it. Fonts, spacing and layout are deliberately simple. What your client experiences depends on your questions, your instructions, and the order you put them in. On Plus and above you can add your own branding on top. So put your effort into clear questions, the right field types, and instructions that leave no doubt about what you need.

Put yourself in your client's shoes

Walk through the whole process from your client's side. Picture every email they get and every tool you ask them to use, then ask yourself three questions.

What do they know?

After years in your field, you take a lot for granted that your clients won't know. Terms and abbreviations that seem basic to you may mean nothing to them. When you write a question or an instruction, picture your most difficult client and explain it to that person. Get it clear enough for them and everyone else finds it easy.

How much time do they have?

Everyone is busy, so ask only for what you need and cut the rest. If a request is long, tell your client they don't have to finish it in one sitting. Their answers save automatically as they go, so a client can close the tab and come back to it later.

Did they know it was coming?

A ten-page request feels far less of a shock when your client is expecting it. Content Snare is built to reduce that overwhelm, but a heads-up still helps. Early in your process, and more than once, mention on calls, in your proposal, and in your emails that you'll need information from them before you can start.

Write instructions that guide your client

Instructions are the foundation of a good client experience. With good instructions your request becomes a guided workflow rather than a big list of questions. They're also where you show a client how the request works, like submitting an answer for review and asking a question when they're stuck. The full guide is at write instructions that get better answers.

Customize your reminders

Content Snare's reminders work out of the box, but they're written to suit everyone, so they're worth tailoring to your brand and your client. A few things that help:

Rewrite the first email. The first message your client gets is their first impression of Content Snare. If they weren't expecting it, explain what the request is for and why the link beats replying by email. Their answers stay in one place and they can track their own progress.

Add a quick refresher. By the time a reminder goes out, your client may have forgotten what the request was about. A line on the due date, what you need the information for, and what happens if it's late is often enough. Use the Variables dropdown to insert a live figure like percent complete or days remaining, so a line reads "you're 70% through, 3 days left" without you editing a number by hand.

Give different client types different schedules. You set up a reminder schedule once for the whole account, then choose which one each request uses. That lets you remind a slow-moving client type more often without touching anyone else's. Build them under reminder schedules.

Use SMS sparingly. Text reminders suit clients who don't live in their inbox, like some consumer clients or clients who aren't especially tech-savvy. Business clients almost always see email. SMS messages are plain text only, and each one uses part of your monthly SMS credits. Credits reset monthly and don't carry over, and a longer message uses more of them. Once the month's credits run out, texts stop until the reset. Keep them short and save them for the clients who need them. A client reading an SMS is on their phone, where instructions take up more room, so send yourself a test request and check how it reads on a small screen.

More ways to make requests easier

Put the critical information first. If you can get moving with only part of what you're asking for, group that on the first page and call it something like "Critical Information." Tell your client that finishing that page alone is enough for you to start, and they can do the rest afterward.

Build different templates for different clients. If your clients fall into distinct groups, a separate template for each can be worth it. A building company might ask both architects and homeowners "what kind of door do you want?" The homeowner needs photos to choose from; the architect only wants to type the answer and would find scrolling through pictures annoying. Set these up in templates.

Show only the questions that apply. Conditions let you hide or reveal questions and whole sections based on an earlier answer, so a client only sees what's relevant to them. Ask "what kind of company do you have?" and reveal the private-company section only when they pick that. See show and hide questions with conditions.

Watch your comments for friction. The Ask A Question button is where a stuck client reaches out. If the same question keeps coming up, or clients trip on the same spot, reword the instruction, add a screenshot or a short video, or put the answer straight into your instructions as an FAQ using the exact wording clients used. More on comments.

Test it before you send it. Preview has a Test mode that saves nothing, so it is the one to use for walking your own conditional paths. Don't test in Prefill mode. What you type there saves into the real request and your client sees it. See preview and prefill a request.

Pick the field type that fits the answer. The right field type saves your client effort. An email field checks the address is valid on its own. For a long written answer, use a multiline or formatted text field. For a set of repeated values, use a multiple-answers text field or a table. See the full list of field types.