Help Scout logo

Land demo requests in the sales mailbox

Demo requests open as conversations in the Sales mailbox, carrying company size, the problem to solve and the timing.

When this happens

New Submission on your "Book a demo" form

Do this

Create a conversation in the Sales mailbox with the company size, use case and timing fields

One-directional. A submission triggers the action — nothing is written back into your form.

Inbound demo requests are easy to answer late, because they arrive somewhere nobody is watching. Putting them in a Sales mailbox in Help Scout means they queue, get assigned and get chased in exactly the way support conversations already do.

This suits teams where the same handful of people answer both the prospect and the customer. Every message to that account — the demo request, the follow-up, the support question a year later — sits on one history.

Setting it up

  1. 1

    Publish "Book a demo" with Work Email required and Phone Number optional. Demanding a phone number up front costs you requests, and the first reply is going by email anyway.

  2. 2

    Use conditional logic so larger companies see the extra qualifying question and everyone else gets a short form.

  3. 3

    In Zapier, choose formformform's "New Submission" trigger and select the demo form.

  4. 4

    Add Help Scout's "Create Conversation" action and set Mailbox to Sales, so demo requests never enter the support response-time figures.

  5. 5

    Build the subject from Company plus a short suffix such as "demo request", which makes the mailbox list read as accounts rather than as a wall of identical words.

  6. 6

    Map What problem are you trying to solve? and When are you looking to implement? into the body, with Company Size on its own line at the top.

  7. 7

    Add a Help Scout workflow on the demo tag that assigns by company size: the larger accounts to a named rep, the rest to the shared sales queue.

  8. 8

    Test with an address you control, confirm the assignment fires, then turn the Zap on.

What maps where

Using the Demo Request Form as the starting point. These are its real fields — swap in your own and the mapping works the same way.

Form fieldHelp Scout
First NameCustomer first name on the conversation
Work EmailCustomer email — keeps the demo thread in the same history as later support
CompanyConversation subject, so the Sales mailbox reads as a list of accounts
Company SizeTop line of the body, and the value a workflow reads to assign
What problem are you trying to solve?Main body of the conversation
When are you looking to implement?Body, under the use case

Variations worth knowing

Add an internal note instead of a thread

When the prospect already has a conversation open, use Help Scout's "Add Note" action against it rather than opening a new one. The note lands in the existing history, so the rep reads the demo request in the context of what came before.

Send the scheduling link in the reply

There is no calendar in formformform, so the booking happens in whatever scheduling tool your reps already use. Keep a saved reply in the Sales mailbox with the link in it, and the first response goes out in a couple of clicks.

If something isn't arriving

The customer name shows as an email address.

First Name and Last Name were not mapped, so Help Scout falls back to the address it was given. Map both on the action step. The demo form keeps them as separate fields, which is exactly what Help Scout's customer record expects.

Demo requests are being answered days late.

Nobody follows the Sales mailbox. Help Scout notifies followers and assignees rather than everyone with access, so add the reps as followers, or assign on creation so each notification has somewhere to go.

Frequently asked questions

Why keep sales enquiries in the same tool as support?

Because the history is the point. When that person writes in six months later with a problem, the demo thread and the support conversation sit on one customer record, so the agent can see what was promised without asking anyone.

Can one form feed both sales and support?

It can. Add a paths step in Zapier keyed on a routing question in the form, so demo requests open in Sales and anything that turns out to be a support issue opens in Support. One form, one embed, two mailboxes.

Will the prospect see this as a support ticket?

No. Help Scout conversations read as ordinary email on the other end, with no portal and no reference number unless you add one. The reply arrives from your sales address and looks like a message a person sat down and wrote.

Related automations

Build the form first

The automation needs somewhere to fire from. Publish a form, connect it once, and every submission from then on runs this flow.

Start free