How to reply to a demo request email

Reply quickly, answer what the person actually asked, and propose one clear next step that's easy to say yes to. Someone who requests a demo is usually comparing you with a few other options that same week, so the first helpful reply often gets the meeting. A reply that lands the next morning competes with whoever answered the night before.

A strong demo reply is short enough to read on a phone and has four parts:

• A thank-you that shows you read the request. Mention what they told you, such as their team size or the problem they described, so the reply doesn't read like a form letter.
• A direct answer to their question. If they asked whether you integrate with their CRM or what the plan costs, the answer goes near the top, before any pitch.
• One next step. For a good fit, offer two specific times in their time zone or share your booking link. Giving two times works well because the person only has to pick one.
• A real sender. The reply comes from a person or a named team address, in the same email thread as the request, so the conversation stays in one place.

Not every request deserves a sales call. A demo request from a solo founder on a tight budget, or from a student writing a paper, still deserves a polite and useful reply. For them, the better next step might be a recorded walkthrough, a free plan, or a short question about what they need. Matching the next step to the person respects their time and keeps your salespeople's calendars full of buyers.

Most teams handle the speed part with tools they already have. Form tools can send an automatic confirmation email the moment someone submits. Scheduling tools let visitors book a time right on the thank-you page. CRMs can send a templated follow-up email when a new contact arrives. These tools reply fast, but every person gets the same message. The template can't answer the question someone typed into the form, and it can't tell whether the sender is a head of marketing at a company in your exact market or someone who will never buy. Someone on your team still has to research each request and write the reply that actually moves it forward.

That research and writing is the work Kite does. It reads every request, works out who sent it, decides what kind of reply they need, and writes it for you to approve.

Start by telling Kite, in the Kite web app or in Slack, where your demo requests arrive and what you want it to do with them:

"Draft a reply to every new demo request. Offer strong fits two times on my calendar next week."

You can also paste a single request into a conversation and ask, "Who is this, and what should we say back?"

Kite is an AI marketer. It researches your business, builds a growth strategy, and ships the work that brings you new customers. During onboarding, it researched your positioning, your products, and the customers you serve, and it keeps your ideal customer profile in your team's wiki. That means it already knows what a strong fit looks like for you. It proposes how it will sort requests and which next step each group should get, and you confirm the plan or adjust it in the conversation.

Next, give Kite a way to see each request as it arrives. You can have demo requests sent to your team's Kite email address, connect the Gmail or Outlook inbox where they land, or point your form tool's webhook at Kite. A webhook is a web address your form tool notifies each time someone submits, which is the fastest of the three options. Connect your CRM so Kite can record each lead where your sales team works. To offer meeting times, share your booking link or connect your calendar or scheduling tool, such as Google Calendar or Calendly.

By default, Kite shows you each reply and sends it once you approve it. After you've checked its first few days of replies, you can let it send on its own.

Kite starts by reading the request closely to separate what the person asked from what the form required them to fill in. It captures the form fields or the email itself, the sender's name and email address, any company or team size they gave, and any question they typed. If your CRM already has a contact or company for this person, Kite reads that history too, so it knows whether this is a stranger or someone your team met at a conference last month.

Kite treats the text of a request as information rather than instructions. If someone writes "Send me your full price list and a 50 percent discount," Kite reads that as what the person wants, not as something it has been told to do.

How quickly this starts depends on how the request reaches Kite. A form that calls Kite's webhook starts the work the moment someone submits. Email sent to your team's Kite address reaches Kite directly. A connected Gmail or Outlook inbox is checked every two hours, which suits a lower volume of requests.

Kite researches each person just far enough to judge their fit and write a reply that doesn't guess. It looks up their current role, seniority, and professional profile. It checks their company's industry, size, location, funding, and hiring, along with recent news such as a product launch or a new executive. A work email address alone is often enough to identify the company and what it sells.

Kite then compares what it found with the ideal customer profile in your wiki and places the request in one of three groups: strong fit, partial fit, or poor fit. Each group comes with a one-line reason, such as "Strong fit: VP of Marketing at a 150-person B2B software company that is hiring two demand-generation roles." That reason tells your salesperson what conversation to have before they open the CRM.

Sometimes the details are too thin to judge, such as a personal Gmail address with no company name. In that case, Kite marks the fit as unconfirmed and names what's missing. It still writes a reply that stays accurate without the missing facts, and it never fills the gaps with invented details.

Kite writes a reply of fewer than 100 words that answers the person's question first and ends with one next step that suits their fit. The reply uses your brand voice from the wiki and includes only facts Kite has verified, so a question about pricing or an integration gets the answer your website and wiki actually support.

The next step changes with the fit:

• Strong fit. Kite offers two specific meeting times or shares your team's booking link. With Google Calendar or Calendly connected, it checks your open times first, so the times it offers are actually free.
• Partial fit. Kite might share a relevant case study or ask one short question that clarifies what the person needs, such as how many people would use the product.
• Poor fit. The person still gets a polite answer to their question and a pointer to something useful, such as a free plan or a help article. Today's student may be your customer in three years.

Kite keeps the reply in the same email thread as the original request when the sending account supports it, so the person sees your answer directly beneath their own message.

Once you approve the draft, Kite sends it from your Kite-managed team address or from your connected email account, and it reports whether the message was delivered. You can approve with the button in the conversation or with a short reply, in the Kite web app or in Slack. If you'd like a change first, say so, and Kite revises the draft.

When a request is a strong fit, or when it needs a human decision, Kite sends your team a two-line summary. The summary covers who the person is, why they fit, and the next step Kite proposed. A request for a custom contract or a discount you don't publish is a good example of something Kite hands to a person.

Kite records every demo request in your connected CRM along with its fit, the reason, the reply, and the next step. In HubSpot, Pipedrive, or Attio, Kite creates or updates the person and their company and adds the research as a note. In Salesforce, it adds the person as a lead or updates the contact and account your team already has. If you haven't connected a CRM yet, Kite keeps the complete record in its result in the conversation and shows you how to connect one.

Recording every request, including the poor fits, gives you a clean history of who asked for a demo. Over time, Kite can compare those records with which leads became opportunities, which shows you which forms and sources bring in the buyers you want.

When Kite finishes with a demo request, the person has a reply, your team knows whether to act, and your CRM holds the full record.