> ## Documentation Index
> Fetch the complete documentation index at: https://help.kuverbooks.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Review Enquiry Details and Customer Product Intent Records

> Use the Kuvera Arc Enquiry Detail View to review a customer's contact information, selected products, quantities, and total purchase-intent value.

The Enquiry Detail View shows the full purchase-intent record captured from your e-commerce website. Use it to review the customer's contact information, selected products, quantities, and estimated enquiry value in one place.

<Info>
  The Enquiry Detail View is **read-only**. It shows the information submitted through your e-commerce website and cannot be edited from within Kuvera Arc.
</Info>

## Open an enquiry detail record

You can open an enquiry directly from the Enquiries Listing Page.

<Frame caption="Enquiries Listing Page" />

<Steps>
  <Step title="Go to Enquiries">
    Navigate to **E-Commerce Management > Enquiries & Contacts** and confirm that the **Enquiries** tab is selected.
  </Step>

  <Step title="Find the enquiry">
    Browse the listing table or use search and date filters to locate the enquiry you want to review.
  </Step>

  <Step title="Open the detail view">
    Click the **View** icon in the enquiry row.

    <Frame caption="Open enquiry detail view" />
  </Step>

  <Step title="Review the details">
    Review customer information, product information, and summary totals.

    <Frame caption="Enquiry Detail View" />
  </Step>

  <Step title="Close the view">
    Click **Close Preview** to return to the Enquiries Listing Page.
  </Step>
</Steps>

## Detail view sections

The Enquiry Detail View is organized into customer information, product information, and summary totals.

<CardGroup cols={3}>
  <Card title="Customer information" icon="user">
    Contact details for the customer who submitted the enquiry.
  </Card>

  <Card title="Product information" icon="boxes-stacked">
    Products the customer selected or showed interest in.
  </Card>

  <Card title="Summary" icon="calculator">
    Combined quantity and estimated total value of the enquiry.
  </Card>
</CardGroup>

## Customer information

The top section shows the customer's submitted contact details.

<Frame caption="Customer information section" />

<CardGroup cols={2}>
  <Card title="Customer Name" icon="user">
    Full name submitted through the e-commerce purchase flow.
  </Card>

  <Card title="Phone Number" icon="phone">
    Customer contact phone number.
  </Card>

  <Card title="Customer Email" icon="envelope">
    Customer email address.
  </Card>

  <Card title="Enquiry Date" icon="calendar-days">
    Date and time the enquiry was recorded in Kuvera Arc.
  </Card>
</CardGroup>

<Info>
  Use the phone number and email address for follow-up through your preferred communication channel.
</Info>

## Product information

The product section lists every item the customer selected or expressed interest in.

<Frame caption="Product information section" />

<CardGroup cols={2}>
  <Card title="Product Name" icon="box">
    Product the customer showed interest in purchasing.
  </Card>

  <Card title="Quantity" icon="calculator">
    Quantity the customer selected or requested, if captured.
  </Card>

  <Card title="Price" icon="tag">
    Listed price per unit at the time of the enquiry.
  </Card>
</CardGroup>

<Note>
  Product details reflect what the customer had in the cart or purchase flow when the enquiry was submitted. Current inventory availability or pricing may have changed since then.
</Note>

## Summary section

The summary section shows the combined value of the enquiry.

<Frame caption="Enquiry summary section" />

<CardGroup cols={2}>
  <Card title="Total Quantity" icon="calculator">
    Combined quantity of all products included in the enquiry.
  </Card>

  <Card title="Total Price" icon="money-bill">
    Combined estimated value of all products in the enquiry.
  </Card>
</CardGroup>

<Tip>
  Use **Total Price** to quickly identify high-value enquiries that may deserve priority follow-up.
</Tip>

## Use enquiry details

<Tabs>
  <Tab title="Sales follow-up">
    Use the customer's contact information and product details to have a more informed conversation.

    Knowing which products the customer selected and the estimated value of the enquiry helps your team personalize follow-up.
  </Tab>

  <Tab title="Pre-sales analysis">
    Review **Total Price** to identify high-value enquiries. Use product details to check stock availability, review promotions, or prepare a quote.
  </Tab>
</Tabs>

## Read-only behavior

Enquiry records are read-only because they represent the original customer interaction captured from your e-commerce website.

<AccordionGroup>
  <Accordion title="Why can't I edit enquiry details?">
    Enquiry records show the exact information captured from the website. Keeping them read-only preserves an accurate record of customer purchase intent.
  </Accordion>

  <Accordion title="What if customer details look incorrect?">
    The customer may have entered incorrect information, or there may be a data capture issue. Verify the original website submission before using the details for follow-up.
  </Accordion>

  <Accordion title="What if product information looks wrong?">
    Product details reflect what was captured at submission time. If names, prices, or codes look outdated, compare them with your current product catalog and review your e-commerce integration settings.
  </Accordion>

  <Accordion title="Can the same customer appear multiple times?">
    Yes. A customer can submit multiple enquiries across different sessions or product selections. Each enquiry is stored as a separate record.
  </Accordion>
</AccordionGroup>

<Warning>
  Always verify customer contact details before reaching out. Enquiry information is recorded as submitted and may contain typos or placeholder information.
</Warning>

<Note>
  Use the Enquiry Detail View to understand purchase intent quickly, prioritize high-value opportunities, and prepare more relevant follow-up.
</Note>