Describe a service the customer can understand before paying
A request form works best when customers know exactly what the price buys. Name the deliverable, explain included revisions or preparation, and state what happens if the request is outside scope. If you need to assess a project before quoting, collect that information first through your normal inquiry process. Do not label an unspecified future project as a guaranteed fixed-price service.
Collect the briefing and reference files privately
Ask for the intended result, relevant background and any delivery requirements. A file-upload question can collect a PDF brief, reference image or TXT document. Supported uploads are private and available to the account owner from submissions, rather than through public image links. Keep the upload relevant to the task and make it required only if you cannot start the agreed service without it.
Agree on delivery after reviewing the paid request
A preferred delivery date is a request, not an automatically confirmed deadline or appointment. Review the briefing and payment status, then confirm the scope and schedule separately. Use paid options for clearly defined extras, such as an additional review, and explain any constraints before checkout. Manual services still need action from you; a paid submission does not mean the service has been delivered.