Free Contact Forms and Paid Services: Where Each Belongs

A free contact form is useful for ordinary enquiries, account help and reports that should reach you without payment. The problem begins when the same form also acts as an undefined queue for substantial new work.

A better form may reduce spam or improve context. A paid service solves a different problem: it lets someone purchase a particular result at a stated price and delivery time. You can use both.

Separate contact from a request to do work

"How do I update my account?" is not the same as "Review my custom onboarding process and recommend fixes." One may be ordinary support; the other may be a service with substantial preparation and judgment.

Keep billing questions, refund requests, security disclosures, account access and existing customer obligations in appropriate free channels. Add a paid path where the work is new, useful and clear enough to scope.

Sell the result rather than a faster message

"Priority contact, $19" leaves the buyer unsure what they receive. A bounded review could instead cover one supplied page and deliver an annotated response addressing three specific questions. Define the page limit, what feedback is included and when it arrives.

Charging can discourage some unsuitable requests, but payment does not prove that a request is safe, in scope or ready to fulfil. It also does not replace spam filtering and ordinary security controls.

Make the service page answer the obvious questions

• Who is this for, and what situation does it address?
• What finished work will arrive, and in which format?
• What text or context link does the buyer need to supply?
• What is excluded, how much does it cost and when is it due?
• How can the buyer raise a delivery problem or request an in-scope correction?

Use the same language in the website link and the offer. If the link promises a review, the page should sell that review rather than an opportunity to discuss whether you might provide it.

What the paid path looks like in Moltgate

The buyer reads the offer, enters contact details and a short brief, agrees to the order policy, then pays through Stripe. The brief comes before payment. Buyers do not need an account and can include text and relevant context links; file attachments are not supported.

After confirmation, the buyer receives an email with a private order link. The seller communicates through the order and delivers the completed work as text or an accessible result link. The buyer has a place to find the purchase, result and subsequent conversation.

Make the seller's commitment credible

The delivery clock starts at payment with the published inputs supplied. Asking for more information does not pause it; a changed deadline requires buyer agreement. An agent-generated draft or a read flag does not constitute delivery.

Buyers have seven calendar days after delivery to review the result and request an in-scope correction. Cancellation before work starts or after an undelivered order's deadline can qualify for a full refund under the order policy. Keep these existing-order conversations out of a new paid checkout.

Test one service before expanding the menu

Free supports one published service priced up to $99. Start with work you can complete reliably and a link placed beside the relevant explanation or support policy. Use service examples for an editable starting point.

Measure relevant visits, orders and delivery effort. If the work repeats, standardize the inputs and use an agent or automation for dependable steps. Keep the free contact route available and pause new paid orders if you cannot meet the published promise.