Event rental inquiry response templates: from message to quote

Ask for the minimum useful brief

Someone asking about a tent may not know the size, anchoring or installation requirements. Do not make them design the solution before replying. Ask a short first question, then build on their answer. Date and location help the team check whether the job is possible; guest count and layout help them scope it.

These are fictional message examples. They do not confirm stock, installation feasibility, a hold or a price.

Build a brief without turning the reply into an interrogation

Split the brief into two passes. The first establishes whether there is a plausible event to review: date, location and approximate use. The second collects what the operator needs to prepare options. Asking every possible installation question in the first message makes a casual inquiry feel like homework; omitting those questions entirely pushes uncertainty into the quote.

Do not ask for a detail that is already established in the conversation. If the customer says “same venue as last time,” retain that statement as context but confirm the event and the relevant site details before copying the prior job. A repeat contact may still be asking about a different location or setup.

How Figaro moves the inquiry forward

1. An inquiry arrives through a supported channel. Figaro reads the request and existing customer context rather than starting the brief again.
2. Figaro prepares a response and collects the agreed qualification details. Calls or texts use the configured approval rules.
3. The inquiry and brief stay in Twenty CRM, with the conversation available for the next person. An uncertain customer or job match needs review.
4. The team reviews site requirements, availability and price, then owns the quote and next action.

Figaro is early access, built on Stretch Tent inquiries. Yelp, website inquiries and the Quo/Twenty setup are described on its product page; other marketplaces are scoped. Supported social direct-message intake can involve Oscar where that connection is enabled. Do not assume every Meta inbox is connected.

See Figaro’s current inquiry-response scope.

See Oscar’s supported social and analytics role.

Keep the record specific to the event

• Capture source, received time, event date, location, guest count, requested scope and the details still missing.
• Keep a separate opportunity for a different event from the same customer. A phone number alone does not prove two messages concern the same job.
• Give the review or callback to one person with a due date. An automated response must not leave an unowned queue behind.

Worked example: an incomplete Stretch Tent request

The following Stretch Tent conversation and records are fictional teaching examples.

Customer: “We need a tent for about 70 people.” First prepared reply: “Thanks for contacting Stretch Tent. What is your event date and city or ZIP? Will the space be used for dining or a standing reception?” This gives the customer a small, answerable task without inventing a size or price.

Customer: “A Saturday in June in Pasadena, seated dinner.” The month alone is insufficient to check a particular date. The next prepared response asks for the Saturday and a photo or approximate dimensions of the space. Figaro should carry the 70 guests, city and dining use forward instead of requesting them again.

Customer provides a date and photo but says the ground may be paved. The record can now contain the event date, location, guest count and stated surface uncertainty. It should also contain an owner task to review the site and an open question about access or anchoring. “Ready for owner review” is a useful next action; “installation approved” is an unsupported conclusion.

Before delivery, the operator checks whether the prepared reply refers to the right event and accurately states what is still unknown. The team then decides whether to prepare a quote, ask another practical question or explain that the job is outside scope.

Read the first-party Stretch Tent case.

Review useful replies, not just response speed

For one cohort of inquiries, count first useful response, brief completed, quote prepared and recorded outcome. Note where customers stop. If fast replies repeatedly attract the wrong job type, review the ad promise with Hunter rather than adding more reminders.

Continue with templates for a quote that has already been sent.

Scope the intake and follow-up workflow.

Use a small quality review to choose the next improvement

Select a set of inquiries of the same type and retain the review date. For each, record whether the first reply contained a useful question, whether the customer supplied the missing details, whether a person completed the review and whether a quote followed. Separate customers who stopped replying from jobs that were outside the service area or not feasible.

• Many acknowledgements but few completed briefs: shorten or clarify the first question and inspect the channel handoff.
• Completed briefs waiting for review: assign an owner and capacity before increasing acquisition.
• Quotes prepared for unsuitable jobs: review qualification and the ad promise with Hunter.
• Duplicate or contradictory records: fix customer/event matching before interpreting funnel rates.

In an explicitly hypothetical review of 20 inquiries, 12 complete briefs and 8 quotes describe two different transitions. Brief completion is 12/20; quote preparation among completed briefs is 8/12. Neither number is a booking rate. These assumed counts illustrate the measurement method and are not Stretch Tent performance results.

Diagnose whether the next constraint is acquisition or handling.

Questions and answers