Skip to content

article

Collecting Contact and Quote Requests

Set up contact and quote forms that route automatically to Messaging › Submissions, so sales and support can reply in one place.

Overview

Contact and quote requests are the most common — and most time-sensitive — forms a business runs. StretchForms gives them special treatment: any form recognized as a contact or quote form is automatically wired to Messaging › Submissions, so responses land where your team already replies to customers. This guide walks through building one end to end.

Why contact and quote forms are special

When a form's type, key, or title signals contact or quote intent, StretchForms automatically:

  • sets the target app to Messaging,
  • assigns the Submissions team as the default owner, and
  • treats the response as a messaging submission rather than a generic form entry.

That means you don't have to configure routing by hand — name it right and the plumbing is done.

Build a contact form

1. Create a New form and name it Contact Us.
2. Set the form type to contact. This is the trigger for automatic Messaging routing.

3. Add the fields a contact form needs:

- Full name — short text, required

- Email — email, required

- Phone — phone, optional

- Company — short text, optional

- Subject — short text

- Message — long text, required

- Consent — checkbox (agree to be contacted / privacy)

4. Set the status to Active.

5. Submit a test message and confirm it appears in Messaging › Submissions.

Build a quote form

A quote form works the same way — just use the type quote and add the fields you need to price the work:

  • Contact fields (name, email, phone, company)
  • What do you need a quote for? — dropdown or long text
  • Budget — dropdown (ranges) or number
  • Timeline — date
  • Details — long text

Because the type is quote, responses route to Messaging automatically, arriving with the Submissions team as owner.

What your team sees

Each contact or quote response arrives as a submission carrying the respondent's name, email, phone, company, subject, and message, plus the source page it came from and the consent flags. From Messaging › Submissions (and the StretchForms Intelligence inbox), your team can read the full response, assign it, add notes, and reply.

Example

A renovation company publishes a Get a Quote form on its site. A homeowner submits it with a $25k–$50k budget and a spring timeline. The response lands in Messaging › Submissions owned by the Submissions team; a coordinator assigns it to an estimator, adds a note with the site address, and replies to book a visit — all without leaving the suite.

Tips

  • Name the type contact or quote to get automatic routing for free.
  • Always include a consent checkbox — consent is captured with the submission.
  • Ask only what you need to respond. For a first contact, name, email, and message are often enough; qualify further in the reply.
  • Add a subject field so your team can scan the queue quickly.

Troubleshooting

My contact form didn't route to Messaging. The auto-route triggers on contact/quote intent in the type, key, or title. Rename the form type to include contact or quote, then re-save.

Responses show up in the StretchForms inbox but not Messaging. Confirm the form type genuinely signals contact/quote; a type like feedback won't trigger messaging routing. You can also set the target app to Messaging manually.

I'm not capturing phone/company. Add those fields to the form — they only arrive if you ask for them.

FAQ

Can I still triage contact submissions inside StretchForms? Yes. They appear in the Intelligence inbox for triage and also route to Messaging › Submissions for replies.

Do quote and contact forms support conditional logic and steps? Yes — everything in the builder is available, so you can branch and split a quote form as needed.

Was this helpful?

Help us improve this article

Use these controls to share whether this answer solved the issue. Feedback helps prioritize updates to StretchSuite Support.