Buy requests and sales conversion

Email a buy request

Send the request PDF/message to selected recipients.

Audience: CRM staffPermission: real_buy_request: View/EditModule v1.0.0
Exact navigationAdmin Area → Requests & Applications → Buy Requests → open request → Send Email
Before you begin
  • Use an account with real_buy_request: View/Edit and confirm the intended record or setting before making a change.
  • Follow the exact route above. If the screen or action is absent, check module activation, ownership and permissions rather than using another person’s account.
  • Use controlled test data for configuration, integration, email, AI, payment, portal or automation changes before production-wide use.

What this guide covers

Send the request PDF/message to selected recipients. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow.

Exact step-by-step process

  1. Open Admin Area → Requests & Applications → Buy Requests → open request → Send Email.
  2. Open the source record and verify its recipient, status, totals and attachments.
  3. Choose the Send, Email, Share or Request action described in the guide.
  4. Select recipients and attachment/signature options shown by the form.
  5. Submit once and verify the activity, delivery metadata, public link or approval request created by the module.

Fields, choices and supported possibilities

Exact actionEmail a buy request
Exact navigationAdmin Area → Requests & Applications → Buy Requests → open request → Send Email
Module version1.0.0
Access rulereal_buy_request: View/Edit
VerificationReopen the source record and confirm the expected status, linked record, file, notification, portal visibility or financial effect.
Request recordCode, client, property/item, request type, currency, property price, term and inspection choice.
Notes and billingClient note, admin note and billing/shipping data where the form exposes them.
ConversionReview status and linked customer/property before converting to a contract or invoice.

Code-backed validations and workflow rules

  • The send form supports recipients, CC, custom template and attach_pdf.
  • Buy and rent requests use separate real_buy_request and real_rent_request capability groups.
  • Status changes and conversion actions validate the current request and linked record IDs.

Expected result and verification

  • The supported email a buy request flow completes without bypassing permission or validation checks.
  • The resulting record, setting, status, file, delivery event or external response is visible from the relevant workspace.
  • Unexpected validation, provider or linked-record errors are investigated before retrying.

Security, privacy and operational checks

  • Apply least privilege to purchasing, vendor, invoice, payment, return, contract and report permissions.
  • Verify vendor identity, bank/payment details, tax, currency, totals and approvals before creating financial commitments.
  • Treat public links, signatures, portal files, attachments and exported reports as controlled business records.
  • Test settings and automated jobs with controlled records before production-wide use.