28.1 Overview

The Inquiries feature allows visitors to send a message through a public VCard. Each submission is connected to the VCard through which it was received, allowing an account with several digital cards to identify the correct person, department, service, or campaign.

An inquiry can contain:

The customer dashboard provides a central Inquiries area for reviewing submissions from all associated VCards. Each VCard also provides its own Inquiries destination for reviewing messages connected only to that card.

28.2 Inquiries Versus Other Visitor Records

Several Book features collect visitor information, but they serve different purposes.

Inquiries

Used for questions, requests, general messages, service interest, and product interest.

Contacts

Used for visitor details collected through the contact-related workflow.

Appointments

Used when a visitor selects a date and time for a booking.

Product Orders

Used when a visitor submits an order for VCard products.

Subscribers

Used when a visitor joins the VCard’s email subscriber list.

An inquiry does not automatically become an appointment or product order. The card owner must respond and guide the visitor to the appropriate next action.

Enabling the Public Inquiry Form

28.3 Opening Basic Details 3

The main inquiry form is controlled from Basic Details 3.

To open it:

1. Select VCards.
2. Locate the digital card.
3. Select Edit.
4. Open Basic Details.
5. Select the Basic Details 3 tab.
6. Locate Display Inquiry Form.

The programmed Basic Details 3 screen contains an enable_enquiry_form switch specifically for the public inquiry form.

28.4 Enabling Display Inquiry Form

To allow visitors to submit general inquiries:

1. Turn on Display Inquiry Form.
2. Select Save or Save & Next.
3. Open the public VCard.
4. Locate the inquiry or contact form.
5. Submit an authorized test message.
6. Confirm that it appears in the dashboard.

The selected template determines the form’s exact heading, position, button style, and appearance.

28.5 Hiding the Inquiry Form

To stop accepting general inquiries through a VCard:

1. Open Basic Details 3.
2. Turn off Display Inquiry Form.
3. Save the VCard.
4. Refresh the public card.
5. Confirm that the form is hidden.

Hiding the form does not delete inquiries already received.

It also does not necessarily remove separate Service or Product inquiry buttons. Review those controls independently.

28.6 Inquiry Form Visibility Is Not Controlled by Manage Section

The general inquiry form is controlled through Display Inquiry Form in Basic Details 3 rather than a separate Inquiry checkbox in Manage Section.

When the form does not appear, review:

before changing unrelated section settings.

Service and Product Inquiries

28.7 Service Inquiry Button

The Services feature provides a separate Display Service Inquiry Button control.

When enabled, visitors can begin an inquiry from the Services area.

This is useful when a visitor has a question about:

1. Availability
2. Pricing
3. Service requirements
4. Service location
5. Customization
6. Eligibility
7. Scheduling
8. Deliverables

The system maintains a dedicated operation for changing the Service inquiry-button setting.

28.8 Enabling Service Inquiries

To enable inquiries from Services:

1. Open the VCard editor.
2. Select Services.
3. Locate the Service inquiry-button setting.
4. Turn it on.
5. Save the change.
6. Open the public VCard.
7. Select the inquiry action from a Service.
8. Confirm that the inquiry form opens.
9. Submit an authorized test.

The exact button text and placement can vary by template.

28.9 Product Inquiry Button

Products provide their own Display Product Inquiry Button control.

Use it when visitors may need information before ordering, such as:

1. Product availability
2. Size or specifications
3. Delivery
4. Custom pricing
5. Wholesale requests
6. Installation
7. Compatibility
8. Product variations

The Product inquiry button is separate from the Product Order process.

28.10 Product Inquiry Versus Product Order

A Product inquiry expresses interest or asks a question.

A Product Order creates an order-related record.

Example:

Do not treat an inquiry as a confirmed sale until the customer completes the proper ordering and payment process.

28.11 Review All Three Inquiry Controls

A VCard can potentially use:

Review each one separately.

For a professional consultant, the general form and Service inquiry button may be useful.

For an online product card, the Product inquiry button and Product Order workflow may be more important.

Avoid displaying unnecessary inquiry options that lead to the same action and confuse visitors.

Inquiry Attachments

28.12 Enable Attachment for Inquiry

The system includes a user setting named:

When enabled, the public inquiry process can allow a visitor to attach one supported image to the submission.

This setting is associated with the VCard owner’s user configuration and can affect inquiry forms connected to that account.

28.13 Supported Attachment Formats

Inquiry attachments accept:

Do not instruct visitors to upload:

1. PDF documents
2. Word documents
3. ZIP archives
4. Executable files
5. Videos
6. Audio files
7. Spreadsheets

The programmed inquiry validation accepts the supported image formats when the attachment setting is active.

28.14 Enabling Attachments

To allow image attachments:

1. Open the user settings area.
2. Locate Enable Attachment for Inquiry.
3. Turn it on.
4. Save the setting.
5. Open a public VCard in a private browser window.
6. Open the inquiry form.
7. Confirm that an attachment control is available.
8. Upload an approved JPG or PNG test image.
9. Submit the inquiry.
10. Confirm that the attachment can be downloaded from the dashboard.

28.15 When Attachments Are Useful

An image attachment may help with:

1. Product photographs
2. Damage reports
3. Design references
4. Screenshots
5. Property images
6. Equipment photographs
7. Error screenshots
8. Installation conditions
9. Branding examples

Do not request highly sensitive documents through a public inquiry form.

28.16 When Attachments Should Be Disabled

Consider leaving attachments off when:

1. The business does not need visitor images.
2. Staff cannot review uploaded files safely.
3. The inquiry process should remain simple.
4. Visitors might upload confidential records.
5. A secured customer portal should be used instead.
6. The organization has no documented file-retention process.

Enabling a feature that is not operationally needed can create unnecessary privacy and security responsibilities.

Public Inquiry Fields

28.17 Visitor Name

The visitor’s Name is required.

The system requires at least two characters.

Encourage visitors to enter a recognizable name rather than:

For internal testing, clearly identify the record as a test.

Example:

28.18 Email Address

Email is required and must use a valid email format.

Example:

The visitor should enter an address they actively monitor because the business may use it to respond.

An inquiry can still appear in the dashboard even when the visitor enters an address that is technically formatted correctly but does not actually exist. Staff should verify questionable contact information before relying on it.

28.19 Telephone Number

The Telephone Number is optional.

When entered, it must satisfy the form’s phone-number validation.

Visitors should use a complete number, including the appropriate country or area information when the business serves multiple regions.

Example:

Test the public form’s accepted telephone formatting before publishing instructions that include spaces, parentheses, or other punctuation.

28.20 Message

The Message is required.

The programmed message length is:

Visitors should provide enough information for the business to understand the request.

Weak:

Better:

I would like information about scheduling a business technology assessment for a company with approximately 25 employees.

Because the field has a maximum length, longer requests should be continued through email or another approved communication channel.

28.21 Keep the Inquiry Form Focused

The general inquiry form is not intended to replace:

1. A full application
2. A detailed intake questionnaire
3. A customer-support ticketing system
4. A secured document-upload portal
5. A medical-information form
6. A student-record system
7. A payment form

Use a Custom Link or approved Iframe when visitors must complete a more detailed external process.

Privacy and Terms Agreement

28.22 Agreement Requirement

When the VCard has a saved Privacy Policy or Terms and Conditions, the inquiry submission requires the visitor to agree to the displayed policy or terms control.

A visitor who does not agree receives a validation message and cannot complete the inquiry.

This connects the form submission process to the policies configured for that VCard.

28.23 Testing the Agreement

After publishing a Privacy Policy or Terms and Conditions:

1. Open the public VCard privately.
2. Open the inquiry form.
3. Complete the required fields.
4. Leave the agreement control unselected.
5. Submit the form.
6. Confirm that an agreement message appears.
7. Select the agreement control.
8. Submit again.
9. Confirm successful processing.

28.24 Keep Policies Accurate

The Privacy Policy should accurately explain that inquiry submissions may collect:

1. Name
2. Email
3. Telephone number
4. Message
5. Uploaded image
6. Submission-related technical information where applicable

It should also explain how the organization uses, stores, shares, and retains the information based on its actual practices.

Terms and Conditions may explain appropriate use of the form and prohibit abusive, unlawful, or misleading submissions.

Visitor Submission Process

28.25 Typical Public Flow

The inquiry process generally follows:

Public VCard templates connect the form to the inquiry-submission route associated with the selected VCard.

28.26 Successful Submission

When an inquiry is accepted:

1. An inquiry record is created.
2. It is associated with the VCard.
3. An uploaded image is stored when supplied and accepted.
4. The system attempts to send an email notification.
5. The visitor receives a success response.

The visitor-facing success message indicates that the inquiry was sent successfully.

28.27 Avoid Repeated Submission

Visitors should not repeatedly select Submit while the first request is processing.

Repeated actions can potentially create duplicate inquiries.

When duplicate records appear:

1. Compare the visitor details.
2. Compare the message.
3. Compare the submission time.
4. Respond only once unless separate requests are intended.
5. Remove unnecessary duplicates after preserving required records.

Inquiry Notification Email

28.28 Where the Notification Is Sent

The system first checks the primary email saved on the VCard.

When a VCard email exists, the inquiry notification is directed there.

When that field is empty, the system uses the VCard owner’s account email as the fallback destination.

A useful configuration is:

Review the receiving email before distributing the card.

28.29 Setting the Correct VCard Email

To review the inquiry destination:

1. Open VCards.
2. Edit the selected VCard.
3. Open Basic Details.
4. Review the primary Email field.
5. Enter the approved receiving address.
6. Save the VCard.
7. Submit a test inquiry.
8. Confirm that the expected mailbox receives it.

Do not use an inactive or former employee’s address.

28.30 Dashboard Record Versus Email Notification

The dashboard inquiry record should be treated as the primary record of the visitor’s submission.

Email notification can fail because of:

1. Incorrect mail configuration
2. Spam filtering
3. Mail-service interruption
4. Receiving-server rejection
5. Incorrect VCard email
6. Full mailbox
7. Domain-authentication problems

Review the Inquiries dashboard regularly even when email notifications normally work.

Opening Inquiries

28.31 Global Inquiries List

To review inquiries from all VCards:

1. Sign in to the customer dashboard.
2. Select Inquiries from the main menu.
3. Review the available records.
4. Open a record to view its complete details.

The global Inquiries route and attachment-download operation are programmed as customer dashboard functions.

28.32 Per-VCard Inquiries

To review messages connected to one VCard:

1. Select VCards.
2. Locate the desired card.
3. Open its three-dot action menu.
4. Select Inquiries.
5. Review the records associated with that card.

The VCard action menu includes a dedicated Inquiries link. The per-card route is separate from the global list.

28.33 When to Use the Global List

Use the main Inquiries area when:

1. Several VCards receive messages.
2. A central staff member manages responses.
3. The organization needs one combined review process.
4. You need to identify which VCard produced each inquiry.
5. You are checking for recent submissions across the account.

28.34 When to Use the Per-Card List

Use the VCard-specific list when:

1. Reviewing one employee’s messages
2. Managing one campaign
3. Reviewing one department
4. Investigating a particular VCard
5. Testing a newly created card
6. Confirming that a duplicate card receives its own inquiries

Viewing Inquiry Details

28.35 Opening a Record

Select the View action beside an inquiry.

The details window can display:

In a VCard-specific inquiry view, the card is already known, so the detail display may focus on the visitor’s Name, Email, Phone, and Message.

28.36 VCard Name

In the global list, the VCard Name identifies where the inquiry originated.

This is important when one account manages cards for:

1. Multiple employees
2. Several locations
3. Different departments
4. Separate brands
5. Multiple programs
6. Different events

Confirm the VCard before responding.

28.37 Missing Telephone Number

When the visitor did not provide a phone number, the details interface can display:

Use the required Email address to respond.

Do not assume that a missing telephone number indicates an error, because that field is optional.

28.38 Reviewing the Message

Before replying, determine what the visitor is requesting.

Common inquiry types include:

1. General information
2. Service question
3. Product question
4. Pricing request
5. Appointment request
6. Support request
7. Partnership proposal
8. Media request
9. Application question
10. Spam or abuse

Route the inquiry to the correct person or system.

Downloading an Attachment

28.39 Attachment Download Button

When an inquiry contains an uploaded image, the details window provides an attachment-download action.

When no attachment exists, the download button is hidden.

The system downloads the stored file using its original filename and recorded file type.

28.40 Downloading the File

To download an attachment:

1. Open the inquiry.
2. Confirm that an Attachment action appears.
3. Select Download Attachment.
4. Save it to an approved location.
5. Scan or inspect the file according to business security procedures.
6. Confirm that it relates to the inquiry.
7. Delete unnecessary local copies when appropriate.

The application provides a dedicated inquiry-attachment download route.

28.41 Treat Visitor Files as Untrusted

Even though the form accepts image formats, staff should handle visitor uploads carefully.

Do not:

1. Disable security software to open a file.
2. Upload the file to an unauthorized service.
3. Forward it unnecessarily.
4. Assume the filename is accurate.
5. Store it indefinitely without a reason.
6. Share it publicly without permission.

Use the attachment only for the purpose connected to the inquiry.

28.42 No Attachment Appears

When the inquiry does not show an attachment:

1. The visitor may not have uploaded one.
2. Attachments may have been disabled.
3. The uploaded format may have been rejected.
4. The visitor may have cancelled before submission.
5. The inquiry may have been submitted before attachments were enabled.

Do not request that a visitor send confidential documents through ordinary email merely because the attachment is missing.

Responding to Inquiries

28.43 No Built-In Reply Composer

The programmed Inquiry management actions focus on:

There is no dedicated Inquiry reply composer, conversation thread, internal notes field, assignment control, or response-status field in this interface.

Respond using the visitor’s provided Email or Telephone Number through the organization’s approved communication system.

28.44 Responding by Email

A recommended email response should:

1. Address the visitor by name.
2. Identify the VCard or organization.
3. Acknowledge the request.
4. Answer the question or explain the next step.
5. Include relevant links.
6. Provide a clear contact method.
7. Avoid exposing confidential internal information.

Example:

Hello Jordan, thank you for contacting AIUNIFY regarding a business technology assessment. We received your request and would like to schedule a brief consultation to better understand your current systems and goals.

28.45 Responding by Telephone

Before calling:

1. Confirm that a phone number was provided.
2. Review the message.
3. Confirm the visitor’s time zone where possible.
4. Identify the VCard through which the inquiry was submitted.
5. Prepare the relevant information.
6. Follow applicable calling and consent requirements.

Do not add the telephone number to unrelated marketing lists without an appropriate basis.

28.46 Moving the Inquiry into Another Workflow

After initial review, the inquiry may need to become:

1. A CRM lead
2. A support ticket
3. An appointment
4. A product order
5. A sales opportunity
6. An application
7. A project request
8. A partnership record

The Inquiry interface does not automatically perform these conversions.

Create the appropriate record in the organization’s connected operational system.

28.47 Preserve the Original Message

Do not alter the meaning of the visitor’s submission when transferring it to another system.

Record:

This helps preserve context and reduce misunderstandings.

Inquiry Status and Follow-Up

28.48 No Read or Unread Status

The programmed Inquiry interface does not provide a separate:

status control.

The system should not be treated as a full customer-support ticketing platform.

Use an external CRM, shared mailbox, or internal tracking process when formal follow-up status is required.

28.49 No Edit Action

Inquiry records represent information submitted by the visitor and do not provide an ordinary Edit action.

When a visitor corrects information:

1. Keep the original inquiry as submitted.
2. Record the corrected information in the follow-up system.
3. Confirm the correction with the visitor.
4. Avoid changing historical information without documentation.

28.50 Recommended Internal Workflow

A practical inquiry process is:

Assign responsibility so inquiries do not remain unanswered.

28.51 Response Priorities

An organization may classify inquiries internally as:

Urgent

Safety, active customer failure, payment concern, or time-sensitive request.

Sales

Pricing, demonstration, product, or service interest.

Support

Existing customer problem or operational question.

General

Partnership, information, media, or nonurgent request.

Spam

Irrelevant, deceptive, abusive, or automated content.

These classifications are operational recommendations and are not built-in Inquiry status options.

Deleting Inquiries

28.52 Deleting a Record

To delete an inquiry:

1. Open Inquiries.
2. Locate the correct record.
3. Confirm the visitor and VCard.
4. Select Delete.
5. Approve the confirmation.
6. Confirm that the record disappears.

The system provides a dedicated Inquiry deletion operation and returns a successful deletion confirmation when completed.

28.53 What Deletion Removes

Deleting the inquiry removes access to its stored management record, including:

1. Visitor name
2. Email
3. Phone
4. Message
5. VCard connection
6. Attachment access through that inquiry

It does not delete copies already saved in:

1. Email
2. CRM
3. Local downloads
4. Backups
5. Other internal systems

Review all applicable systems when honoring a valid deletion request.

28.54 No Visible Restore Option

The Inquiry interface does not provide a visible recycle bin or restore action.

Before deleting:

1. Confirm that the inquiry has been handled.
2. Confirm that retention is no longer required.
3. Preserve any authorized business record.
4. Confirm that the correct inquiry is selected.
5. Review whether an attachment is still needed.

A deleted record may not be recoverable through the customer interface.

28.55 Do Not Delete Merely to Mark Resolved

Because the system has no resolved-status option, deleting a record may appear to be a way to clear completed inquiries.

However, deletion should follow the organization’s retention policy.

Use a CRM, spreadsheet, shared mailbox, or other approved system to track resolution when historical records must be retained.

Privacy, Security, and Retention

28.56 Collect Only Necessary Information

The inquiry form should be used only for information needed to respond to the visitor.

Do not encourage visitors to submit:

1. Passwords
2. Social Security numbers
3. Bank credentials
4. Full payment-card information
5. Private medical records
6. Student records
7. Government identification
8. Security codes
9. Confidential customer databases

Provide a secured alternative when sensitive information is genuinely required.

28.57 Restrict Dashboard Access

Inquiry records contain personal information.

Only authorized users should be able to:

1. View messages
2. Download attachments
3. Copy contact details
4. Delete records
5. Respond to visitors

Protect dashboard accounts with strong passwords and available account-security controls.

28.58 Define a Retention Period

The organization should determine how long inquiries are retained based on:

1. Business need
2. Contract requirements
3. Legal obligations
4. Dispute handling
5. Customer-service practices
6. Privacy commitments
7. Industry requirements

Do not retain inquiries indefinitely without a documented purpose.

28.59 Avoid Unnecessary Downloads

Attachments can remain available through the inquiry record.

Download an image only when staff need it.

Unnecessary downloads create additional copies that may be harder to secure, locate, and delete later.

Testing the Complete Inquiry Workflow

28.60 Public Inquiry Test

After configuring the feature:

1. Enable Display Inquiry Form.
2. Review Service and Product inquiry-button settings.
3. Review the VCard email.
4. Review Privacy Policy and Terms.
5. Review the attachment setting.
6. Open the public VCard privately.
7. Enter an authorized test Name.
8. Enter a valid test Email.
9. Test with and without the optional Phone field.
10. Enter a message within the permitted length.
11. Upload a supported image when attachments are enabled.
12. Agree to policies when required.
13. Submit.
14. Confirm the success message.

28.61 Dashboard Test

After submitting:

1. Open the main Inquiries area.
2. Locate the test record.
3. Confirm the VCard Name.
4. Open the details.
5. Confirm Name, Email, Phone, and Message.
6. Download the attachment where applicable.
7. Open the VCard’s action menu.
8. Select its individual Inquiries option.
9. Confirm that the same record appears.
10. Delete the test inquiry after testing when appropriate.

28.62 Email Notification Test

Confirm that:

1. The message reaches the correct VCard email.
2. The sender and subject are recognizable.
3. The visitor information is accurate.
4. The message is not classified as spam.
5. The account-owner fallback works when the VCard email is empty.
6. Staff know that the dashboard should still be reviewed.

Repeat testing after changing the VCard email or mail configuration.

Duplicated VCards

28.63 Review Inquiry Settings After Duplication

After duplicating a VCard:

1. Open the duplicate.
2. Review Basic Details 3.
3. Confirm Display Inquiry Form.
4. Review the VCard email.
5. Review Service inquiry settings.
6. Review Product inquiry settings.
7. Review Privacy Policy and Terms.
8. Review the attachment setting.
9. Submit a test inquiry.
10. Confirm that the duplicate’s VCard Name appears in the global list.
11. Confirm that notification reaches the correct recipient.

New submissions through the duplicate are connected to the duplicated VCard rather than being treated as messages for the original card.

28.64 Common Duplication Risk

A duplicated VCard may still contain the original cardholder’s email.

This could send new inquiry notifications to:

1. A former employee
2. The wrong department
3. The original salesperson
4. Another location
5. An inactive mailbox

Always replace and test the email before distributing the duplicated card.

Troubleshooting

28.65 Inquiry Form Does Not Appear

Confirm that:

1. Display Inquiry Form is enabled in Basic Details 3.
2. The VCard was saved.
3. The VCard is active.
4. The correct public card is being viewed.
5. The page was refreshed.
6. The selected template supports the inquiry presentation.
7. The test is being performed in a private browser window.

28.66 Service Inquiry Button Does Not Appear

Confirm that:

1. At least one Service exists.
2. The Service is saved.
3. Display Service Inquiry Button is enabled.
4. The public card was refreshed.
5. The selected template displays the action.
6. The correct VCard is being tested.

28.67 Product Inquiry Button Does Not Appear

Confirm that:

1. At least one Product exists.
2. The Product is saved.
3. Display Product Inquiry Button is enabled.
4. The public card was refreshed.
5. The Product section is visible.
6. The correct VCard is being tested.

28.68 Inquiry Will Not Submit

Confirm that:

1. Name contains at least two characters.
2. Email is correctly formatted.
3. Phone is either blank or valid.
4. Message contains at least two characters.
5. Message does not exceed 255 characters.
6. Terms were accepted when required.
7. The attachment uses JPG, JPEG, or PNG.
8. The browser session remains active.
9. The network connection is working.

28.69 Attachment Is Rejected

Confirm that:

An image copied from another source may actually be WebP, HEIC, GIF, or another format even when it appears to be a normal photograph.

Export or convert it properly to JPG or PNG before uploading.

28.70 Attachment Control Is Missing

Confirm that:

1. Enable Attachment for Inquiry is turned on.
2. The setting was saved.
3. The public page was refreshed.
4. The correct VCard owner’s settings are being used.
5. The selected template supports the attachment control.
6. A private browser window is being used for testing.

28.71 Agreement Message Appears

The VCard has a Privacy Policy or Terms and Conditions, and the visitor has not accepted the agreement.

Select the agreement control and submit again.

Do not remove the policies merely to avoid the agreement requirement.

28.72 Inquiry Appears but Email Is Missing

Check:

1. The global Inquiries list
2. The VCard-specific Inquiries list
3. VCard primary email
4. Account email
5. Spam or junk folder
6. Mail configuration
7. Sending-domain authentication
8. Mail-service status
9. Receiving-mailbox capacity

Do not ask the visitor to submit repeatedly until the dashboard has been checked for an existing record.

28.73 Email Arrives at the Wrong Address

Review the primary Email saved on the VCard.

When it is blank, review the VCard owner’s account email because that is the fallback destination.

Update the appropriate address and submit another test.

28.74 Inquiry Appears Under the Wrong VCard

Confirm that:

1. The correct public URL was distributed.
2. The correct QR code was scanned.
3. A duplicated card was not confused with the original.
4. The visitor used the intended employee or department card.
5. Custom-domain routing opens the correct alias.

Replace incorrect distributed links and QR codes.

28.75 Phone Displays N/A

This means the visitor did not provide a telephone number.

Use the required Email address to respond.

28.76 Attachment Download Does Not Appear

The inquiry may not contain an attachment.

Also confirm that:

1. The attachment was successfully submitted.
2. The file passed validation.
3. The complete inquiry is being viewed.
4. The correct record was selected.
5. The attachment was not removed with the inquiry.

28.77 Downloaded Attachment Will Not Open

Possible causes include:

1. Incomplete download
2. Corrupted source file
3. Misleading filename
4. Unsupported local viewer
5. Security software blocking the file

Do not disable security protections. Request a replacement through an approved method when necessary.

28.78 Duplicate Inquiries Appear

Possible causes include:

1. Visitor selected Submit repeatedly.
2. Browser retried the request.
3. Visitor believed the first submission failed.
4. The same message was sent from multiple VCards.
5. Automated spam submitted the form.

Compare the records before deleting any duplicate.

28.79 Spam Inquiries

When irrelevant or abusive submissions increase:

1. Review available reCAPTCHA settings.
2. Avoid publishing unnecessary public forms.
3. Review the distributed VCard links.
4. Delete confirmed spam according to policy.
5. Do not respond to suspicious links or requests.
6. Do not download unnecessary attachments.
7. Review system security and mail filters.

28.80 Inquiry Cannot Be Edited

This is expected. The customer interface does not provide an Edit action for submitted inquiry data.

Preserve the original and record corrected information in the organization’s follow-up system.

28.81 Inquiry Cannot Be Restored

The customer interface does not provide a restore option after deletion.

Retain required information before confirming the delete action.

28.82 Inquiry Management Checklist

Before relying on the inquiry workflow, confirm that:

1. Display Inquiry Form is configured correctly.
2. Service inquiry-button behavior was reviewed.
3. Product inquiry-button behavior was reviewed.
4. The correct VCard email is saved.
5. The account fallback email is current.
6. Attachment capability is configured intentionally.
7. Only JPG, JPEG, and PNG images are accepted.
8. The Privacy Policy describes inquiry information.
9. Terms are accurate.
10. The agreement control was tested.
11. Name, Email, Phone, and Message validation work.
12. The 255-character Message limit was considered.
13. A public test inquiry was submitted.
14. The inquiry appeared in the global list.
15. The inquiry appeared under the correct VCard.
16. The details window displayed accurate information.
17. Attachment download was tested where applicable.
18. Email notification reached the correct mailbox.
19. Staff understand there is no built-in reply composer.
20. A response and follow-up process has been assigned.
21. Sensitive information is not requested through the form.
22. Retention and deletion procedures are documented.
23. Duplicated VCards use the correct email and policies.
24. The workflow was tested on desktop and mobile.

Chapter Completion

At the end of this chapter, the user should understand how to enable the general VCard inquiry form, manage Service and Product inquiry buttons, allow image attachments, review global and card-specific inquiries, view visitor information, download attachments, respond through approved communication channels, delete records, and troubleshoot submission or notification problems.